メニュー
Draft a user experience specification for a requested CoC feature. Use when planning new features, designing user flows, or creating UX specs for the CoC dashboard, CLI, server, or Node packages.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | draft |
| description | Draft a user experience specification for a requested CoC feature. Use when planning new features, designing user flows, or creating UX specs for the CoC dashboard, CLI, server, or Node packages. |
Draft a user experience specification for the requested feature or ask. Include:
User Story: Who is the user and what problem are they solving?
Entry Points: How does the user discover and access this feature?
User Flow: Step-by-step walkthrough of the primary workflow
Edge Cases & Error Handling:
Visual Design Considerations:
Settings & Configuration:
Discoverability: How will users learn about this feature?
Focus on clarity and simplicity. Prefer conventions already established in CoC. No code details.
Comprehensive reference for CoC (Copilot of Copilot) architecture — server, memory system, LLM tools, SDK wrapper, process store, workflow engine, deep-wiki, and dashboard SPA. Use whenever the user asks anything related to CoC (Copilot of Copilot), forge, deep-wiki, coc-client, the CoC server, dashboard, workflow engine, memory system, LLM tools, process store, or any of their subsystems. Also use whenever you need background knowledge to answer a question, plan a change, or ground your reasoning in this codebase — read the relevant reference file(s) under `references/` before responding. Use when building, modifying, debugging, or explaining CoC features, or when understanding how subsystems interact.
Submit a single commit or a range of commits as a new GitHub pull request. Cherry-picks the commits onto a fresh branch off the latest origin/main, pushes, opens the PR via `gh`, and enables auto-merge by default. On any cherry-pick/rebase conflict the script aborts the entire submit; the AI must NOT attempt to resolve conflicts. Use when the user asks to "open a PR for this commit", "send commits X..Y as a PR", "PR-ify these commits", or similar.
Schedule recurring follow-up messages into the current conversation. Supports fixed-interval monitoring and one-shot wakeups for dynamic self-pacing.
MUST BE LOADED for any code change in this repository. Implements the requested code change and adds comprehensive test coverage, ensuring tests pass across Linux, macOS, and Windows. Use whenever you are about to modify, add, refactor, fix, or delete source code in this repo — including bug fixes, feature work, refactors, and small tweaks. Use when you need to execute implementation work (not just planning) and must include tests. Commit the changes to the repository after the implementation is complete.
Delegate a job from the current chat to a new conversation. Use when the user asks to delegate or hand off work.
Generate optimized YAML pipeline configurations from natural language requirements, or DAG workflow configurations for complex multi-stage processing with fan-out, fan-in, and scripting. Ask clarifying questions about task type, data source, and output format before creating pipelines. Use when users want to create, design, or build a pipeline or workflow for data processing, classification, research, or analysis tasks.
