The point is not that I write code with AI, but that anything requiring repeated judgement gets written down as an executable spec both people and models read.
Components & interface
· Den component library: design tokens and layout rules
· Breakpoints, mobile rules, overflow and truncation
· Component API migrations, e.g. VShadow → shadowSize
· New-page scaffolding and stylesheet conventions
· One component set shared by web, the Chrome extension and the Figma plugin
· Workaround ledger: each hack records its root cause and is deleted once the library fixes it
Connectors & services
· MCP server template: local Stdio
· MCP server template: remote SSE
· Auth, rate limiting, timeouts, error handling, test fixtures
· Read-only data connector: SQL whitelist, read-only transaction, resource caps
· Heartbeats and scheduled inspection, natural-language querying
· Cost control: per-round budget and usage records, forced wrap-up before the cap
The standards live in the Skills, and the Skills live in the repository: your team can add a rule or connect a new system themselves — no need to wait for me.