Best use case
ck:docs is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Analyze codebase and manage project documentation — init, update, summarize.
Teams using ck:docs should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/docs/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ck:docs Compares
| Feature / Agent | ck:docs | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Analyze codebase and manage project documentation — init, update, summarize.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Documentation Management Analyze codebase and manage project documentation through scouting, analysis, and structured doc generation. ## Default (No Arguments) If invoked without arguments, use `AskUserQuestion` 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 `AskUserQuestion` with header "Documentation Operation", question "What would you like to do?". ## Subcommands | Subcommand | Reference | Purpose | |------------|-----------|---------| | `/ck:docs init` | `references/init-workflow.md` | Analyze codebase and create initial documentation | | `/ck:docs update` | `references/update-workflow.md` | Analyze codebase and update existing documentation | | `/ck:docs summarize` | `references/summarize-workflow.md` | Quick analysis and update of codebase summary | ## Routing Parse `$ARGUMENTS` first word: - `init` → Load `references/init-workflow.md` - `update` → Load `references/update-workflow.md` - `summarize` → Load `references/summarize-workflow.md` - empty/unclear → AskUserQuestion (do not auto-run `init`) ## Shared Context 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. **IMPORTANT**: **Do not** start implementing code.
Related Skills
ck:docs-seeker
Search library/framework documentation via llms.txt (context7.com). Use for API docs, GitHub repository analysis, technical documentation lookup, latest library features.
ck:worktree
Create isolated git worktree for parallel development in monorepos.
ck:web-testing
Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.
ck:web-frameworks
Build with Next.js (App Router, RSC, SSR, ISR), Turborepo monorepos. Use for React apps, server rendering, build optimization, caching strategies, shared dependencies.
ck:web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
ck:watzup
Review recent changes and wrap up the current work session.
ck:use-mcp
Utilize MCP server tools with intelligent discovery and execution.
ck:ui-ux-pro-max
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.
ck:ui-styling
Style UIs with shadcn/ui components (Radix UI + Tailwind CSS). Use for accessible components, themes, dark mode, responsive layouts, design systems, color customization.
ck:threejs
Build 3D web apps with Three.js (WebGL/WebGPU). 556 searchable examples, 60 API classes, 20 use cases. Actions: create 3D scene, load model, add animation, implement physics, build VR/XR. Topics: GLTF loader, PBR materials, particle effects, shadows, post-processing, compute shaders, TSL. Integrations: WebGPU, physics engines, spatial audio.
ck:test
Run unit, integration, e2e, and UI tests. Use for test execution, coverage analysis, build verification, visual regression, and QA reports.
ck:template-skill
Replace with description of the skill and when Claude should use it.