メニュー
Test fixture — produced-skill ships ≥1 Hard Rule referencing body/root/provider + a surface token AND the cited shell/<slug> resolves to a Layer B row in produced anti-patterns.md. SHELL_INVARIANTS must PASS.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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 ships ≥1 Hard Rule referencing body/root/provider + a surface token AND the cited shell/<slug> resolves to a Layer B row in produced anti-patterns.md. SHELL_INVARIANTS must PASS. |
Source: <reference-project> @ src/app/layout.tsx
import { ThemeProvider, BaseSurface } from 'ds-react'
import './globals.css'
export default function RootLayout({ children }) {
return (
<html lang="en">
<body>
<ThemeProvider>
<BaseSurface style={{ backgroundColor: 'var(--ds-surface-default)' }}>
{children}
</BaseSurface>
</ThemeProvider>
</body>
</html>
)
}
@import "ds-themes/light.css";
body {
background-color: var(--ds-surface-default);
color: var(--ds-text-default);
}
| 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 |
var(--ds-surface-default) via either the <BaseSurface style> prop OR body { background-color: var(--ds-surface-default); color: var(--ds-text-default); } in globals.css. A token-painted component on an unpainted shell is the canonical mode-mismatch bug — see references/anti-patterns.md shell/unpainted-body.<ThemeProvider> MUST wrap children, not render as a sibling — provider context only reaches descendants, see shell/provider-missing-content-wrap.[VERIFY] marker inline.After generating UI: cite each component used to its source file; list any [VERIFY] markers; name the screen-level prompt built; AND confirm shell parity: the page/root surface paints with var(--ds-surface-default); the provider wraps children, not siblings.
In scope: tokens, assets, component descriptions, component APIs.