jdanigo/hydraia / skills/greenfield-architect
greenfield-architect
VerifiedGreenfield Architect — design the system before the first line
Runs in the MAIN session (interactive). The "app from scratch" route of the Hydraia pipeline: everything here happens BEFORE the normal Phase 2 spec, and feeds it.
Flow
- Elicit (in this order, one question each, skip what the request already answers):
- Problem + primary users — what pain, who feels it.
- Scale honesty — expected users/data/requests as ranges (10? 10k? 10M?). Push back on fantasy numbers.
- Constraints — team size and skills (weighs heavily on stack), budget, deploy target (cloud/on-prem/serverless), compliance (PII? payments? health?).
- Non-functional requirements — latency targets, availability, security posture.
- Integration landscape — what existing systems it must talk to.
- Architecture proposal. Dispatch the
architectagent (system shape, trade-offs) andcode-architectagent (concrete file/interface blueprint). Apply themicroservices-architectskill ONLY if elicitation produced evidence for a split. Present 2–3 shapes with trade-offs and one recommendation. - Stack recommendation. Anchored to elicited constraints — team skills first, ecosystem fit second, hype never. Confirm with the human. Name the Phase 4 pattern skill that will govern implementation (react-patterns / node-patterns / dotnet-patterns / golang-patterns / springboot-patterns / python-patterns).
- API surface. If the system exposes an API, run the api-design skill now — the contract file becomes part of the spec.
- Record decisions. Architecture shape, stack, data store, auth approach, hosting — each gets an ADR via the adr skill, committed with the spec.
- Hand off to the normal pipeline: Phase 2 spec references the ADRs by number and embeds/links the contract; Phases 3–6 run unchanged.
Anti-patterns to refuse
- Microservices for a 2-person team "to be ready for scale" → monolith + ADR with the split trigger.
- Choosing the stack the model likes over the stack the team knows.
- Designing for 10M users when elicitation said 500.
- Skipping the API contract because "we can document it later".
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: 197k | 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 |