Framework for analyzing requirements, evaluating trade-offs, and documenting architectural decisions.
Works with
Guides context discovery through structured questions and project classification before design begins
Provides ADR templates and trade-off analysis framework for capturing decision rationale and alternatives
Includes decision trees and anti-pattern guidance for selecting appropriate architectural patterns
Emphasizes simplicity-first approach: add complexity only when proven necess
"Requirements drive architecture. Trade-offs inform decisions. ADRs capture rationale."
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 |
| Skill | Use For |
|---|---|
@[skills/database-design] |
Database schema design |
@[skills/api-patterns] |
API design patterns |
@[skills/deployment-procedures] |
Deployment architecture |
"Simplicity is the ultimate sophistication."
Before finalizing architecture:
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionarchitectureExecute the skills CLI command in your project's root directory to begin installation:
Fetches architecture from davila7/claude-code-templates and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate architecture. Access via /architecture in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
24.2K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
24.2K
stars
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
davila7/claude-code-templates
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
Registry listing for architecture matched our evaluation — installs cleanly and behaves as described in the markdown.
I recommend architecture for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added architecture from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in architecture — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
architecture fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in architecture — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend architecture for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
architecture reduced setup friction for our internal harness; good balance of opinion and flexibility.
architecture is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
architecture has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 44