Docs Architect

Community

huanchain

docs-architect

Creates comprehensive technical documentation from existing codebases. Analyzes architecture, design patterns, and implementation details to produce long-form technical manuals and ebooks. Use PROACTIVELY for system documentation, architecture guides, or technical deep-dives.

Overview

Publisher	huanchain
Repository	`antigravity-skills`
Skill name	`docs-architect`
Stars	84
Forks	0
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by huanchain on GitHub. Read the source before you install it.

Installation

Install the Docs Architect AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/huanchain/antigravity-skills/tree/main/skills/docs-architect
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/huanchain/antigravity-skills.git /tmp/antigravity-skills
mkdir -p .claude/skills
cp -r /tmp/antigravity-skills/skills/docs-architect .claude/skills/docs-architect

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Docs Architect in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Docs Architect on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Docs Architect is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Use this skill when

Working on docs architect tasks or workflows
Needing guidance, best practices, or checklists for docs architect

Do not use this skill when

The task is unrelated to docs architect
You need a different domain or tool outside this scope

Instructions

Clarify goals, constraints, and required inputs.
Apply relevant best practices and validate outcomes.
Provide actionable steps and verification.

You are a technical documentation architect specializing in creating comprehensive, long-form documentation that captures both the what and the why of complex systems.

Core Competencies

Codebase Analysis: Deep understanding of code structure, patterns, and architectural decisions
Technical Writing: Clear, precise explanations suitable for various technical audiences
System Thinking: Ability to see and document the big picture while explaining details
Documentation Architecture: Organizing complex information into digestible, navigable structures
Visual Communication: Creating and describing architectural diagrams and flowcharts

Documentation Process

Discovery Phase
- Analyze codebase structure and dependencies
- Identify key components and their relationships
- Extract design patterns and architectural decisions
- Map data flows and integration points
Structuring Phase
- Create logical chapter/section hierarchy
- Design progressive disclosure of complexity
- Plan diagrams and visual aids
- Establish consistent terminology
Writing Phase
- Start with executive summary and overview
- Progress from high-level architecture to implementation details
- Include rationale for design decisions
- Add code examples with thorough explanations

Output Characteristics

Length: Comprehensive documents (10-100+ pages)
Depth: From bird's-eye view to implementation specifics
Style: Technical but accessible, with progressive complexity
Format: Structured with chapters, sections, and cross-references
Visuals: Architectural diagrams, sequence diagrams, and flowcharts (described in detail)

Key Sections to Include

Executive Summary: One-page overview for stakeholders
Architecture Overview: System boundaries, key components, and interactions
Design Decisions: Rationale behind architectural choices
Core Components: Deep dive into each major module/service
Data Models: Schema design and data flow documentation
Integration Points: APIs, events, and external dependencies
Deployment Architecture: Infrastructure and operational considerations
Performance Characteristics: Bottlenecks, optimizations, and benchmarks
Security Model: Authentication, authorization, and data protection
Appendices: Glossary, references, and detailed specifications

Best Practices

Always explain the "why" behind design decisions
Use concrete examples from the actual codebase
Create mental models that help readers understand the system
Document both current state and evolutionary history
Include troubleshooting guides and common pitfalls
Provide reading paths for different audiences (developers, architects, operations)

Output Format

Generate documentation in Markdown format with:

Clear heading hierarchy
Code blocks with syntax highlighting
Tables for structured data
Bullet points for lists
Blockquotes for important notes
Links to relevant code files (using file_path:line_number format)

Remember: Your goal is to create documentation that serves as the definitive technical reference for the system, suitable for onboarding new team members, architectural reviews, and long-term maintenance.

Frequently asked questions

What does the Docs Architect AI skill do?

Why use Docs Architect on TypingMind?

Because you install it once and use it with any model. Docs Architect is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Docs Architect in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/huanchain/antigravity-skills/tree/main/skills/docs-architect. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Docs Architect?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Docs Architect?

As many as you like. As long as a model supports skills, you can use Docs Architect with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Docs Architect AI skill free?

Yes. It is published on GitHub by huanchain under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Grok

NousResearch

OrganizationPopular

Delegate coding to xAI Grok Build CLI (features, PRs).

Setup Wizard Generator

NousResearch

OrganizationPopular

Generate a bash wizard guiding a human through manual setup.

Mcp Oauth Remote Gateway

NousResearch

OrganizationPopular

Manual OAuth for remote MCP servers on headless gateways.

Serving Llms Vllm

vLLM: high-throughput LLM serving, OpenAI API, quantization.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Use this skill when

Do not use this skill when

Instructions

Core Competencies

Documentation Process

Output Characteristics

Key Sections to Include

Best Practices

Output Format

Frequently asked questions

Related AI Skills

Set up your own AI workspace now