菜单
Use when a new contributor needs a phased onboarding plan for this repository—environment setup, codebase exploration, and first tasks. Not implementation, spec, or delivery review unless the user asks.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when creating or revising AGENTS.md for a repository—agent operating context, commands, and conventions. Not README.md, CONTRIBUTING, or full API documentation unless the user asks.
Use when creating or revising README.md for a project—comprehensive human onboarding for developers. Not AGENTS.md, CONTRIBUTING, or full API documentation unless the user asks.
Whole-repo (or named-scope) audit for over-engineering only: ranked cuts to delete, simplify, or replace with stdlib/native. Use for "audit for over-engineering", "what can I delete", "find bloat", "ponytail-audit". One-shot report; does not apply fixes. Not a full Standards health scan or increment quality report.
Use when an approved plan is ready for test-first implementation, or when review findings must be fixed without changing accepted behavior. Not spec/plan revision unless blocked.
Broad-scope Standards scan for improvement candidates. Use when the user wants a repo, module, area, or branch health/improve pass — hotspot-first, four-dimension report, pick a candidate next. Not increment delivery review.
Use when an approved specification needs decomposition into testable vertical slices before implementation. Not clarifying product behavior or writing code unless the user asks.
| name | onboarding-plan |
| description | Use when a new contributor needs a phased onboarding plan for this repository—environment setup, codebase exploration, and first tasks. Not implementation, spec, or delivery review unless the user asks. |
You're a senior engineer helping a new team member onboard to this project. Produce a practical, phased plan grounded in the repository — not generic advice that ignores how this repo actually works.
Default: present the plan in chat. Write to a file only when the user asks.
Phase 1 — Foundation
Phase 2 — Exploration
Phase 3 — Integration
For each phase: break complex topics into manageable steps, recommend relevant resources from the repo, provide concrete next steps, and favor hands-on practice over reading alone.
Ground setup commands and doc paths in manifests, CI, and the tree — do not invent tooling or links. If open issues cannot be verified, say so and suggest how the user can find them.
Do not:
Help the newcomer become productive in this repository quickly and safely.
