The Best Architecture and System Design Skills for Claude Code

Architecture is the category where a skill's value is easiest to judge: either it produces an artifact you can review, or it produces paragraphs you already knew.

The architecture skills in our directory split cleanly into two groups: generalists that produce a design document, and specialists bound to a particular stack or problem domain. The specialists score well but only apply in a narrow band; the generalists are the safer install.

The skills worth installing

cloud-architect — 9.4 · Design & Creative

Cloud architecture, migration planning, and cost optimization. What makes it useful is the output shape: a design with cost implications, not just a diagram. Migration planning is where most architecture advice stops being generic.

rag-architect — 9.3 · Documents

Production RAG: chunking strategy, embedding choices, retrieval evaluation. This is the most concrete specialist on the list — RAG has enough specific failure modes (chunk boundaries, recall vs precision, evaluation sets) that a general architecture skill cannot substitute.

architecture-designer — 9.2 · Developer Tools

High-level system design and review of existing designs. The generalist baseline: boundaries, data flow, trade-offs. If you want one architecture skill and have no specific stack, start here.

microservices-architect — 9.1 · Writing

Distributed systems and monolith decomposition into bounded contexts. Useful when the question is specifically "how do I split this", which is a different question from "what should the architecture be".

java-architect — 9.1 · Productivity

Enterprise Java architecture and configuration. Framework-bound, so only relevant if that is your stack.

graphql-architect — 9.0 · Design & Creative

GraphQL schema design, Apollo Federation, and resolver architecture. Again a specialist — but GraphQL schema design has conventions that a general skill will get wrong.

Generalist or specialist

The pattern across this set is consistent: specialists score roughly the same as generalists, so the decision should be made on fit, not on score. cloud-architect at 9.4 does not mean it is better than architecture-designer at 9.2 — it means it is better at cloud migration specifically.

The one exception is rag-architect, which is worth installing alongside a generalist if you are building retrieval. The domain has enough specific mechanics that the overlap is small.

How to choose

• No specific stack? architecture-designer, then stop.
• Cloud migration or cost? cloud-architect.
• Building retrieval? Add rag-architect; it earns its score.
• Framework-bound architects (java-architect, graphql-architect) — only if that is what you ship.

Architecture skills compose well with diagram skills: the design reasoning lives in the architect, the rendering in the diagram tool. The design category covers the visualization half.