菜单
Optional code-navigation aid for large or unfamiliar codebases. Use during the plan or implement phases to map module dependencies, find where a symbol is defined and used, and orient before making changes. This is a navigation helper only — it is NOT the memory layer. Skip for small projects.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Persistent memory layer across sessions. Use to recall prior context at the start of work, to store checkpoints at phase boundaries, and to answer "what did we decide / do before" questions. Backed by the agentmemory server (local SQLite + vector embeddings) on port 3111, with an MCP-only fallback. Every phase skill calls this to survive /clear and compaction boundaries.
Phase 4 of the SDLC, used ONLY for user-facing features. Use this to produce UI/UX design documentation and a persistent design system before implementation. Triggers when tasks.md exists and the spec marked a UI surface. Coordinates with the ui-ux-pro-max skill to generate design-system/MASTER.md and per-page specs. Skip entirely for CLI tools, libraries, or backend-only work.
Phase 5 of the SDLC. Use this to write code that satisfies the tasks, strictly test-first (TDD). Triggers when tasks.md exists and design is done or not needed. Implements one task at a time, writing a failing test before code, then making it pass, then refactoring. Persists progress to memory after each task so work survives session boundaries.
Master coordinator for the full software development lifecycle. Use this when starting a new feature or project, when the user is unsure which phase to run, when resuming work after a break, or to establish/edit the project constitution. Routes to specify, plan, tasks, design, implement, review, and ship phases in the correct order and enforces that no phase is skipped. ALWAYS consider this skill first at the start of any development work.
Phase 2 of the SDLC. Use this to decide HOW a specified feature will be built — architecture, tech choices, data model, API contracts, and trade-offs. Triggers after a spec exists and the user wants a technical plan or design decisions. Produces specs/<feature>/plan.md plus Architecture Decision Records (ADRs). Must read spec.md and memory/constitution.md and respect their constraints.
Phase 6 of the SDLC. Use this to verify the implementation against the spec's acceptance criteria and the project constitution before shipping. Triggers when implementation is complete. Produces specs/<feature>/review.md — a filled acceptance checklist with pass/fail per criterion and required fixes. Does not ship; gates whether ship is allowed.
| name | code-graph |
| description | Optional code-navigation aid for large or unfamiliar codebases. Use during the plan or implement phases to map module dependencies, find where a symbol is defined and used, and orient before making changes. This is a navigation helper only — it is NOT the memory layer. Skip for small projects. |
Adapted from safishamsi/graphify. Builds a lightweight dependency/symbol map to orient in
big codebases. Not persistent memory — use memory-manager for that.
/plan on an existing large codebase → map current architecture before proposing changes./implement when a task touches unfamiliar modules → find definitions and call sites first.memory-manager.Допоміжний інструмент навігації для великих кодових баз: граф залежностей, пошук визначень/використань символів, оцінка впливу змін. Це НЕ памʼять — для памʼяті є memory-manager. Для маленьких проєктів не потрібен.