菜单
Use when starting a brand new project from scratch and needing project structure, rules, and documentation files generated
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when explaining unfamiliar concepts, architectures, bugs, or implementation patterns. Focus on mental models, why the pattern exists, and transfer to other contexts instead of surface-level code explanation.
Write responses in a thoughtful, technically confident, collaborative engineering tone suitable for GitHub, Discord, OSS discussions, reviews, chats, and maintainer conversations.
Use when the user wants to understand existing code — what it does, why it exists, and how to recall it later. Not for teaching during implementation (use mentor-mode). Use when the user asks "what does this file do", "explain this code", or points at code they don't understand.
Use when adding project structure and rules to an existing codebase that has no CLAUDE.md or AGENTS.md
Use when wanting minimal project rules without design docs or implementation plans — just CLAUDE.md and AGENTS.md
| name | new-project |
| description | Use when starting a brand new project from scratch and needing project structure, rules, and documentation files generated |
Scaffolds CLAUDE.md, AGENTS.md, docs/design.md, and docs/plan.md for a new project.
Ask the user for:
Project context file. Keep under 80 lines.
Must include:
@AGENTS.md — import for all coding conventionsDefault aesthetic if unspecified:
All coding conventions. No overlap with CLAUDE.md. Keep under 100 lines.
Must include:
Ask user about design vision, then document:
Phased implementation with checkboxes. Commit sequence: one commit per checkbox.