Design technical changes with Mermaid diagrams and acceptance criteria.
npx skills add https://github.com/garethrhughes/fragile --skill architect-garethrhughes
Please help me install this Agent Skill. Skill: architect Source: https://github.com/garethrhughes/fragile/tree/main/.opencode/skills/architect Command: npx skills add https://github.com/garethrhughes/fragile --skill architect-garethrhughes
This Skill helps teams decide how to build significant changes before implementation starts, reducing architectural drift, rework, and hidden operational risk.
Use the architect skill to draft a proposal for a significant change, including system boundaries, trade-offs, Mermaid diagrams, and verifiable acceptance criteria.
High-intent search queries and answers about installing and using this skill.
A technical design proposal evaluates system boundaries, data flow, and trade-offs before code ships. You need one for significant backend, infrastructure, or API changes that could affect maintainability, security, or operational cost.
Draft an architecture proposal by defining module boundaries, evaluating infrastructure topology, and adding Mermaid diagrams. The proposal includes trade-off analysis, impact assessments, open questions, and verifiable acceptance criteria.
Yes, you can design API contracts and database schema changes using this proposal-first workflow. It evaluates cross-cutting concerns, documents assumptions, and records impact across frontend, tests, and security before implementation begins.
The best way to document trade-offs for infrastructure changes is a structured proposal that compares alternatives, surfaces edge cases, and records impact across database, frontend, tests, and security while enforcing project architecture constraints.
Yes, proposal-first design applies to observability updates and release strategy planning. It produces proposal-ready design decisions, impact assessments, and acceptance criteria to reduce architectural drift and hidden operational risk.
Writing a design proposal before coding reduces rework and architectural drift by forcing teams to evaluate module boundaries, identify edge cases, and define acceptance criteria before implementation starts, preventing hidden operational risk.
HechaoYannetGenerate a master architecture document from GDDs, ADRs, and governance constraints.
anishi1222Analyze Azure resource groups and generate Mermaid topology diagrams.
Andre-cardiaDesign and optimize PostgreSQL database architectures with RLS policies and migrations.
EdgeHuntBrainstorm architectures with trade-off analysis and explicit decision criteria.
