god-docs

Included with Lifetime

$97 forever

Implement and maintain the GOD doc system - a documentation strategy for multi-component repositories. Use when: (1) a task requires any code modifications or analysis, (2) adding or modifying any documentation, (3) auditing doc freshness and detecting drift

Designassets

What this skill does


# GOD Docs

Developer-facing, template-enforced, dependency-tracked, deterministically verifiable architecture documentation.

## Core Concept

GOD Docs treat documentation as a **build artifact**. Staleness is computed, not guessed. Three-level hierarchy (System → Domain → Component), template-enforced structure, declared inter-doc dependencies, and enforcement via git hooks + CI.

Full specification: `references/spec.md`

## Pre-Requisite: Domain Decomposition

Before any GOD Docs, the repo MUST be split into **non-overlapping domains**. Every source file maps to exactly ONE domain. This is what makes dirty-checking deterministic.

## Hierarchy

```
docs/GOD.md                          # Level 0: System
docs/domains/{domain}/GOD.md         # Level 1: Domain
{component}/GOD.md                   # Level 2: Component
```

## Quick Start

### Initialize in a Repo

1. Create template directory and templates:

   ```bash
   mkdir -p docs/templates docs/domains docs/sync
   ```

2. Copy templates from `assets/COMPONENT-GOD-TEMPLATE.md` and `assets/DOMAIN-GOD-TEMPLATE.md`
3. Create system-level `docs/GOD.md` — see `references/spec.md` §3 for required sections
4. Install git hook from `assets/pre-commit` → `.githooks/pre-commit`
5. Run `git config core.hooksPath .githooks`

### Create a Component GOD Doc

1. Copy template: `cp docs/templates/COMPONENT-GOD-TEMPLATE.md {component}/GOD.md`
2. Fill ALL `{{PLACEHOLDER}}` tokens — zero unfilled placeholders allowed
3. Add `<!-- GOD-DEPS: ... -->` declaring upstream GOD Docs this component depends on
4. Register in parent domain GOD Doc (component map + link)
5. Register in system GOD Doc (component registry table)
6. Verify: `grep -c "{{" {component}/GOD.md` must return 0

### Create a Domain GOD Doc

1. Copy template: `cp docs/templates/DOMAIN-GOD-TEMPLATE.md docs/domains/{domain}/GOD.md`
2. Fill all placeholders
3. List all components in this domain with links to their Level 2 GOD Docs
4. Document domain-internal and cross-domain event contracts

## Inter-GOD Dependencies

Each GOD Doc declares dependencies via HTML comment:

```markdown
<!-- GOD-DEPS:
  - event-bus
  - schema-registry
-->
```

Meaning: this component consumes events/schemas/APIs from those components. When a dependency's GOD Doc changes, this doc is transitively flagged stale.

## Dirty-Check Algorithm

```
1. Collect changed files (git diff)
2. Map files → owning component
3. If source changed but GOD.md didn't → DIRTY
4. Walk GOD-DEPS graph: dependents of DIRTY docs → TRANSITIVELY DIRTY
5. Output: all DIRTY ∪ TRANSITIVELY DIRTY
```

Two enforcement layers:

- **Git hook** (pre-commit): interactive prompt, local
- **CI action**: blocks merge on stale docs — see `references/spec.md` §6.3

## Template Required Sections

### Component GOD Doc (Level 2)

- Overview (non-technical)
- Component-Centric Architecture (Mermaid component-level diagram)
- Interfaces (CLI commands, API endpoints)
- Technical Deep-Dive (patterns, implementation)
- Development & Deployment

### Domain GOD Doc (Level 1)

- Domain Overview
- Domain-centric Architecture/Topology (Mermaid diagram)
- Component Summaries (with links to Level 2 docs)
- Cross-Component Interactions and/or Messaging
- Shared Infrastructure

### System GOD Doc (Level 0)

- System Topology (Mermaid diagram)
- Domain Reference Table
- Component Registry (name, domain, status, GOD Doc link)
- Cross-Domain Dependency Graph
- System-Wide Data Flows
- Infrastructure Requirements

## Key Principle

> If you can't cleanly decompose your repo into non-overlapping domains, GOD Docs aren't ready for you yet. Fix that first.

Files: 6

Size: 26.5 KB

Complexity: 53/100

Category: Design

Source: https://github.com/delorenj/skills/tree/main/god-docs

Related in Design

contribute

Included

Local-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".

Designscripts

architectural-analysis

Included

User-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).

Designscripts

mcp

Included

Model Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.

Designscripts

react-native-skia

Included

Design, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.

Designscripts

plaid

Included

Product Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".

Designscripts

nextjs-framer-motion-animations

Included

Adds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.

Designscripts