Technical design documents for significant architecture decisions.

Each design doc covers the problem, proposed solution, alternatives considered, and trade-offs. Design docs are written before implementation begins.

Creating a design doc

Run the Design Doc Writer agent with an approved PRD:

claude --agent design-doc-writer

The agent will interview you about architecture decisions, research the codebase, and produce a design doc from the template. The output's Task Breakdown section feeds directly into Claude Code's plan mode for implementation.

Design Docs

• Hardened IaC Bootstrap — Helmfile-orchestrated bootstrap with Vault secrets, PSS restricted, ResourceQuota (draft, 2026-03-17)
• Autonomous Security Improvement Loop — Bash wrapper invoking Claude Code for iterative Mac workstation hardening with adversarial verification (draft, 2026-03-18)
• Security Improvement Log — Structured log of autonomous security improvements
• Pai Improvements — Markdown-backed memory MCP, active recall via pai-recaller sub-agent, 1-min commitment scheduler, browser automation. Single-user Discord assistant on Claude Max OAuth (draft, 2026-05-08)
• Blog Redesign: Agent-Native Design System — Token-driven Tailwind v4 @theme system, Radix + shadcn owned components in TSX, Storybook 10 workshop/docs/visual-tests, dark mode by token swap, autonomous verification gate; replaces MUI/Emotion/styled-components (draft, 2026-06-13)