메뉴
Analyze codebase and manage project documentation. Use for doc initialization, updates, summaries, codebase analysis.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Automate browsers with Puppeteer CLI scripts and persistent sessions. Use for screenshots, performance analysis, network monitoring, web scraping, form automation, JavaScript debugging.
Autoresearch is the upstream meta-framework (Udit Goenka, MIT) for autonomous goal-directed iteration with safety guardrails. Locally split into 4 specialized skills. Start here to learn the pattern, then route to the right specialized skill.
Open the ClaudeKit plans dashboard in the CLI config UI. Use for plan kanban views, progress tracking, timeline checks, and quick navigation into plan files.
UI/UX design intelligence for web and mobile: style selection, color systems, typography, layout, accessibility, interaction states, responsive behavior, forms, charts, design systems, and code review across React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, and HTML/CSS.
Interview-driven advisory skill. Analyzes a prompt or URL (GitHub issue, spec, doc), scouts the codebase, interviews the user one question at a time to reframe the problem into exact requirements and goals, then delivers honest advice: what to do, what to avoid, better alternatives, benefits and trade-offs. Use when the user asks for advice, a second opinion, a sanity check, or requirement reframing before committing to a direction.
Task router for AgentKit installs. Classifies the task, activates the right installed skills, chains them into the shortest workflow that fits, and spawns installed subagents at defined trigger points to raise output quality. Use at the start of multi-step, multi-domain, or ambiguous work, or when unsure which skill or agent applies.
| name | ak:docs |
| description | Analyze codebase and manage project documentation. Use for doc initialization, updates, summaries, codebase analysis. |
| user-invocable | true |
| when_to_use | Invoke to create, refresh, or audit project documentation. |
| category | utilities |
| keywords | ["documentation","init","update","summarize"] |
| argument-hint | init|update|summarize |
| metadata | {"author":"agentkit","version":"1.2.0"} |
Analyze codebase and manage project documentation through scouting, analysis, and structured doc generation.
IMPORTANT: Invoke "the engineer project-organization skill" skill to organize the outputs.
If invoked without arguments, use ask_user capability to present available documentation operations:
| Operation | Description |
|---|---|
init | Analyze codebase & create initial docs |
update | Analyze changes & update docs |
summarize | Quick codebase summary |
Present as options via ask_user capability with header "Documentation Operation", question "What would you like to do?".
| Subcommand | Reference | Purpose |
|---|---|---|
/ak:docs init | references/init-workflow.md | Analyze codebase and create initial documentation |
/ak:docs update | references/update-workflow.md | Analyze codebase and update existing documentation |
/ak:docs summarize | references/summarize-workflow.md | Quick analysis and update of codebase summary |
Parse $ARGUMENTS first word:
init → Load references/init-workflow.mdupdate → Load references/update-workflow.mdsummarize → Load references/summarize-workflow.mdinit)If another workflow needs to decide whether docs should be touched before
invoking docs operations, load references/documentation-management.md.
Documentation lives in ./docs directory:
./docs
├── project-overview-pdr.md
├── code-standards.md
├── codebase-summary.md
├── design-guidelines.md
├── deployment-guide.md
├── system-architecture.md
└── project-roadmap.md
Use docs/ directory as the source of truth for documentation.
When authoring or refreshing diagrams in system-architecture.md, apply /ak:tech-graph's SVG layout rules for component spacing, arrow routing, label placement, and z-index ordering. Pair with /ak:preview --diagram for visual self-review, or use /ak:tech-graph directly for publish-grade output.
IMPORTANT: Do not start implementing code.