[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CBSFCFGFVH31X0XCM3G0X4":3,"skill-same:01M7CBSFCFGFVH31X0XCM3G0X4":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":6,"ownerDescription":39,"updatedAt":40,"install":41,"resources":54},"01M7CBSFCFGFVH31X0XCM3G0X4","architecture-designer",null,"Use when designing new high-level system architecture, reviewing existing designs, or making architectural decisions. Invoke to create architecture diagrams, write Architecture Decision Records (ADRs), evaluate technology trade-offs, design component interactions, and plan for scalability. Use for system design, architecture review, microservices structuring, ADR authoring, scalability planning, and infrastructure pattern selection — distinct from code-level design patterns or database-only design tasks.","om-scogo\u002Fskillsh-scraper","om-scogo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160466840?v=4","01M79AWB6DFVCQ7RK70CS34B96","Om Achrekar","01M79AWB6ZM9SKR8KDH1WSSM22",0,"MIT","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fjeffallan-claude-skills\u002Farchitecture-designer\u002FSkill.md",[],[],"2026-11-15 14:19:17",false,"---\nname: architecture-designer\ndescription: Use when designing new high-level system architecture, reviewing existing designs, or making architectural decisions. Invoke to create architecture diagrams, write Architecture Decision Records (ADRs), evaluate technology trade-offs, design component interactions, and plan for scalability. Use for system design, architecture review, microservices structuring, ADR authoring, scalability planning, and infrastructure pattern selection — distinct from code-level design patterns or database-only design tasks.\nlicense: MIT\nmetadata:\n  author: https:\u002F\u002Fgithub.com\u002FJeffallan\n  version: \"1.1.1\"\n  domain: api-architecture\n  triggers: architecture, system design, design pattern, microservices, scalability, ADR, technical design, infrastructure\n  role: expert\n  scope: design\n  output-format: document\n  related-skills: fullstack-guardian, devops-engineer, secure-code-guardian, microservices-architect, code-reviewer\n---\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,"license":15,"metadata":24,"description":7},{"role":25,"scope":26,"author":27,"domain":28,"version":29,"triggers":30,"output-format":31,"related-skills":32},"expert","design","https:\u002F\u002Fgithub.com\u002FJeffallan","api-architecture","1.1.1","architecture, system design, design pattern, microservices, scalability, ADR, technical design, infrastructure","document","fullstack-guardian, devops-engineer, secure-code-guardian, microservices-architect, code-reviewer","main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fjeffallan-claude-skills\u002Farchitecture-designer",1,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper","https:\u002F\u002Fgithub.com\u002Fom-scogo","SDE-1 @ Scogo ","2026-07-18 12:22:46",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill architecture-designer",{"tool":47,"command":48},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill architecture-designer",{"tool":50,"command":51},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill architecture-designer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fjeffallan-claude-skills\u002Farchitecture-designer\u002FSkill.md",true,[55],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"metadata.json","REFERENCE","参考文档",484,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fjeffallan-claude-skills\u002Farchitecture-designer\u002Fmetadata.json",[62,69,74,81,86,93],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7D6MC9FAAEV4CMNYX8W7JTG","arxiv-search","Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002Fskills\u002Farxiv-search\u002FSKILL.md",[],[],{"skillNo":70,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7D4ZTCS4DR3CE4JY06X84T2","working-with-legacy-code","Safely change and test untested codebases using Feathers' \"Working Effectively with Legacy Code\". Use when the user mentions \"legacy code\", \"no tests\", \"untested codebase\", \"how do I test this\", \"seams\", \"characterization tests\", \"golden master\", \"sprout method\", \"afraid to change this code\", \"monster method\", \"dependency breaking\", or \"inherited a messy codebase\". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout\u002Fwrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002Fworking-with-legacy-code\u002FSKILL.md",[],[],{"skillNo":82,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7D4ZB4CJBFW5JE67CPH2QRV","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", \"typographic scale\", or \"the text is hard to read\". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":94,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]