design-architecture
Reviews the current codebase architecture and proposes improvements using four parallel specialist subagents: System Architect, Software Architect, Data Architect, and an Adversarial Architect that red-teams failure paths, LLM adversarial output scenarios, silent corruption risks, and invariant bypasses. Each subagent independently analyzes the codebase from their domain perspective, then their findings are consolidated into a living `architecture.md` file with a tracked to-do list and change log. Use this skill whenever the user asks to review, analyze, audit, or improve the architecture — or
npx skills add SenolIsci/mykg --skill design-architecture --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Design Architecture Skill This skill performs a structured architecture review by dispatching four specialist subagents in parallel, then consolidating their findings into a maintained `architecture.md` document. One of the four subagents is a dedicated adversarial red-team agent that probes failure paths, invariant bypasses, and silent corruption scenarios that the structural review agents would not naturally surface. The goal is not to produce a one-time report — it's to maintain a living architectural record that evolves as the codebase evolves. The to-do list inside `architecture.md` becomes the actionable roadmap. --- ## Workflow ### Step 1 — Read existing architecture.md (if it exists) Before spawning subagents, check whether `architecture.md` already exists in the project root. If it does, read it so you understand what was previously documented, what to-dos are already tracked, and what changes have already been logged. This context shapes what the subagents should focus on (new ground vs. follow-up on prior findings). ### Step 2 — Spawn four subagents in parallel Launch all four at once (same message, parallel Agent tool calls). Each subagent is defined in `.claude/agent
- Workflow
- Step 1 — Read existing architecture.md (if it exists)
- Step 2 — Spawn four subagents in parallel
- Step 3 — Consolidate findings
- Step 4 — Write or update architecture.md
- Step 5 — Report back to the user
- Maintaining architecture.md over time
- Notes on the mykg codebase
What does the design-architecture skill do?
Reviews the current codebase architecture and proposes improvements using four parallel specialist subagents: System Architect, Software Architect, Data Architect, and an Adversarial Architect that red-teams failure paths, LLM adversarial output scenarios, silent corruption risks, and invariant bypasses. Each subagent independently analyzes the codebase from their domain perspective, then their findings are consolidated into a living `architecture.md` file with a tracked to-do list and change log. Use this skill whenever the user asks to review, analyze, audit, or improve the architecture — or
How do I install it?
Run `npx skills add SenolIsci/mykg --skill design-architecture --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From SenolIsci/mykg, a repository with 63 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.