Menu
Test fixture — produced-skill mode, Setup section cites a docs URL. WIRING_NOT_SYNTHESIZED must PASS.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Execute a unit of work end-to-end: understand, implement, validate with typecheck and build, then commit. Use when the user wants to do work, build a feature, fix a bug, or implement an issue or phase from a plan. Do NOT use for design-system skill extraction — that flow has its own meta-skill (extract-ds-skill).
Test fixture — produced-skill mode, ships a references/design-craft.md that was paraphrased during persist instead of copied verbatim (a NEVER dropped, a MUST softened). DESIGN_CRAFT must FAIL on the byte-diff and cite craft/regenerated-not-copied.
Test fixture — meta-skill self-mode, full three-phase shape but missing the per-phase handoff-emission prose. HANDOFF_EMISSION must report FAIL.
Test fixture — meta-skill self-mode. discovery.md handoff template carries both required sections but hedges a foundation sub-page with "if confirmed". HANDOFF_COMPLETENESS must report FAIL (state/handoff-out-of-scope-deferred).
Test fixture — meta-skill self-mode. discovery.md handoff template has a `## Decisions` block but NO `## Components proposed` section. HANDOFF_COMPLETENESS must report FAIL (state/handoff-missing-component-shape).
Test fixture — meta-skill self-mode with the three-phase shape, the phase-N.md handoff-write prose, and the dryrun-label labeling section all present, but missing the cutoff prose at Phase 1 close and Phase 2 close. HANDOFF_EMISSION must report FAIL and the failure messages must cite state/inline-phase-transition (the handoff write IS referenced and the dryrun-label prose IS present, but the post-write inline transition is the failure mode).
| name | produced-skill |
| description | Test fixture — produced-skill mode, Setup section cites a docs URL. WIRING_NOT_SYNTHESIZED must PASS. |
Lift the wiring verbatim from https://acme.example.com/docs/getting-started:
import { ThemeProvider } from 'acme-react'
export default function RootLayout({ children }) {
return (
<html lang="en">
<body>
<ThemeProvider>{children}</ThemeProvider>
</body>
</html>
)
}
| Trigger | Files to load | Notes |
|---|---|---|
| user composes a screen, page, or section layout | references/design-craft.md | DS-agnostic design-craft defaults, shipped verbatim by the meta-skill — the DS wins on conflict |
| button asks | references/components/button.md | per-component file |
<ThemeProvider> MUST wrap children, not render as a sibling. Provider context only reaches descendants, so any token-derived var(--<surface-default>) resolution depends on the wrap.In scope: tokens, assets, component descriptions, component APIs.