Architecture

Skill uncfreak1255-code/sawyer-skills-legacy/.claude/skills/architecture

Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.From its SKILL.md

Install

npx -y skills add uncfreak1255-code/sawyer-skills-legacy --skill architecture

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.7 KB, 322 tokens by cl100k_base, as published. Nobody here has run it

Architecture Decision Framework

"Requirements drive architecture. Trade-offs inform decisions. ADRs capture rationale."

🎯 Selective Reading Rule

Read ONLY files relevant to the request! Check the content map, find what you need.

File	Description	When to Read
`context-discovery.md`	Questions to ask, project classification	Starting architecture design
`trade-off-analysis.md`	ADR templates, trade-off framework	Documenting decisions
`pattern-selection.md`	Decision trees, anti-patterns	Choosing patterns
`examples.md`	MVP, SaaS, Enterprise examples	Reference implementations
`patterns-reference.md`	Quick lookup for patterns	Pattern comparison

🔗 Related Skills

Skill	Use For
`@[skills/database-design]`	Database schema design
`@[skills/api-patterns]`	API design patterns
`@[skills/deployment-procedures]`	Deployment architecture

Core Principle

"Simplicity is the ultimate sophistication."

Start simple
Add complexity ONLY when proven necessary
You can always add patterns later
Removing complexity is MUCH harder than adding it

Validation Checklist

Before finalizing architecture:

Requirements clearly understood
Constraints identified
Each decision has trade-off analysis
Simpler alternatives considered
ADRs written for significant decisions
Team expertise matches chosen patterns

What ships with it: 5 files

10.3 KB alongside SKILL.md

Gives 0 of the 12 instructions most architecture codebase skills give in 322 tokens

Counted across 858 of the 1,304 authors here whose files we hold, read 2026-09-06

Apply the deletion test to identify shallow modulesin 32 of 858, across 31 files
Read domain glossary and ADRs before exploringin 22 of 858, across 19 files
Use Tailwind and Mermaid via CDN for reportsin 21 of 858, across 18 files
Document architecture decision recordsin 20 of 858, across 12 files
Offer to record ADRs for rejected candidatesin 17 of 858, across 14 files
Limit primary navigation to four to seven itemsin 17 of 858, across 7 files
Write HTML report to the system temp directoryin 17 of 858, across 14 files
Read product marketing context before asking questionsin 16 of 858, across 6 files
Use Mermaid graph TD for visual sitemapsin 15 of 858, across 5 files
Ensure every page has at least one internal linkin 15 of 858, across 5 files
Use ASCII tree format for page hierarchy draftsin 15 of 858, across 5 files
Enforce lowercase URLs with hyphensin 15 of 858, across 5 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.