principle-outcome-oriented-execution
WHEN an approved migration has explicit phase boundaries; NOT unmanaged breakage; converge on the verified end-state contract.
- License 许可
- MIT
- 所属仓库
- mintuz/skills
- 最近更新
- 2026-11-13
- Stars
- ★ 35
- Forks
- 7
01 前言 Front Matter
- name
- principle-outcome-oriented-execution
- description
- WHEN an approved migration has explicit phase boundaries; NOT unmanaged breakage; converge on the verified end-state contract.
03 SKILL.md 正文
Outcome Oriented Execution
State the accepted end-state behavior and guarantees, affected consumers, phase checks and rollback. Optimize the migration for that outcome rather than preserving throwaway internal shapes.
Temporary breakage is acceptable only inside authorized, isolated, reversible work with a declared boundary and recovery path. Keep shared branches, deployed systems and supported consumers usable. Use compatibility only where those real obligations require it.
Run high-signal checks as each phase closes. Resolve failed gates before building dependent work on them.
Finish with the relevant static, integration and runtime checks against the final artifact. Compilation is one result, not proof of ordering, cancellation or persistence. Report unfinished checks honestly; a tidy intermediate state is not the requested outcome.
Distinct from: principle-sequence-verifiable-units (ordering dependent changes into checked units), principle-migrate-callers-then-delete-legacy-apis (replacing an API and removing its transitional paths).
Done: the final artifact passes the relevant static, integration and runtime checks, and any unfinished check is reported.
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
USE WHEN writing, fixing or reviewing styling in a project that uses Tailwind CSS, even a one-class change or a request that does not name Tailwind: colours, focus rings, spacing, class names chosen by a prop, map or CVA variants, theme tokens and dark mode in the Tailwind stylesheet or tailwind.config, setup or upgrades (if unsure whether the project uses Tailwind, check package.json or the main stylesheet first); NOT WHEN writing plain CSS or Sass in a project without Tailwind; produces class names Tailwind can find, syntax for the installed major version, visible focus indicators, and no unrequested dependency or invented brand value.
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
USE WHEN changing the logic, data, props, state, Effects or rendered text of a React component, hook or page, even a one-line change; NOT WHEN the request is styling only (class names, Tailwind, CSS, dark mode, spacing, shadows) or tests only, or when it models submit, in-flight, loading, retry or failure states, even for a named React form (xstate covers that, including its React wiring); applies React 19 composition, state, Effect, structure, API and performance rules with only the project's installed libraries.
react-testing
USE WHEN writing, fixing or reviewing a React Testing Library test for a component, hook or context provider, even one small test, or when asked for an end-to-end journey inside a Vitest or React Testing Library suite; NOT WHEN changing the component itself (react), testing XState actors or @xstate/react (xstate), or writing a Playwright or Cypress test; covers renderHook, providers, async results, forms and false-pass anti-patterns, and declines end-to-end journeys with the testable slices.