菜单
Use when starting substantive work to choose the right workflow skill without adding unnecessary ceremony to trivial interactions
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Explore ideas and create designs before implementation
Use when about to claim work is complete or before committing - enforces verification and proposes a commit
Fetch current library and framework documentation from Context7 instead of relying on training data
Use when you have a written implementation plan to execute - direct execution by default, subagents for complex tasks
Use when encountering any bug, test failure, or unexpected behavior — find root cause before proposing any fix
Use when implementing any feature or bugfix, before writing implementation code
| name | using-expert-mode |
| description | Use when starting substantive work to choose the right workflow skill without adding unnecessary ceremony to trivial interactions |
| compatibility | opencode |
| license | MIT |
Choose the smallest correct workflow for the user's request. Use skills to structure substantive work, not to add ceremony to trivial interactions.
Before substantive work, follow this flow:
For trivial interactions, respond directly.
Load a skill before:
Usually respond directly for:
brainstorming: explore a design before implementationwriting-plans: turn approved requirements into an implementation planexecuting-plans: carry out an existing plan task by tasksystematic-debugging: investigate bugs or failing tests root-cause-firsttest-driven-development: implement behavior starting from a failing testcompleting-work: verify status before claiming successcontext7-mcp: fetch current official documentationLoad only what you need now. If the task changes shape, load the next relevant skill at that point.