brainfish-ai/reasondb/create-doc
Claude Code and agent skill by brainfish-ai/reasondb
- community
Checking that the SKILL.md file is still in the repository.
Create new documentation pages interactively. Searches codebase to ensure accuracy.
Install
npx vskill@latest install brainfish-ai/reasondb/create-docSKILL.md
Instructions
When user wants to create documentation:
Step 0: Read Context
Read `.devdoc/context.json` if it exists:
- Use
product.namefor product references - Apply
terminology.glossaryfor correct terms - Use
documentation.codeExamples.primaryLanguagefor code - Read templates from
documentation.templates
Step 1: Understand What to Create
Ask the user:
"What would you like to document?
- A specific feature or concept - I'll create a guide/tutorial
- Code files or functions - Point me to the code, I'll generate docs
- API endpoints - I'll analyze your API and create reference docs
- Something else - Describe what you need"
Step 2: Gather Information
Based on their choice:
For Feature/Concept:
- "What's the topic/title?"
- "What type of page?
- Guide - Explains how to do something
- Tutorial - Step-by-step walkthrough
- Reference - Technical specifications
- Troubleshooting - Problem/solution format"
- "Any specific sections you want included?"
For Code Documentation:
- "Which files or directories should I analyze?"
- "What should I focus on?
- Public API/exports
- Internal architecture
- Usage examples
- All of the above"
- Read the specified files
- Extract functions, classes, types, examples
For API Documentation:
- Check for existing OpenAPI/GraphQL specs
- If found: "I found
{spec}. Should I generate docs from it?" - If not: "Point me to your API routes/controllers"
- Extract endpoints, parameters, responses
For Other:
- Ask clarifying questions
- Understand the scope and purpose
Step 3: Search Codebase (CRITICAL - No Hallucination)
ALWAYS search and read actual files before generating content:
3a. Search for Relevant Files
3b. Read the Files Found
For each relevant file:
- Read the file - Get actual implementation
- Extract key info:
- Function signatures and parameters
- Type definitions
- Error codes and messages
- Code examples from tests
3c. Assess Information Sufficiency
3d. Handle Insufficient Information
If files not found, present options:
3e. Detect Feature Flags & Duplicates
Search for feature flags:
Search for duplicate/similar features:
Flag findings for user guidance:
3f. Show What Was Found
Step 4: Choose Template
Read the appropriate template from .devdoc/templates/:
| Content Type | Template | |
|---|---|---|
| How-to guide | guide.md | |
| Tutorial | tutorial.md | |
| API endpoint | api-reference.md | |
| Quick start | quickstart.md | |
| FAQ/Issues | troubleshooting.md |
Step 5: Draft Content (From Real Files Only)
CRITICAL: Only use data from files you actually read.
Draft the documentation (DO NOT WRITE YET):
- Read the template for structure guidance
- Apply context (terminology, voice, language)
- Use ONLY data from searched files:
- Get exact function signatures from source files
- Get type definitions from actual type files
- Reference examples from test files or examples folder
- Document errors from error handling code
- Include mermaid diagrams for flows/architecture
- Add real code examples copied from codebase
- Use proper MDX components (Steps, Cards, Tabs, etc.)
- Cite sources - Note which files info came from
- Mark feature flags - Note conditional features
- Note duplicates - Reference related/similar features
NEVER generate content without reading source files first.
Step 6: Review Content with User (MANDATORY)
ALWAYS show the complete draft for user review before writing:
import { login } from '@package/auth';
const token = await login('user@example.com', 'password');
Step 7: Propose File Location
After content approval, suggest where to save:
"I'll create this page at: docs/guides/{topic}.mdx
Does this location work, or would you prefer somewhere else?"
Step 8: Create and Update Navigation
Only after user approves content AND location:
- Write the MDX file
- Ask: "Should I add this to the navigation in docs.json?"
- If yes, update docs.json with the new page
Step 9: Summary
"Created:
docs/guides/{topic}.mdx- {description}- Updated
docs.jsonnavigation
Preview with npm run dev
Want me to create another page or make changes to this one?"
Code Documentation Examples
From TypeScript/JavaScript:
Generates:
import { validateToken } from '@package/auth';
const isValid = validateToken(userToken); if (!isValid) { throw new Error('Invalid token'); }
From Python:
Generates similar documentation following the template structure.
Key Principles
| Principle | Description | |
|---|---|---|
| Search before generate | ALWAYS search/read files before writing | |
| No hallucination | Only use data from actual source files | |
| Review before write | ALWAYS show draft to user for approval | |
| Flag feature flags | Detect and highlight conditional features | |
| Flag duplicates | Identify similar/related features | |
| Use mermaid diagrams | Visualize architecture, flows, sequences | |
| Cite sources | Note which files information came from |
Quality Guidelines
- SEARCH FIRST - Never generate without reading source files
- REVIEW WITH USER - Always show draft before creating file
- DETECT FEATURE FLAGS - Search for conditional features
- DETECT DUPLICATES - Find similar functions/features
- Extract real code examples from actual files
- Flag insufficient info and offer auto-correct options
- Include error handling from source code
- Add TODO markers for sections needing human review
- Link to related documentation
- Apply terminology from context.json
- Cite source files in frontmatter
Mermaid Diagram Requirements
ALWAYS include mermaid diagrams for:
| Content Type | Diagram | Example | |
|---|---|---|---|
| Architecture | flowchart TB | System components | |
| Data flow | flowchart LR | Request processing | |
| API calls | sequenceDiagram | Auth flow | |
| State machine | stateDiagram-v2 | Lifecycle | |
| Data models | erDiagram | Database schema |
Example for architecture docs:
Example for API docs:
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingdocs/.claude/skills/create-doc/SKILL.md
Popularity
- Repository stars
- 61
- Repository forks
- 3
- 7-day trend score
- 20
Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 24 Mar 2026, 7 months ago.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/brainfish-ai/reasondb/create-doc)