Skip to content
Skill category

Software Architecture and Planning skills

Agent skills for architecture, API design, domain-driven design, specs and task plans. Compare methods that settle design choices before an agent writes code.

43 skills

About Software Architecture and Planning

An agent that starts coding from a one-line request will make design choices on its own, and those choices are costly to undo. The skills here move the thinking earlier: interview you about the goal, write a spec, record the trade-offs and break the work into ordered tasks.

The category has two halves. Architecture skills cover system design, clean architecture, domain-driven design, API and GraphQL design, microservices and data-intensive systems, many of them distilled from well-known books. Planning skills cover interviews, specs, implementation plans, ticket breakdowns and architecture decision records, so the reasoning stays in the repository after the session ends.

When choosing, match the skill to the size of the decision. A quick API design checklist is enough for a single endpoint, while a new service calls for a skill that produces diagrams, written trade-offs and a decision record. Look at what the skill outputs and where it saves it, since a spec in a tracker and a spec in a markdown file feed different workflows. Book-based rule sets work best as background guidance and may need trimming to fit your codebase.

A good starting pair is one interview or spec skill and one architecture skill that fits your stack, with a task breakdown skill to hand the result to an implementer.

Showing 31 of 43 skillsNetwork Shell Git Clear all
Model-led108 tokens in use

Domain-Driven Design Distilled

3,324

Software Architecture And Planning

Vaughn Vernon-inspired rules for subdomains, bounded contexts and small aggregates with the least DDD ceremony that works.

Skill
33idle
108in use
3,514up to
Tokens, counted offlineView skill
Model-led110 tokens in use

Implementing Domain-Driven Design

3,324

Software Architecture And Planning

Vaughn Vernon-inspired rules for building aggregates, repositories, domain events and application services in code.

Skill
32idle
110in use
3,881up to
Tokens, counted offlineView skill
Model-led124 tokens in use

Patterns of Enterprise Application Architecture

3,324

Software Architecture And Planning

Martin Fowler-inspired rules for choosing layers, service layers, domain models, mappers, units of work and DTOs.

Skill
37idle
124in use
4,475up to
Tokens, counted offlineView skill
Model-led5,283 tokens in use

app-lifecycle

687

Software Architecture And Planning

The detailed SaaS path from idea to production: eleven stages, each with its output and a done-when, grouped into phases the owner can try, with shape switches and owner decisions.

Skill
42idle
5,283in use
32,319up to
Tokens, counted offlineView skill
Model-led1,408 tokens in use

document-app

687

Software Architecture And Planning

Writes or refreshes an app's system docs from its code (architecture, flows, permissions, variables), or checks existing docs against the code and reports disagreements.

Skill
39idle
1,408in use
1,408up to
Tokens, counted offlineView skill
Model-led3,188 tokens in use

propose

687

Business And Startup Strategy · Software Architecture And Planning

Research an idea, then propose what to build in one HTML page with sourced claims, key screens, open decisions and a recommendation.

Skill
41idle
3,188in use
5,311up to
Tokens, counted offlineView skill
Model-led2,475 tokens in use

shipping-artifacts

687

Software Architecture And Planning

Defines the small set of documents that make an AI-built app reviewable: architecture, flows, permissions, variables, a coverage map and conditional docs for email, cron, SEO and agents.

Skill
36idle
2,475in use
2,573up to
Tokens, counted offlineView skill

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers