[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71K5CGEEBE595F4W5FZK720":3,"skill-same:01M71K5CGEEBE595F4W5FZK720":73},{"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":27,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":13,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":58,"install":59,"resources":72},"01M71K5CGEEBE595F4W5FZK720","architecture",null,"Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.","mryfmo\u002Fdotfiles","mryfmo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F11512262?v=4","01M71K2RDZFFQKYGMHMS5Y9PW1","01M71K2REKJ0WS61PNFQPTYP5T",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fkwp-upstream\u002Fengineering\u002Fskills\u002Farchitecture\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[5,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"record","new","when","decision record","trade-offs","architecture decision","with","proposal","requirements","trade","design","system design","use","decision","adr","system","kafka","create","component","2026-11-10 10:12:30",false,"---\nname: architecture\ndescription: Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.\nargument-hint: \"\u003Cdecision or system to design>\"\n---\n\n# \u002Farchitecture\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nCreate an Architecture Decision Record (ADR) or evaluate a system design.\n\n## Usage\n\n```\n\u002Farchitecture $ARGUMENTS\n```\n\n## Modes\n\n**Create an ADR**: \"Should we use Kafka or SQS for our event bus?\"\n**Evaluate a design**: \"Review this microservices proposal\"\n**System design**: \"Design the notification system for our app\"\n\nSee the **system-design** skill for detailed frameworks on requirements gathering, scalability analysis, and trade-off evaluation.\n\n## Output — ADR Format\n\n```markdown\n# ADR-[number]: [Title]\n\n**Status:** Proposed | Accepted | Deprecated | Superseded\n**Date:** [Date]\n**Deciders:** [Who needs to sign off]\n\n## Context\n[What is the situation? What forces are at play?]\n\n## Decision\n[What is the change we're proposing?]\n\n## Options Considered\n\n### Option A: [Name]\n| Dimension | Assessment |\n|-----------|------------|\n| Complexity | [Low\u002FMed\u002FHigh] |\n| Cost | [Assessment] |\n| Scalability | [Assessment] |\n| Team familiarity | [Assessment] |\n\n**Pros:** [List]\n**Cons:** [List]\n\n### Option B: [Name]\n[Same format]\n\n## Trade-off Analysis\n[Key trade-offs between options with clear reasoning]\n\n## Consequences\n- [What becomes easier]\n- [What becomes harder]\n- [What we'll need to revisit]\n\n## Action Items\n1. [ ] [Implementation step]\n2. [ ] [Follow-up]\n```\n\n## If Connectors Available\n\nIf **~~knowledge base** is connected:\n- Search for prior ADRs and design docs\n- Find relevant technical context\n\nIf **~~project tracker** is connected:\n- Link to related epics and tickets\n- Create implementation tasks\n\n## Tips\n\n1. **State constraints upfront** — \"We need to ship in 2 weeks\" or \"Must handle 10K rps\" shapes the answer.\n2. **Name your options** — Even if you're leaning one way, I'll give a more balanced analysis with explicit alternatives.\n3. **Include non-functional requirements** — Latency, cost, team expertise, and maintenance burden matter as much as features.\n","# \u002Farchitecture\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nCreate an Architecture Decision Record (ADR) or evaluate a system design.\n\n## Usage\n\n```\n\u002Farchitecture $ARGUMENTS\n```\n\n## Modes\n\n**Create an ADR**: \"Should we use Kafka or SQS for our event bus?\"\n**Evaluate a design**: \"Review this microservices proposal\"\n**System design**: \"Design the notification system for our app\"\n\nSee the **system-design** skill for detailed frameworks on requirements gathering, scalability analysis, and trade-off evaluation.\n\n## Output — ADR Format\n\n```markdown\n# ADR-[number]: [Title]\n\n**Status:** Proposed | Accepted | Deprecated | Superseded\n**Date:** [Date]\n**Deciders:** [Who needs to sign off]\n\n## Context\n[What is the situation? What forces are at play?]\n\n## Decision\n[What is the change we're proposing?]\n\n## Options Considered\n\n### Option A: [Name]\n| Dimension | Assessment |\n|-----------|------------|\n| Complexity | [Low\u002FMed\u002FHigh] |\n| Cost | [Assessment] |\n| Scalability | [Assessment] |\n| Team familiarity | [Assessment] |\n\n**Pros:** [List]\n**Cons:** [List]\n\n### Option B: [Name]\n[Same format]\n\n## Trade-off Analysis\n[Key trade-offs between options with clear reasoning]\n\n## Consequences\n- [What becomes easier]\n- [What becomes harder]\n- [What we'll need to revisit]\n\n## Action Items\n1. [ ] [Implementation step]\n2. [ ] [Follow-up]\n```\n\n## If Connectors Available\n\nIf **~~knowledge base** is connected:\n- Search for prior ADRs and design docs\n- Find relevant technical context\n\nIf **~~project tracker** is connected:\n- Link to related epics and tickets\n- Create implementation tasks\n\n## Tips\n\n1. **State constraints upfront** — \"We need to ship in 2 weeks\" or \"Must handle 10K rps\" shapes the answer.\n2. **Name your options** — Even if you're leaning one way, I'll give a more balanced analysis with explicit alternatives.\n3. **Include non-functional requirements** — Latency, cost, team expertise, and maintenance burden matter as much as features.\n",{"name":5,"description":7,"argument-hint":52},"\u003Cdecision or system to design>","main","af601a97567f1f07e9337cad899506f601f419f1","tests\u002Ffixtures\u002Fkwp-upstream\u002Fengineering\u002Fskills\u002Farchitecture","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles","https:\u002F\u002Fgithub.com\u002Fmryfmo","2026-11-13 12:53:52",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add mryfmo\u002Fdotfiles --skill architecture",{"tool":65,"command":66},"bunx","bunx skills add mryfmo\u002Fdotfiles --skill architecture",{"tool":68,"command":69},"pnpm","pnpm dlx skills add mryfmo\u002Fdotfiles --skill architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fkwp-upstream\u002Fengineering\u002Fskills\u002Farchitecture\u002FSKILL.md",true,[],[74,80,86,113,134,152],{"skillNo":75,"name":76,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":47},"01M71K61D634ATEV8NWTGGWNGS","x","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fponytail\u002Fskills\u002Fx\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":47},"01M71K605VRE3ABPN1MZHJNZ29","y","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fponytail\u002Fdocs\u002Fskills\u002Fy\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":95,"publishedAt":47},"01M71K5Y3XX1PYZAWA7M5RG9VD","status-report","Generate a status report with KPIs, risks, and action items. Use when writing a weekly or monthly update for leadership, summarizing project health with green\u002Fyellow\u002Fred status, surfacing risks and decisions that need stakeholder attention, or turning a pile of project tracker activity into a readable narrative.","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fkwp-upstream\u002Foperations\u002Fskills\u002Fstatus-report\u002FSKILL.md",[92],{"categoryNo":93,"categoryName":94,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000034","行政与办公人员",[96,97,98,99,100,101,102,103,34,104,105,106,107,108,109,40,30,110,111,112],"status report","report","status","tracker","health","generate","leadership","narrative","weekly","attention","green","for","project","writing","decisions","team","project health",{"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":14,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":47},"01M71K5VJAHGE1NH22BGBXP693","runbook","Create or update an operational runbook for a recurring task or procedure. Use when documenting a task that on-call or ops needs to run repeatably, turning tribal knowledge into exact step-by-step commands, adding troubleshooting and rollback steps to an existing procedure, or writing escalation paths for when things go wrong.","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fkwp-upstream\u002Foperations\u002Fskills\u002Frunbook\u002FSKILL.md",[],[115,120,121,122,123,124,125,45,126,30,127,128,40,109,129,130,107,131,132,133],"task","update","name","run","process","operational","call","ops","Existing","knowledge","rollback","escalation","recurring","things",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":47},"01M71K5SJ0FT7KD82E7PJCGATX","risk-assessment","Identify, assess, and mitigate operational risks. Trigger with \"what are the risks\", \"risk assessment\", \"risk register\", \"what could go wrong\", or when the user is evaluating risks associated with a project, vendor, process, or decision.","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fkwp-upstream\u002Foperations\u002Fskills\u002Frisk-assessment\u002FSKILL.md",[],[141,142,143,34,41,144,145,30,146,147,148,149,150,124,108,125,151],"risk assessment","assessment","risk","user","Wrong","go","assess","trigger","risk register","vendor","register",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":158,"publishedAt":47},"01M71K5PYD2A2BDM6KMZ8F01SV","change-request","Create a change management request with impact analysis and rollback plan. Use when proposing a system or process change that needs approval, preparing a change record for CAB review, documenting risk and rollback steps before a deployment, or planning stakeholder communications for a rollout.","https:\u002F\u002Fgithub.com\u002Fmryfmo\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fkwp-upstream\u002Foperations\u002Fskills\u002Fchange-request\u002FSKILL.md",[],[159,160,161,40,34,162,163,164,165,166,167,30,168,169,170,43,171,107,172,143],"request","change request","change","communications","stakeholder communications","review","rollback plan","analysis","rollout","impact","change management","impact analysis","deployment","planning"]