cli-forge-arch
Skill5 starsChanged 8 months agoMITView on GitHub
Router for architecture design. Detects whether the user needs an HLD or LLD and delegates to the appropriate skill. Use when the user says 'design doc', 'architecture', or is ambiguous about HLD vs LLD. For explicit HLD requests, use cli-forge-hld directly. For explicit LLD requests, use cli-forge-lld directly.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- murillo-consulting/cli-skillsedited, first seen Oct 20, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- murillo-consulting/cli-skills★ 098% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository40 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .cursor/rules/cli-audit-code.mdcCursor rule
- .cursor/rules/cli-audit-doc.mdcCursor rule
- .cursor/rules/cli-forge-arch.mdcCursor rule
- .cursor/rules/cli-forge-schema.mdcCursor rule
- cli-audit-codeSkill
- cli-audit-dataSkill
- cli-audit-docSkill
- cli-audit-driftSkill
- cli-audit-hanoiSkill
- cli-audit-reviewSkill
- cli-audit-shellSkill
- cli-audit-syncSkill
- cli-audit-tangleSkill
- cli-audit-testSkill
- cli-audit-wizardSkill
- cli-audit-xraySkill
- cli-cycleSkill
- cli-forge-chefSkill
- cli-forge-choice-uxSkill
- cli-forge-dataSkill
- cli-forge-demoSkill
- cli-forge-docSkill
- cli-forge-githubSkill
- cli-forge-hldSkill
- cli-forge-infraSkill
- cli-forge-lldSkill
- cli-forge-oci-rootlessSkill
- cli-forge-perfSkill
- cli-forge-pipelineSkill
- cli-forge-plumeSkill
- cli-forge-prezSkill
- cli-forge-profileSkill
- cli-forge-quorumSkill
- cli-forge-readmeSkill
- cli-forge-resilienceSkill
- cli-forge-schemaSkill
- cli-forge-treeSkill
- cli-git-conventionalSkill
- cli-watermarkSkill
The file
Files
Language rule: Skill instructions are written in English. When generating user-facing output, detect the project's primary language (from README, comments, docs, commit messages) and produce the document in that language. If the project is bilingual, ask the user which language to use before proceeding.
Gotchas — read ../gotchas.md before producing output to avoid known mistakes.
Arch Router — HLD / LLD Dispatcher
This skill has been split into two focused skills. Route the user's request accordingly:
Routing Table
| Signal in user's request | Delegate to |
| "HLD", "system design", "architecture", "C4 context/container", "capacity", "back-of-envelope", "ATAM", "Gate review", "design proposal" | /cli-forge-hld |
| "LLD", "detailed design", "class diagram", "sequence diagram", "API spec", "DB schema", "component design", "STRIDE", "threat model" | /cli-forge-lld |
| "design doc", "tech spec" (ambiguous) | Ask the user: "Do you want a high-level design (system architecture, C4 L1-L2, capacity estimation, ADRs) or a low-level design (class diagrams, API contracts, DB schemas, sequence diagrams)?" |
| Both mentioned | Produce HLD first, then LLD for each key container |
What changed
The original cli-forge-arch combined HLD and LLD in a single skill. This caused issues:
- Users asking for HLD got LLD-level detail (class diagrams, DB schemas) they didn't need
- Users asking for LLD got HLD-level context (system diagrams, capacity) that was redundant
- The skill was too large to produce focused, high-quality output
New skills:
cli-forge-hld— C4 L1-L2, capacity estimation, ADRs, ATAM tradeoff analysis, deployment architecturecli-forge-lld— C4 L3-L4, class/sequence/state diagrams, API contracts, DB schemas, STRIDE, testability
The references/ directory is preserved here for backward compatibility but the canonical references now live in each skill's own references/ directory.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.