メニュー
Prepare or execute a parallel Codex implementation only when the user explicitly requests `/implement`, parallel work, multiple agents, or an implementation handoff for this repository.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/skitsanos/dutchy-design-system --skill implementコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Audit Dutchy Bun SSR pages and components for accessibility, keyboard, semantics, ARIA, focus, and theme contrast issues. Use for accessibility, WCAG, keyboard, or screen-reader reviews in this repository.
Add a Dutchy Design System component with its Bun SSR JSX, optional vanilla JavaScript behavior, demo route, registry entry, documentation, styling source, and focused verification.
Audit Dutchy Bun SSR routes for native controls or layout markup that should use existing design-system components, and verify required client-side handlers and selector contracts.
SKILL.md を表示中
| name | implement |
| description | Prepare or execute a parallel Codex implementation only when the user explicitly requests `/implement`, parallel work, multiple agents, or an implementation handoff for this repository. |
Use this workflow only for explicit parallel or multi-agent requests. Ordinary implementation requests should be handled directly.
Read AGENTS.md, the requested specification, a relevant existing implementation, shared integration files, and available checks. Identify independently owned file groups and dependencies between them.
Do not split the work when it is concentrated in one shared file, requires unresolved architecture decisions, or has fewer than two genuinely independent work streams.
When Codex multi-agent tools are available and the user requested execution, create bounded work units with:
Reserve registries, navigation, shared configuration, and final integration for one owner after dependent work lands. Avoid review-only agents and overlapping write scopes.
When multi-agent tools are unavailable, provide the same work units as copy-ready handoff prompts. State coordination points and integration order clearly.
Finish by integrating results, resolving conflicts without discarding user changes, running repository checks, and reporting any incomplete work.
