[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71MB23MXAC92J9RFZ6P2GHC":3,"skill-same:01M71MB23MXAC92J9RFZ6P2GHC":76},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M71MB23MXAC92J9RFZ6P2GHC","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.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Farchitecture\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Farchitecture\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"knowledge","work","record","create","with","architecture decision","requirements","when","use","new","design","decision","system","trade-offs","kafka","proposal","adr","system design","decision record","2026-11-10 10:56:23",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.\"\ntags: []\ntools: []\nlicense: Apache-2.0\nsource: https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\nsource_path: \"engineering\u002Fskills\u002Farchitecture\"\nsource_commit: 8444efcd48f7012f09797778a36a33e73d0861f4\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,"tags":43,"tools":44,"source":45,"license":14,"description":7,"source_path":46,"source_commit":47},[],[],"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins","engineering\u002Fskills\u002Farchitecture","8444efcd48f7012f09797778a36a33e73d0861f4","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Farchitecture",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":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add monoes\u002Fmonomind --skill architecture",{"tool":63,"command":64},"bunx","bunx skills add monoes\u002Fmonomind --skill architecture",{"tool":66,"command":67},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Farchitecture\u002FSKILL.md",true,[71],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",11607,[77,103,139,164,188,215],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":102},"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.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[84,85,86,87,88,89,29,19,90,91,92,93,94,95,96,97,98,99,100,101],"zk","zk steward","steward","zero-knowledge","engineer","choice","impact","query","snark","review","monomind","security review","stark","zettelkasten","cryptography","security","org","blockchain","2026-11-10 13:02:02",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":107,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":121,"publishedAt":102},"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.","MIT","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",[111,116],{"categoryNo":112,"categoryName":113,"taxonomyType":114,"taxonomyTypeDesc":115},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":117,"categoryName":118,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[122,123,124,88,125,126,26,127,91,128,129,130,131,132,133,134,135,136,137,138],"writing","writing plans","plans","superpowers","implementation plan","you","code","tasks","plan","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":143,"sourceHtmlUrl":144,"categories":145,"keywords":149,"publishedAt":102},"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",[146],{"categoryNo":147,"categoryName":148,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000031","产品经理",[132,150,151,152,153,19,154,26,155,156,20,131,157,158,159,160,161,162,27,163],"write spec","spec","user request","problem","acceptance","ask","vague","request","scoping","idea","metrics","feature","problem statement","document",{"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":14,"licenseFileUrl":168,"sourceHtmlUrl":169,"categories":170,"keywords":174,"publishedAt":102},"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",[171],{"categoryNo":172,"categoryName":173,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000033","数据分析师",[91,132,175,176,177,178,19,27,26,179,180,23,181,20,182,183,184,185,186,187],"write query","postgres","for","snowflake","best practices","natural-language","multi","github","sql","https","syntax","plugins","data",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":200,"publishedAt":102},"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",[194,197],{"categoryNo":195,"categoryName":196,"taxonomyType":114,"taxonomyTypeDesc":115},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":198,"categoryName":199,"taxonomyType":114,"taxonomyTypeDesc":115},"01JBSEEDCAT000000000000023","Skill与智能体开发",[201,202,203,204,177,205,206,207,208,90,209,210,211,91,94,182,212,213,214,184],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"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":14,"licenseFileUrl":6,"sourceHtmlUrl":219,"categories":220,"keywords":222,"publishedAt":102},"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",[221],{"categoryNo":198,"categoryName":199,"taxonomyType":114,"taxonomyTypeDesc":115},[203,223,224,225,226,227,228,177,229,230,128,5,231,232,94,182,233,234,184,235],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","state","leadership","recovery","operations","systems"]