Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/keminghe/common-devx/living-design-documentsnpx skills add KemingHe/common-devx --skill living-design-documentsgit clone --depth 1 https://github.com/KemingHe/common-devxWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/keminghe/common-devx/living-design-documents)<a href="https://agentmods.dev/skills/keminghe/common-devx/living-design-documents"><img src="https://agentmods.dev/badge/skills/keminghe/common-devx/living-design-documents.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00055 | $0.04037 |
| Opus 5 | $0.00028 | $0.02018 |
| Sonnet 5 | $0.00011 | $0.00807 |
| Haiku 4.5 | $0.00006 | $0.00404 |
Grade A, and why
living-design-documents scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 328 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Living Design Documents
Create and maintain three living design documents that guide development through structured design thinking. Core Decisions capture load-bearing policies. Taxonomy provides detailed specifications. Parked holds deferred analysis. Documents graduate upward as maturity increases.
Temporary persona: Senior engineering PM with expertise in structured design and AI-native documentation.
When to Use This Skill
- New project setup requiring initial design structure
- Design decisions needed during development
- Complexity growing and requiring documentation
- Audit due (7 days for solo projects, 30 days for team projects since Last Audited date)
- User triggers: "design docs", "LDD", "core decisions", "taxonomy", "parked decisions"
Asset Resolution
- Check
./assets/design-*-template.md(skill-local) - If not found, search
**/design-*-template.mdin repository - If still not found, generate from scratch following the template structure in this skill
Simple vs Complex Project Adaptation
Templates default to simple project pattern. Adapt based on project complexity:
| Project Type | Core Decisions | Taxonomy | Parked |
|---|---|---|---|
| Simple (single-focus) | design-core-decisions.md |
design-taxonomy.md |
design-parked.md |
| Complex (multi-component) | design-core-decisions.md |
design-taxonomy-[component].md |
design-parked-[component].md |
Detection heuristics:
- Simple: <5 major components, single team, focused purpose
- Complex: 5+ components, multiple teams, or distinct bounded contexts
Template adaptation examples for complex projects:
| Element | Simple (template default) | Complex (agent adapts) |
|---|---|---|
| Taxonomy filename | design-taxonomy.md |
design-taxonomy-api.md |
| Taxonomy title | # Design - Taxonomy |
# Design - Taxonomy - API |
| Parked filename | design-parked.md |
design-parked-api.md |
| Parked title | # Design - Parked |
# Design - Parked - API |
| Taxonomy NOTE links | ./design-parked.md |
./design-parked-api.md, ./design-taxonomy-database.md |
| Parked NOTE links | ./design-taxonomy.md |
./design-taxonomy-api.md |
| References section | Omit cross-component links | Add cross-component section anchors |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 328 lines · 55 tokens per session scan A 7fab18b377f7
living-design-documents is a skill published in the GitHub repository KemingHe/common-devx (10 stars, last pushed 3mo ago), licensed MIT. It adds 55 tokens to every session and 4,037 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
developer-marketing-playbook
Complete developer marketing playbook covering DevRel programs, documentation as marketing, API developer experience, community building, and hackathon strategy. For dev-tool founders who need to reach engineers. Follow @WeiYipei on X.
doc-bridge-handoff
Resolve Doc Bridge boundaries before changing code.
Technical Documentation Writer
Write developer documentation that developers actually read. API docs, READMEs, architecture guides, and onboarding docs with clarity and structure.
openapi-designer
Design complete OpenAPI 3.1 specifications for RESTful APIs. Covers schemas, security, examples, webhooks, and documentation generation.
documentation-writer
Write clear, comprehensive technical documentation. Covers README files, API docs, tutorials, architecture guides, and documentation systems.
golden-rss
Use when testing the rss golden build.