[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72ZD2B3KF3379BA8FVB6RPZ":3,"skill-same:01M72ZD2B3KF3379BA8FVB6RPZ":74},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":13,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":37,"install":38,"resources":51},"01M72ZD2B3KF3379BA8FVB6RPZ","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.","andrewthomastaylor\u002FSkills","andrewthomastaylor","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F249856925?v=4","01M72Z00NZWQPWA1TVXZPKXXWJ","01M72Z00PJ210Z6DAD1N93P2HG",0,"MIT","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Farchitecture-designer\u002FSKILL.md",[],[],"2026-11-11 15:11:14",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":14,"metadata":23,"description":7},{"role":24,"scope":25,"author":26,"domain":27,"version":28,"triggers":29,"output-format":30,"related-skills":31},"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","cb7b4065bacb4b06224de86d509ccef568f68b79","claude-skills\u002Fskills\u002Farchitecture-designer","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor","2026-05-29 06:53:07",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add andrewthomastaylor\u002FSkills --skill architecture-designer",{"tool":44,"command":45},"bunx","bunx skills add andrewthomastaylor\u002FSkills --skill architecture-designer",{"tool":47,"command":48},"pnpm","pnpm dlx skills add andrewthomastaylor\u002FSkills --skill architecture-designer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Farchitecture-designer\u002FSKILL.md",true,[52,58,62,66,70],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fadr-template.md","REFERENCE","参考文档",2752,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Farchitecture-designer\u002Freferences\u002Fadr-template.md",{"path":59,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Farchitecture-patterns.md",4605,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Farchitecture-designer\u002Freferences\u002Farchitecture-patterns.md",{"path":63,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fdatabase-selection.md",2569,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Farchitecture-designer\u002Freferences\u002Fdatabase-selection.md",{"path":67,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fnfr-checklist.md",3046,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Farchitecture-designer\u002Freferences\u002Fnfr-checklist.md",{"path":71,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fsystem-design.md",3009,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Farchitecture-designer\u002Freferences\u002Fsystem-design.md",[75,84,92,99,106,113],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M732GDQJ0CWHBAW4D7ENMA3N","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fskill-creator\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fskill-creator\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M731QVEE2QCT389Z3X1JWFVQ","humanizer-zh","去除文本中的 AI 生成痕迹。适用于编辑或审阅文本，使其听起来更自然、更像人类书写。\n基于维基百科的\"AI 写作特征\"综合指南。检测并修复以下模式：夸大的象征意义、\n宣传性语言、以 -ing 结尾的肤浅分析、模糊的归因、破折号过度使用、三段式法则、\nAI 词汇、否定式排比、过多的连接性短语。","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fhumanizer-zh\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fhumanizer-zh\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":18},"01M731AMWEC72GFFNFS55F0TTC","returns-reverse-logistics","Codified expertise for returns authorization, receipt and inspection, disposition decisions, refund processing, fraud detection, and warranty claims management. Informed by returns operations managers with 15+ years experience. Includes grading frameworks, disposition economics, fraud pattern recognition, and vendor recovery processes. Use when handling product returns, reverse logistics, refund decisions, return fraud detection, or warranty claims.","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Feverything-claude-code\u002Fskills\u002Freturns-reverse-logistics\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":18},"01M7319BJFM3CBX39C85QWSMD1","quality-nonconformance","Codified expertise for quality control, non-conformance investigation, root cause analysis, corrective action, and supplier quality management in regulated manufacturing. Informed by quality engineers with 15+ years experience across FDA, IATF 16949, and AS9100 environments. Includes NCR lifecycle management, CAPA systems, SPC interpretation, and audit methodology. Use when investigating non-conformances, performing root cause analysis, managing CAPAs, interpreting SPC data, or handling supplier quality issues.","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Feverything-claude-code\u002Fskills\u002Fquality-nonconformance\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":18},"01M7318DPHWK6CEVCVT7PHNKDZ","production-scheduling","Codified expertise for production scheduling, job sequencing, line balancing, changeover optimization, and bottleneck resolution in discrete and batch manufacturing. Informed by production schedulers with 15+ years experience. Includes TOC\u002Fdrum-buffer-rope, SMED, OEE analysis, disruption response frameworks, and ERP\u002FMES interaction patterns. Use when scheduling production, resolving bottlenecks, optimizing changeovers, responding to disruptions, or balancing manufacturing lines.","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Feverything-claude-code\u002Fskills\u002Fproduction-scheduling\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":18},"01M7315ZE0J0AB6KTQAFGCYF5V","logistics-exception-management","Codified expertise for handling freight exceptions, shipment delays, damages, losses, and carrier disputes. Informed by logistics professionals with 15+ years operational experience. Includes escalation protocols, carrier-specific behaviors, claims procedures, and judgment frameworks. Use when handling shipping exceptions, freight claims, delivery issues, or carrier disputes.","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Feverything-claude-code\u002Fskills\u002Flogistics-exception-management\u002FSKILL.md",[],[]]