principle-report-every-transition
WHEN running a long-running loop, watch or babysitting job; NOT for one-off status reports or deciding report structure; reports each meaningful state change unprompted as it happens.
- License 许可
- MIT
- 所属仓库
- mintuz/skills
- 最近更新
- 2026-11-11
- Stars
- ★ 35
- Forks
- 7
01 前言 Front Matter
- name
- principle-report-every-transition
- description
- WHEN running a long-running loop, watch or babysitting job; NOT for one-off status reports or deciding report structure; reports each meaningful state change unprompted as it happens.
03 SKILL.md 正文
Report every transition
In a long-running loop or watch, the user learns each state change from you, not by asking.
- Before the loop starts, name the states the user cares about, such as failing, fix applied, passing, held, blocked and done.
- Report each transition when it happens, without being asked. Do not hold it back for a final summary.
- Carry the evidence that identifies the transition: what changed, the failing check or cause, the attempt count, and the new revision or artifact.
- Report a held or blocked state as a transition, naming what it waits on. Report the terminal state before going quiet.
If the user has to ask how it is going, reporting has already failed.
Distinct from: principle-never-block-on-the-human (continuing while a human decision is pending), principle-lead-with-the-answer (structuring an explanation or report), principle-gaps-are-not-passes (reporting checks that did not run).
Done: each transition was reported when it happened, with its identifying evidence; none was left for the user to discover.
04 同仓库更多 Skills
xstate
WHEN React state changes in response to an external answer — async submit, in-flight or loading flags, retries, cancellation, polling, optimistic updates, stale responses — or to an interaction with an interruptible middle, such as a drag or a gesture; or WHEN building, reviewing, testing, or visualising XState 5 actors and @xstate/react integrations; NOT for a value one event sets completely, such as a text draft, a focus flag, or a plain open and closed toggle; models typed lifecycles and renders legal Mermaid stateDiagram-v2 charts.
web-design
WHEN refining UI layout, typography, color, or polish; NOT code implementation; provides concise principles for intentional, legible design.
tailwind
WHEN building design systems or component libraries with Tailwind CSS; covers design tokens, CVA patterns and dark mode.
refactoring
WHEN you need a plan to refactor, restructure, or clean up working code and the test result is known, either green or a recorded failing set; NOT for new feature delivery or any behavior change; reversible-baseline safety with prioritized improvements.
react
WHEN building or changing React components, pages, hooks, effects, or apps, including edits to existing components; NOT for test code (react-testing) or styling (css, tailwind); enforces scalable architecture, state management, API layer, performance patterns.
react-testing
WHEN testing React components/hooks/context with React Testing Library; NOT e2e; covers renderHook, providers, forms, and anti-patterns.