Menu
Skill for maintaining clear, DRY, and easy-to-navigate design documents for architect agents.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Specialized agent that crafts high level designs and plans
Translates design documents and plans into code
Find one insight that eliminates multiple components - "if this is true, we don't need X, Y, or Z"
| name | maintain-designs |
| description | Skill for maintaining clear, DRY, and easy-to-navigate design documents for architect agents. |
Clarity, easy discovery, minimal redundancy, low upkeep designs with clear canonicals and minimal code.
One topic per page; one canonical per topic. Prefer deletion with consolidation instead of duplicates. Keep pages skimmable. Stay high-level and include minimal code.
List all docs with a one-line summary and note overlaps. No metadata beyond that. Cluster by theme Group loosely (e.g., UI, backend, parsing, patterns, specs). Keep flexible. Choose canonicals For overlapping topics, pick the clearest/most current as the canonical.
Pull unique, still-relevant bits into the canonical. Rewrite for skim: Title, TL;DR, When to use, How, Gotchas, Links. Split only if a page becomes unwieldy.
Delete or replace overlaps with a one-line stub linking to the canonical. Move rough-but-useful notes to a lightweight WIP area; drop the rest. Delete obsolete docs and references. Design docs should never reference plans.
Arrange under a small set of theme folders or keep flat. Use nesting sparingly and only when it clearly aids navigation.
Add or update a minimal top-level index (and optional per-theme) with curated links and one-liners. Remove drift and new duplicates.
No obvious duplicates. Everything is discoverable from a minimal index. Docs are short, skimmable, and easy to maintain.
