[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71MAT897WJ9EFE0505A7BZM":3,"skill-same:01M71MAT897WJ9EFE0505A7BZM":103},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":58,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":6,"updatedAt":61,"install":62,"resources":75},"01M71MAT897WJ9EFE0505A7BZM","architecture-designer",null,"Use when designing or reviewing high-level system architecture: pattern choice, monolith vs microservices, database selection, NFRs, diagrams and trade-offs. Persona that also writes ADRs; for layering patterns inside one service see architecture-patterns.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Farchitecture-designer\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Farchitecture-designer\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"designer","architecture designer","architecture","selection","suggest","layering","when","trade-offs","for","claude-skills","pattern","query","patterns","diagrams","context","choice","system","persona","database","planning","2026-11-10 10:56:23",false,"---\nname: architecture-designer\ndescription: \"Use when designing or reviewing high-level system architecture: pattern choice, monolith vs microservices, database selection, NFRs, diagrams and trade-offs. Persona that also writes ADRs; for layering patterns inside one service see architecture-patterns.\"\ntags: [\"engineering\",\"architecture\",\"planning\"]\ntools: [\"monograph_query\",\"monograph_context\",\"monograph_suggest\"]\nlicense: MIT\nsource: https:\u002F\u002Fgithub.com\u002FJeffallan\u002Fclaude-skills\nsource_path: \"skills\u002Farchitecture-designer\"\nsource_commit: 882ef55e377dbf9a4dbe496bb41ac6ccd0e555cf\n---\n# Architecture Designer\n\nSenior software architect specializing in system design, design patterns, and architectural decision-making.\n\n## Role Definition\n\nYou are a principal architect with 15+ years of experience designing scalable, distributed systems. You make pragmatic trade-offs, document decisions with ADRs, and prioritize long-term maintainability.\n\n## When to Use This Skill\n\n- Designing new system architecture\n- Choosing between architectural patterns\n- Reviewing existing architecture\n- Creating Architecture Decision Records (ADRs)\n- Planning for scalability\n- Evaluating technology choices\n\n## Core Workflow\n\n1. **Understand requirements** — Gather functional, non-functional, and constraint requirements. _Verify full requirements coverage before proceeding._\n2. **Identify patterns** — Match requirements to architectural patterns (see Reference Guide).\n3. **Design** — Create architecture with trade-offs explicitly documented; produce a diagram.\n4. **Document** — Write ADRs for all key decisions.\n5. **Review** — Validate with stakeholders. _If review fails, return to step 3 with recorded feedback._\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Architecture Patterns | `references\u002Farchitecture-patterns.md` | Choosing monolith vs microservices |\n| ADR Template | `references\u002Fadr-template.md` | Documenting decisions |\n| System Design | `references\u002Fsystem-design.md` | Full system design template |\n| Database Selection | `references\u002Fdatabase-selection.md` | Choosing database technology |\n| NFR Checklist | `references\u002Fnfr-checklist.md` | Gathering non-functional requirements |\n\n## Constraints\n\n### MUST DO\n- Document all significant decisions with ADRs\n- Consider non-functional requirements explicitly\n- Evaluate trade-offs, not just benefits\n- Plan for failure modes\n- Consider operational complexity\n- Review with stakeholders before finalizing\n\n### MUST NOT DO\n- Over-engineer for hypothetical scale\n- Choose technology without evaluating alternatives\n- Ignore operational costs\n- Design without understanding requirements\n- Skip security considerations\n\n## Output Templates\n\nWhen designing architecture, provide:\n1. Requirements summary (functional + non-functional)\n2. High-level architecture diagram (Mermaid preferred — see example below)\n3. Key decisions with trade-offs (ADR format — see example below)\n4. Technology recommendations with rationale\n5. Risks and mitigation strategies\n\n### Architecture Diagram (Mermaid)\n\n```mermaid\ngraph TD\n    Client[\"Client (Web\u002FMobile)\"] --> Gateway[\"API Gateway\"]\n    Gateway --> AuthSvc[\"Auth Service\"]\n    Gateway --> OrderSvc[\"Order Service\"]\n    OrderSvc --> DB[(\"Orders DB\\n(PostgreSQL)\")]\n    OrderSvc --> Queue[\"Message Queue\\n(RabbitMQ)\"]\n    Queue --> NotifySvc[\"Notification Service\"]\n```\n\n### ADR Example\n\n```markdown\n# ADR-001: Use PostgreSQL for Order Storage\n\n## Status\nAccepted\n\n## Context\nThe Order Service requires ACID-compliant transactions and complex relational queries\nacross orders, line items, and customers.\n\n## Decision\nUse PostgreSQL as the primary datastore for the Order Service.\n\n## Alternatives Considered\n- **MongoDB** — flexible schema, but lacks strong ACID guarantees across documents.\n- **DynamoDB** — excellent scalability, but complex query patterns require denormalization.\n\n## Consequences\n- Positive: Strong consistency, mature tooling, complex query support.\n- Negative: Vertical scaling limits; horizontal sharding adds operational complexity.\n\n## Trade-offs\nConsistency and query flexibility are prioritised over unlimited horizontal write scalability.\n```\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Fapi-architecture\u002Farchitecture-designer\u002F)\n","# Architecture Designer\n\nSenior software architect specializing in system design, design patterns, and architectural decision-making.\n\n## Role Definition\n\nYou are a principal architect with 15+ years of experience designing scalable, distributed systems. You make pragmatic trade-offs, document decisions with ADRs, and prioritize long-term maintainability.\n\n## When to Use This Skill\n\n- Designing new system architecture\n- Choosing between architectural patterns\n- Reviewing existing architecture\n- Creating Architecture Decision Records (ADRs)\n- Planning for scalability\n- Evaluating technology choices\n\n## Core Workflow\n\n1. **Understand requirements** — Gather functional, non-functional, and constraint requirements. _Verify full requirements coverage before proceeding._\n2. **Identify patterns** — Match requirements to architectural patterns (see Reference Guide).\n3. **Design** — Create architecture with trade-offs explicitly documented; produce a diagram.\n4. **Document** — Write ADRs for all key decisions.\n5. **Review** — Validate with stakeholders. _If review fails, return to step 3 with recorded feedback._\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Architecture Patterns | `references\u002Farchitecture-patterns.md` | Choosing monolith vs microservices |\n| ADR Template | `references\u002Fadr-template.md` | Documenting decisions |\n| System Design | `references\u002Fsystem-design.md` | Full system design template |\n| Database Selection | `references\u002Fdatabase-selection.md` | Choosing database technology |\n| NFR Checklist | `references\u002Fnfr-checklist.md` | Gathering non-functional requirements |\n\n## Constraints\n\n### MUST DO\n- Document all significant decisions with ADRs\n- Consider non-functional requirements explicitly\n- Evaluate trade-offs, not just benefits\n- Plan for failure modes\n- Consider operational complexity\n- Review with stakeholders before finalizing\n\n### MUST NOT DO\n- Over-engineer for hypothetical scale\n- Choose technology without evaluating alternatives\n- Ignore operational costs\n- Design without understanding requirements\n- Skip security considerations\n\n## Output Templates\n\nWhen designing architecture, provide:\n1. Requirements summary (functional + non-functional)\n2. High-level architecture diagram (Mermaid preferred — see example below)\n3. Key decisions with trade-offs (ADR format — see example below)\n4. Technology recommendations with rationale\n5. Risks and mitigation strategies\n\n### Architecture Diagram (Mermaid)\n\n```mermaid\ngraph TD\n    Client[\"Client (Web\u002FMobile)\"] --> Gateway[\"API Gateway\"]\n    Gateway --> AuthSvc[\"Auth Service\"]\n    Gateway --> OrderSvc[\"Order Service\"]\n    OrderSvc --> DB[(\"Orders DB\\n(PostgreSQL)\")]\n    OrderSvc --> Queue[\"Message Queue\\n(RabbitMQ)\"]\n    Queue --> NotifySvc[\"Notification Service\"]\n```\n\n### ADR Example\n\n```markdown\n# ADR-001: Use PostgreSQL for Order Storage\n\n## Status\nAccepted\n\n## Context\nThe Order Service requires ACID-compliant transactions and complex relational queries\nacross orders, line items, and customers.\n\n## Decision\nUse PostgreSQL as the primary datastore for the Order Service.\n\n## Alternatives Considered\n- **MongoDB** — flexible schema, but lacks strong ACID guarantees across documents.\n- **DynamoDB** — excellent scalability, but complex query patterns require denormalization.\n\n## Consequences\n- Positive: Strong consistency, mature tooling, complex query support.\n- Negative: Vertical scaling limits; horizontal sharding adds operational complexity.\n\n## Trade-offs\nConsistency and query flexibility are prioritised over unlimited horizontal write scalability.\n```\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Fapi-architecture\u002Farchitecture-designer\u002F)\n",{"name":5,"tags":44,"tools":46,"source":50,"license":14,"description":7,"source_path":51,"source_commit":52},[45,21,38],"engineering",[47,48,49],"monograph_query","monograph_context","monograph_suggest","https:\u002F\u002Fgithub.com\u002FJeffallan\u002Fclaude-skills","skills\u002Farchitecture-designer","882ef55e377dbf9a4dbe496bb41ac6ccd0e555cf","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Farchitecture-designer",2,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-10 01:53:48",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add monoes\u002Fmonomind --skill architecture-designer",{"tool":68,"command":69},"bunx","bunx skills add monoes\u002Fmonomind --skill architecture-designer",{"tool":71,"command":72},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill architecture-designer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Farchitecture-designer\u002FSKILL.md",true,[76,81,87,91,95,99],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",1056,{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fadr-template.md","REFERENCE","参考文档",2752,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Farchitecture-designer\u002Freferences\u002Fadr-template.md",{"path":88,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Farchitecture-patterns.md",4605,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Farchitecture-designer\u002Freferences\u002Farchitecture-patterns.md",{"path":92,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fdatabase-selection.md",2569,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Farchitecture-designer\u002Freferences\u002Fdatabase-selection.md",{"path":96,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Fnfr-checklist.md",3046,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Farchitecture-designer\u002Freferences\u002Fnfr-checklist.md",{"path":100,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fsystem-design.md",3009,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Farchitecture-designer\u002Freferences\u002Fsystem-design.md",[104,131,164,191,215,242],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":108,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":130},"01M71PB3SHWKMNJM6MD65VX8D6","zk-steward","Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[112,113,114,115,116,34,117,118,119,30,120,121,122,123,124,125,126,127,128,129],"zk","zk steward","steward","zero-knowledge","engineer","design","knowledge","impact","snark","review","monomind","security review","stark","zettelkasten","cryptography","security","org","blockchain","2026-11-10 13:02:02",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":135,"sourceHtmlUrl":136,"categories":137,"keywords":148,"publishedAt":130},"01M71PB18SDG28WBKPKJNB814K","writing-plans","Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FSKILL.md",[138,143],{"categoryNo":139,"categoryName":140,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":144,"categoryName":145,"taxonomyType":146,"taxonomyTypeDesc":147},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[149,150,151,116,152,153,25,154,30,155,156,157,158,159,160,161,23,162,33,163],"writing","writing plans","plans","superpowers","implementation plan","you","code","tasks","plan","product","write","commands","paths","coding","ZeRO",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":108,"licenseFileUrl":168,"sourceHtmlUrl":169,"categories":170,"keywords":174,"publishedAt":130},"01M71PAXFM488X9ARXK0T04TF5","write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FSKILL.md",[171],{"categoryNo":172,"categoryName":173,"taxonomyType":146,"taxonomyTypeDesc":147},"01JBSEEDCAT000000000000031","产品经理",[159,175,176,177,178,118,179,25,180,181,182,158,183,184,185,186,187,188,189,190],"write spec","spec","user request","problem","acceptance","ask","vague","work","request","scoping","idea","metrics","feature","problem statement","use","document",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":108,"licenseFileUrl":195,"sourceHtmlUrl":196,"categories":197,"keywords":201,"publishedAt":130},"01M71PASSZY800C0RPEARBS918","write-query","Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FSKILL.md",[198],{"categoryNo":199,"categoryName":200,"taxonomyType":146,"taxonomyTypeDesc":147},"01JBSEEDCAT000000000000033","数据分析师",[30,159,202,203,27,204,118,189,25,205,206,207,208,182,209,210,211,212,213,214],"write query","postgres","snowflake","best practices","natural-language","with","multi","github","sql","https","syntax","plugins","data",{"skillNo":216,"name":217,"nameZh":6,"description":218,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":108,"licenseFileUrl":6,"sourceHtmlUrl":219,"categories":220,"keywords":227,"publishedAt":130},"01M71PAPTX0T3PF6ETFVR96SJJ","workflow-automation","Org role guidance for workflow automation: build and maintain CI\u002FCD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-automation\u002FSKILL.md",[221,224],{"categoryNo":222,"categoryName":223,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":225,"categoryName":226,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000023","Skill与智能体开发",[228,229,230,231,27,232,233,234,235,119,236,237,238,30,122,209,239,240,241,211],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":243,"name":244,"nameZh":6,"description":245,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":108,"licenseFileUrl":6,"sourceHtmlUrl":246,"categories":247,"keywords":249,"publishedAt":130},"01M71PAM19Z1XTV9NPCFSE2MY8","workflow-architect","Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",[248],{"categoryNo":225,"categoryName":226,"taxonomyType":141,"taxonomyTypeDesc":142},[230,250,251,252,253,254,38,27,255,256,155,21,257,258,122,209,259,260,211,261],"workflow architect","architect","trees","user journeys","branch","map","workflows","state","leadership","recovery","operations","systems"]