菜单
Explore the current project across its tooling, context, and codebase. Use to survey what is installed, see what is available, or find which skill, agent, or rule fits a goal. Not for choosing the next step or running an item; it only points.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Initialize or refresh the project memory bank. Use when the user wants to set up or regenerate the project's memory files. Not for updating one memory file after it exists or editing a single rule directly.
Guide a project's journey through AIDD, from first setup to shipping a feature. Use when the user says onboard me, where do I start, or what to do next. Not for listing every installed surface.
Design and validate a new SaaS's architecture into an INSTALL.md via Q&A and stack comparison. Use when the user starts a project, chooses a stack, or picks an architecture pattern. Not for editing an existing stack or scaffolding code.
Route a request to generate a context artifact (skill, rule, agent, command, or hook) to its generator when the kind is unnamed. A named kind triggers its generator directly. Not for listing existing artifacts.
Generate a router-based skill across the host AI tools a project uses. Use when the user wants to create, scaffold, or refactor a skill, or turn a workflow into one. Not for other artifacts like rules, agents, commands, hooks.
Generate a coding rule that governs editor and agent behavior across the host AI tools. Use when the user wants to write, add, or refactor a rule, convention, or coding standard. Not for other artifacts like skills, agents, or hooks.
| name | 11-explore |
| description | Explore the current project across its tooling, context, and codebase. Use to survey what is installed, see what is available, or find which skill, agent, or rule fits a goal. Not for choosing the next step or running an item; it only points. |
| argument-hint | survey | drill |
Surveys the current project across three axes so the user sees what is there and can dig into any of them. It maps the project, it never prescribes a next step.
| # | Action | Role | Input |
|---|---|---|---|
| 01 | survey | Scan the three axes and present a compact map | project root |
| 02 | drill | Descend one axis or all, level by level, match an intent if any | a scope or a goal |
Detect the project's AI tools first, from the signals in references/ai-mapping.md. Then route by what the user asked: no scope given runs survey for a compact map, a named axis or "all" runs drill straight away. Always propose the axes when the request is open, never assume one. Run each action's ## Test before the next.
Before running an action, read its file in actions/, not only the table or assets.
references/ai-mapping.md.references/ai-mapping.md: the per-tool signals, scan paths, and formats for the Tooling and Context axes.