write-docs
Skill336 starsChanged 10 months agoMITView on GitHub
Write documentation with real, validated examples. Executes commands through the user to capture actual output. Use for any new documentation or major doc updates.
45 other projects use a version of this.
Adopted by
Most recently taken up by
- iammrduncan/skillstheir own version, first seen Nov 16, 2026
- dzhng/skillstheir own version, first seen Nov 15, 2026
- develeep/dev-gongbangtheir own version, first seen Nov 15, 2026
- karlo-ks/Infradecktheir own version, first seen Nov 15, 2026
- dzhng/jevgreptheir own version, first seen Nov 11, 2026
- alchemy-run/alchemy-effecttheir own version, first seen Nov 9, 2026
Used with
Projects with it also use close-spec, design-with-images and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
dzhngSkillclose-spec
When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](../review/SKILL.md) (run before closing).
Also in 5 projects that use this
dzhngSkilldesign-with-images
Explore UI and visual design with image generation, then iterate the real implementation against the user-selected concept. Use when brainstorming visual directions, offering mockup variants, or implementing an approved generated design; do not stop at the mockups or the first code approximation.
Also in 5 projects that use this
transitive-bullshitSkillcompare-screenshots
Compare screenshots against the intended design, distinguishing approved references from historical baselines. Use for iterative implementation matching, before/after visual review, objective image telemetry, or checking a lone capture for flat, empty, or badly framed content.
Also in 5 projects that use this
LucasMatuszewskiSkillaudit-agents
Audit and maintain agent configuration files (.claude/agents, AGENTS.md, CLAUDE.md, agent-memory). Checks for duplicates, outdated info, naming conflicts, wrong technical facts, and files over 200 lines. Fixes all issues and commits.
Also in 5 projects that use this
wolverin0Skillaudit-decisions
Standardize remediation decisions, baseline-policy entries, and legal-review banners for accepted, deferred, or policy-blocked audit findings.
Also in 4 projects that use this
rhnfzlSkillexplore-unknowns
Walk the user through mapping the unknowns of a task before, during, and after they build it, and hand them a four-quadrant map (settled ground, open decisions, taste, and landmines) they keep. Reach for this eagerly whenever a request is ambiguous or underspecified, the codebase or domain is unfamiliar, the user will "know it when they see it", a reference implementation must be understood before porting, a build-queue or architecture-changing task is about to start, a mid-build deviation needs capturing, or a finished change needs buy-in or verified understanding before merge. Trigger even when the skill is not named: "do a blindspot pass", "find my unknown unknowns", "interview me about this change", "brainstorm the approach for a task I am about to build", "help me scope this", "what am I missing here", "plan this before I build", "I know nothing about X in this codebase". When a territory profile is present it reads memory and the graph first and feeds the map into the build pipeline; without one it degrades to a plain general map. Not for trivial or mechanical tasks with clear acceptance criteria, single-fact lookups, pure debugging of a known symptom, or pure code review, those have their own tools. Do not use it to run the build itself; the map is the deliverable and implementation remains a separate task, whether it has not started or is already underway.
Also in 5 projects that use this
- +5 more from dzhng
Other versions45 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 45
- tldraw/tldraw★ 51ksame name
- tabler/tabler★ 42ksame name
- videojs/video.js★ 40ksame name
- PrefectHQ/prefect★ 24ksame name
- comet-ml/opik★ 23ksame name
- coder/coder★ 17ksame name
- browseros-ai/BrowserOS★ 14ksame name
- Agenta-AI/agenta★ 4.9ksame name
- liveblocks/liveblocks★ 4.8ksame name
- dzhng/jevgrep★ 3.2ksame name
35 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository33 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- dot-ai-changelog-fragmentSkill
- dot-ai-generate-cicdSkill
- dot-ai-generate-dockerfileSkill
- dot-ai-impact_analysisSkill
- dot-ai-manageKnowledgeSkill
- dot-ai-manageOrgDataSkill
- dot-ai-operateSkill
- dot-ai-prd-closeSkill
- dot-ai-prd-createSkill
- dot-ai-prd-doneSkill
- dot-ai-prd-fullSkill
- dot-ai-prd-nextSkill
- dot-ai-prds-getSkill
- dot-ai-prd-startSkill
- dot-ai-prd-update-decisionsSkill
- dot-ai-prd-update-progressSkill
- dot-ai-process-feature-requestSkill
- dot-ai-projectSetupSkill
- dot-ai-query-dot-aiSkill
- dot-ai-querySkill
- dot-ai-recommendSkill
- dot-ai-remediateSkill
- dot-ai-request-dot-ai-featureSkill
- dot-aiSkill
- dot-ai-tag-releaseSkill
- dot-ai-usersSkill
- dot-ai-versionSkill
- dot-ai-worktree-prdSkill
- dot-ai-write-docsSkill
- infographic-generatorSkill
- publish-mock-serverSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
22 rules. 0 are common, 19 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 43 edited versions we read keep these.
19
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Write accurate, user-focused documentation with real examples by executing operations through the user.
- Distinctive: line 12
Execute-then-document: Never write examples without real output
- Distinctive: line 13
Chunk-by-chunk: Write one section at a time, get confirmation before proceeding
- Distinctive: line 14
User-focused: Write for users, not developers
- Distinctive: line 15
Validate prerequisites: Run setup steps from existing docs to verify they work
- Distinctive: line 17
Fix docs when broken: If existing docs don't work during setup, STOP and discuss updating those docs before proceeding.
- Distinctive: line 23
Ask the user what documentation to write.
- Distinctive: line 65
If documenting a feature not yet in published charts:
- Distinctive: line 77
Add these flags to helm install:
- Very specific: line 87
IMPORTANT: Always use KUBECONFIG=./kubeconfig.yaml for all kubectl/helm commands.
- Distinctive: line 89
If any step fails or doesn't match existing docs: STOP and discuss whether to update those docs before proceeding.
- Distinctive: line 116
MCP interactions: Ask user to send intent and share output (these are the user-facing examples we're documenting)
- Distinctive: line 132
After all sections are written:
- Distinctive: line 133
Verify internal links work
- Distinctive: line 134
Check links to other docs exist
- Very specific: line 135
Update mcp-tools-overview.md if adding a new tool guide
- Distinctive: line 136
Update any index pages
- Distinctive: line 169
Never invent output: - Always use real responses from the user
- Distinctive: line 170
Never skip validation: - Every example must be executed first
- Distinctive: line 172
Use user language: - Avoid internal/developer terminology
- Distinctive: line 173
Include error cases: - Document what happens when things go wrong
- Very specific: line 174
Full flags in commands: - Always use long-form flags (e.g., --filename not -f, --namespace not -n, --output not -o).
“Common” is measured: kept by at least 6 in 10 of the 43 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Write Documentation
Write accurate, user-focused documentation with real examples by executing operations through the user.
Principles
- Execute-then-document: Never write examples without real output
- Chunk-by-chunk: Write one section at a time, get confirmation before proceeding
- User-focused: Write for users, not developers
- Validate prerequisites: Run setup steps from existing docs to verify they work
- Claude runs infrastructure, user runs MCP: Claude executes all bash/infrastructure commands. Only ask user for MCP client interactions (the actual user-facing examples).
- Fix docs when broken: If existing docs don't work during setup, STOP and discuss updating those docs before proceeding.
Workflow
Step 1: Identify the Documentation Target
Ask the user what documentation to write. Options:
- New feature guide (e.g., "knowledge base guide")
- Update existing guide
- API reference
- Setup/configuration guide
Step 2: Fresh Environment Setup
ALWAYS start with a clean test cluster to ensure reproducible documentation.
Follow the actual docs (docs/setup/mcp-setup.md) - this validates they work.
Claude executes all infrastructure steps directly using Bash tool:
- Tear down existing test cluster if present
kind delete cluster --name dot-ai-test 2>/dev/null || true rm -f ./kubeconfig.yaml - Create fresh Kind cluster with local kubeconfig
kind create cluster --name dot-ai-test --kubeconfig ./kubeconfig.yaml export KUBECONFIG=./kubeconfig.yaml - Install prerequisites (ingress controller)
kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/main/deploy/static/provider/kind/deploy.yaml # Wait for ingress to be ready kubectl wait --namespace ingress-nginx --for=condition=ready pod --selector=app.kubernetes.io/component=controller --timeout=300s - Follow docs/setup/mcp-setup.md (skip controller if not needed for the feature)
- Step 1: Set environment variables (use existing API keys from env)
- Step 2: Install controller via Helm (skip if feature doesn't need it)
- Step 3: Install MCP server via Helm
- Step 4: Tell user to configure MCP client
- Step 5: Tell user to verify with "Show dot-ai status"
For unreleased features: Build and use local images
If documenting a feature not yet in published charts:
# Build MCP server image npm run build docker build -t dot-ai:test . kind load docker-image dot-ai:test --name dot-ai-test # Build agentic-tools plugin image docker build -t dot-ai-agentic-tools:test ./packages/agentic-tools kind load docker-image dot-ai-agentic-tools:test --name dot-ai-testAdd these flags to helm install:
--set image.repository=dot-ai \ --set image.tag=test \ --set image.pullPolicy=Never \ --set plugins.agentic-tools.image.repository=dot-ai-agentic-tools \ --set plugins.agentic-tools.image.tag=test \ --set plugins.agentic-tools.image.pullPolicy=Never
IMPORTANT: Always use KUBECONFIG=./kubeconfig.yaml for all kubectl/helm commands.
If any step fails or doesn't match existing docs: STOP and discuss whether to update those docs before proceeding.
Why fresh cluster? Ensures documentation examples work from a known clean state and validates setup docs.
Step 3: Outline the Documentation
Present an outline of sections to write. Example:
1. Overview (what it does, when to use it)
2. Prerequisites
3. Basic Usage (with real examples)
4. Advanced Features
5. API Reference
6. Troubleshooting
7. Next StepsGet user confirmation on the outline before proceeding.
Step 4: Write Chunk-by-Chunk
🚨 CRITICAL: One section at a time. NEVER write multiple sections or the whole doc at once.
For each section:
- Execute first — Run every command or ask user to run every MCP interaction that will appear in this section. Do this BEFORE writing any documentation prose.
- Bash commands: Claude runs these directly using Bash tool
- MCP interactions: Ask user to send intent and share output (these are the user-facing examples we're documenting)
- Wait for output — For MCP interactions, user shares the actual output. For bash commands, capture the real output.
- Write and apply the chunk immediately — Write the documentation section using real output and apply the edit directly (Write or Edit tool). Do NOT ask for permission — the user will cancel the edit if they want changes. Do NOT show the markdown in a code block and ask "should I write this?" — just write it.
- Proceed to next section — Move to the next section and repeat.
Key distinction: Infrastructure/setup = Claude runs it. User-facing MCP examples = User runs it and shares output.
NEVER do these:
- ❌ Write the entire document in one go
- ❌ Write multiple sections before getting confirmation
- ❌ Show proposed markdown and ask "want me to write this?"
- ❌ Write examples without executing the commands first
- ❌ Skip execution for "simple" or "standard" commands — validate everything
Step 5: Cross-Reference Check
After all sections are written:
- Verify internal links work
- Check links to other docs exist
- Update
mcp-tools-overview.mdif adding a new tool guide - Update any index pages
Step 6: Final Review
Tell the user: "Documentation complete. Please review the full file and let me know if any adjustments are needed."
Example Execution Request Formats
For MCP tool operations:
Please send this intent to your MCP client:
"Ingest this document into the knowledge base: [content] with URI: [url]"
Share the response you receive.For status checks:
Please ask: "Show dot-ai status"
Share what you see for the Vector DB collections.For bash commands:
Please run:
kubectl get pods -n dot-ai
Share the output.Important Rules
- Never invent output - Always use real responses from the user
- Never skip validation - Every example must be executed first
- Keep sections small - One concept per chunk for easy review
- Use user language - Avoid internal/developer terminology
- Include error cases - Document what happens when things go wrong
- Full flags in commands - Always use long-form flags (e.g.,
--filenamenot-f,--namespacenot-n,--outputnot-o). Full flags are more self-documenting for users unfamiliar with the tools.
File Locations
- Feature guides:
docs/guides/mcp-*-guide.md - Setup guides:
docs/setup/*.md - Tool overview:
docs/guides/mcp-tools-overview.md - Images:
docs/img/
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

