Genesis Documentation

Automatically document your codebase with AI-powered analysis

Genesis is Quoth's automated documentation system. It analyzes your codebase and creates structured documentation that AI agents can use to understand your project.

How Genesis Works

1

Configuration - Genesis asks about your preferred documentation depth

2

Analysis - Your AI tool reads local files using its native capabilities

3

Documentation - Each document is created and uploaded incrementally

4

Indexing - Documents are embedded for semantic search

Depth Levels

Genesis offers three depth levels to match your documentation needs:

LevelDocumentsTimeBest For
minimal3~3 minQuick overview, prototypes
standard5~7 minTeam onboarding, regular development
comprehensive11~20 minEnterprise audit, full documentation

Minimal (3 Documents)

  • project-overview.md - High-level system overview
  • tech-stack.md - Dependencies and frameworks
  • repo-structure.md - Directory organization

Standard (5 Documents)

Everything in minimal, plus:

  • coding-conventions.md - Code style and patterns
  • testing-patterns.md - Test structure and examples

Comprehensive (11 Documents)

Everything in standard, plus:

  • api-schemas.md - REST/GraphQL endpoints
  • database-models.md - Tables and relations
  • shared-types.md - TypeScript interfaces
  • error-handling.md - Error patterns
  • security-patterns.md - Auth and validation
  • tech-debt.md - Known issues and improvements

Running Genesis

Run Genesis as a skill or ask Claude directly:

/quoth:genesis

Or: "Run Genesis with comprehensive depth"

Genesis respects your .gitignore and won't document sensitive files like .env or node_modules.

Updating Documentation

Genesis creates initial documentation, but keeping it current is important. You have three options:

The Quoth daemon automatically detects stale docs and updates them nightly:

  • Tracks content hashes (SHA-256) of every source file referenced in each doc
  • Compares hashes nightly — detects real content changes
  • Uses Kimi K2.5 to generate incremental updates to affected sections
  • Auto-bumps version (1.0.0 → 1.0.1), commits, and pushes to git
  • Reports changes at the next session start (once, never repeated)

No manual intervention needed.

Manual Incremental Updates

Re-run Genesis with update_only focus to refresh only changed sections:

"Run Genesis with update_only focus to refresh documentation"

Full Regeneration

Re-run Genesis to rebuild all docs from scratch:

"Run Genesis to fully regenerate documentation"

Best Practices

Start Small

Begin with minimal depth, expand as needed

Keep Current

Run Genesis after major changes

Review Output

Verify generated docs match your project