astroville/sprout / .claude/skills/architecture-principles
architecture-principles
VerifiedShared software architecture principles focused on right-tool decisions, scale-readiness, and avoiding unnecessary distributed complexity.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.9 KB |
SKILL.md
View on GitHub---
name: architecture-principles
description: Shared software architecture principles focused on right-tool decisions, scale-readiness, and avoiding unnecessary distributed complexity.
compatibility: opencode
metadata:
audience: architects
purpose: reusable-guidance
---
## What I do
Provide shared architectural principles that can be loaded by agents when evaluating existing systems or designing new ones.
## Core stance
- Prefer the simplest design that credibly satisfies the requirements.
- Optimize for the right tool for the job and the right design for the job.
- Treat complexity as a cost that must justify itself.
- Favor maintainability, operability, debuggability, and team cognition.
- Preserve a credible path to scale without forcing distributed complexity too early.
## Scale-readiness without overengineering
- Do not build microservices or distributed systems by default.
- Do design systems so they can grow beyond one node when needed.
- Prefer stateless application nodes where practical.
- Prefer externalized durable state and shared coordination mechanisms.
- Design async work to be queue-friendly and idempotent.
- Avoid designs that require special singleton nodes unless they are truly necessary.
- Call out likely first bottlenecks and the incremental path to address them.
## Guardrails
- Recommend microservices only when scaling asymmetry, ownership boundaries, isolation requirements, or compliance pressures clearly justify them.
- Do not recommend rewrites without a realistic migration path.
- Do not add abstractions for hypothetical future flexibility.
- Do not recommend CQRS, event sourcing, plugin systems, or heavy orchestration unless the problem clearly demands them.
- Every recommendation should include operational implications and testing implications.
## When to use me
Use this skill when an agent needs consistent architectural judgment across brownfield analysis, greenfield design, or architecture review.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |