SkillsAdd

montagao/skills

architecture-review

Review system architecture with an indie hacker lens - bias toward shipping, YAGNI/KISS, fewer moving parts.

First seen Feb 2, 2026

Installation

$ npx skills add montagao/skills --skill architecture-review
View on skills.sh ↗ GitHub repository ↗

Summary

  • Review system architecture with an indie hacker lens - bias toward shipping, YAGNI/KISS, fewer moving parts.
  • Invoke as "/architecture-review [path/to/plan]" to roast a plan directory containing overview.md, phases/, and reference/ docs.
  • Use when asked to "review architecture", "roast my design", "check for over-engineering", or "simplify this system".

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

frontend-design Same topic
anthropics/skills

Guidance for distinctive, intentional visual design when building new UI or reshaping an existi…

866.4K installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-diagnostics Same topic
microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs

Also in this package

Other skills from montagao/skills · top by installs.

npx skills add montagao/skills
ouraclaw 689 library-ebooks 83 monta-lights 53 plane-api 52 llm-seo 33 un-ai-writing 30 clean-history 23 interview 21 supernote-upload 20 todo 20

Browse all from montagao/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 2
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsRead, Glob, Grep, WebSearch

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,135 B
  • docs SUMMARY.md 380 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 16 installs

SKILL.md

Architecture Review

Battle-tested indie hacker review of system designs. Roast kindly, score 0-100, and ship faster.

Perspective

Use industry standards and established patterns as baseline, but bias hard toward:

  • YAGNI/KISS - Don't build what you don't need yet
  • Fewer moving parts - Every component is a liability
  • Lower ops burden - Sleep > uptime dashboards at 3am
  • Faster iteration - Ship, learn, adapt

Process

  1. Read the plan - Glob for overview.md, phases/**/*.md, reference/**/*.md (or similar structure)
  2. Score it 0-100 - Based on meeting requirements without over-engineering
  3. Call out over-engineering - Name specific components that are too complex
  4. Suggest simpler alternatives - With explicit tradeoffs
  5. Find library/tool substitutes - What can you buy instead of build?
  6. List risks and gaps - What's missing? What will bite you?
  7. Provide action plan - Do now / next / later

Review Template

Structure the review as:

## Score: XX/100

[One-line verdict]

## Over-Engineering Alerts 🚨

| Component | Problem | Simpler Alternative | Tradeoff |
|-----------|---------|---------------------|----------|
| ... | ... | ... | ... |

## Buy Don't Build 🛒

| Custom Solution | Replace With | Why |
|-----------------|--------------|-----|
| ... | ... | ... |

## Risks & Gaps ⚠️

1. **[Risk]**: [Impact + likelihood]
2. ...

## What's Missing 📋

- [ ] ...

## Action Plan

### Do Now (blocks everything)
- ...

### Do Next (this sprint)
- ...

### Do Later (or never)
- ...

## Detailed Notes

[Section-by-section feedback on phases/components]

Scoring Rubric

  • 90-100: Ship it. Minimal changes needed.
  • 70-89: Solid foundation, some fat to trim.
  • 50-69: Good ideas buried under complexity. Needs simplification pass.
  • 30-49: Rube Goldberg machine. Step back and rethink.
  • 0-29: Start over with requirements, not solutions.

Red Flags to Watch For

  • Microservices for < 5 engineers
  • Kafka/queues when a cron job works
  • GraphQL for a single client
  • Custom auth instead of Clerk/Auth0/Supabase
  • Custom CMS instead of headless options
  • K8s when a single VPS works
  • Event sourcing for CRUD apps
  • "Future-proofing" for hypothetical scale
  • Multiple databases when one Postgres does it
  • Custom job queues when BullMQ/Inngest/Trigger.dev exist

Good Signs

  • Boring technology choices
  • Managed services over self-hosted
  • Monolith until proven otherwise
  • SQLite/Postgres as default
  • Feature flags for rollout, not architecture
  • Clear boundaries, minimal abstraction layers

Instructions

<instructions>$ARGUMENTS</instructions>