菜单
Test fixture — produced SKILL.md sets a `data-*-color-scheme` attribute in the root-entry-file code block. Hard Rules cites `shell/mode-attribute-no-theme-import` to pair the attribute with a theme import, but no row appears in produced anti-patterns.md. Cross-check must FAIL.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | produced-skill |
| description | Test fixture — produced SKILL.md sets a `data-*-color-scheme` attribute in the root-entry-file code block. Hard Rules cites `shell/mode-attribute-no-theme-import` to pair the attribute with a theme import, but no row appears in produced anti-patterns.md. Cross-check must FAIL. |
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" data-ds-color-scheme="dark">
<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 |
|---|---|---|
| button asks | references/components/button.md | per-component file |
var(--ds-surface-default) via the <BaseSurface style> prop OR body { background-color: ... } 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.<html data-ds-color-scheme="<mode>"> MUST be paired with the matching theme CSS import (@import "ds-themes/<mode>.css";). The attribute sets the resolution context; the import provides the values — see shell/mode-attribute-no-theme-import.[VERIFY] marker inline.After generating UI: cite each component used; confirm shell parity.
In scope: tokens, assets, component descriptions, component APIs.
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).