[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79V6WDR2CDT94CMC7AC4VNV":3,"skill-same:01M79V6WDR2CDT94CMC7AC4VNV":79},{"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":38,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M79V6WDR2CDT94CMC7AC4VNV","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.","Vishwajeetsrk\u002FJARVIS-AI-OS","Vishwajeetsrk","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F83073825?v=4","01M79V4YAYQ35CPZPBS1RQ6VEX","VishwaJeet","01M79V4YBP8A6PPPZ91229KVHN",11,"MIT","https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS\u002Fblob\u002Fmain\u002F.agents\u002Fskills\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","87476a719bbe41680362bb9bfacf884c53784783",".agents\u002Fskills\u002Farchitecture-designer",3,"https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS","https:\u002F\u002Fjarvisaios.vercel.app","https:\u002F\u002Fgithub.com\u002FVishwajeetsrk","https:\u002F\u002Flearnifyaitool.vercel.app\u002F","🎉 Welcome to my profile! I'm a BCA student with a passion for technology and innovation. As a frontend developer.","2026-09-01 14:20:58",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add Vishwajeetsrk\u002FJARVIS-AI-OS --skill architecture-designer",{"tool":49,"command":50},"bunx","bunx skills add Vishwajeetsrk\u002FJARVIS-AI-OS --skill architecture-designer",{"tool":52,"command":53},"pnpm","pnpm dlx skills add Vishwajeetsrk\u002FJARVIS-AI-OS --skill architecture-designer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Farchitecture-designer\u002FSKILL.md",true,[57,63,67,71,75],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fadr-template.md","REFERENCE","参考文档",2752,"https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Farchitecture-designer\u002Freferences\u002Fadr-template.md",{"path":64,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Farchitecture-patterns.md",4605,"https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Farchitecture-designer\u002Freferences\u002Farchitecture-patterns.md",{"path":68,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fdatabase-selection.md",2569,"https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Farchitecture-designer\u002Freferences\u002Fdatabase-selection.md",{"path":72,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fnfr-checklist.md",3046,"https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Farchitecture-designer\u002Freferences\u002Fnfr-checklist.md",{"path":76,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fsystem-design.md",3009,"https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Farchitecture-designer\u002Freferences\u002Fsystem-design.md",[80,86,95,103,109,117],{"skillNo":81,"name":82,"nameZh":6,"description":6,"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},"01M79VY332PY7B4KCWMN3FM430","workspace-agent","https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS\u002Fblob\u002Fmain\u002Fskills\u002Fworkspace-agent\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":90,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M79VXZK9MKMYDV57N8VJDPYW","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M79VXR975D5MQTW5VMFTKWGG","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M79VXMF2JMWE9GETMJFRM4B9","ui-ux-expert","https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS\u002Fblob\u002Fmain\u002Fskills\u002Fui-ux-expert\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"01M79VXGG2RRFF3EH79CDYVE0K","theme-factory","Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors\u002Ffonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.","https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS\u002Fblob\u002Fmain\u002Fskills\u002Ftheme-factory\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS\u002Fblob\u002Fmain\u002Fskills\u002Ftheme-factory\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":19},"01M79VXCR3A6QMYT131RFKNTWT","test-agent","https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS\u002Fblob\u002Fmain\u002Fskills\u002Ftest-agent\u002FSKILL.md",[],[]]