[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASF5TM4PNTA7B55384270G":3,"skill-same:01M7ASF5TM4PNTA7B55384270G":58},{"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":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7ASF5TM4PNTA7B55384270G","senior-system-design",null,"Use when designing or reviewing a system, service, migration or cross-component feature — anything where load, failure, data shape, security boundaries or rollout matter. Produces a design with explicit non-functional requirements, capacity assumptions, failure modes, security boundaries, observability and a rollout plan.","badrabbitt\u002Fleanrigor","badrabbitt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F91770919?v=4","01M7ASDXHKQ5D169TY5S4VJPTK","01M7ASDXJADMY7PNQC14E2NEH2",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fbadrabbitt\u002Fleanrigor\u002Fblob\u002Fmain\u002Fskills\u002Fsenior-system-design\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: senior-system-design\ndescription: Use when designing or reviewing a system, service, migration or cross-component feature — anything where load, failure, data shape, security boundaries or rollout matter. Produces a design with explicit non-functional requirements, capacity assumptions, failure modes, security boundaries, observability and a rollout plan.\nlicense: Apache-2.0\n---\n\n# Senior system design\n\nA design is a set of decisions with stated consequences. Prose that describes\ncomponents without deciding anything is not a design.\n\nWrite the design to `architecture.md`, one section per heading below. Each\nsection must end in a decision or an explicitly recorded unknown.\n`references\u002Fnfr-checklist.md` holds the detailed prompts; consult it when a\nsection feels thin.\n\n## 1. Functional requirements\nWhat the system must do, as capabilities a caller can invoke. Number them so the\nrest of the document can refer to them.\n\n## 2. Non-functional requirements\nState numbers, not adjectives. Required: request rate, data volume, latency\ntarget and the percentile it applies to, availability target, durability\nexpectation, consistency model, retention. \"Fast\" and \"reliable\" are not\nrequirements.\n\n## 3. Capacity assumptions\nShow the arithmetic: requests per second, bytes per record, records per day,\nstorage at one year, peak-to-average ratio. Label every input as measured,\nestimated or assumed. A capacity section with no arithmetic is a guess wearing\na suit.\n\n## 4. Data\nEntities, ownership, access patterns, indexes implied by those patterns, and the\nmigration path from what exists today. Say which component owns each write.\n\n## 5. Failure modes\nFor each dependency: what happens when it is slow, when it is down, and when it\nreturns wrong data. Then decide, per call: timeout, retry policy with backoff and\njitter, retry budget, idempotency, and what the caller sees when you give up.\nRetries without a budget turn one failure into an outage.\n\n## 6. Security boundaries\nWhere trust changes hands. For each boundary: what authenticates the caller,\nwhat authorizes the action, what is validated, what is logged, and what must\nnever be logged. Name where secrets live and how they rotate.\n\n## 7. Observability\nThe signals that would let someone diagnose this at 3am: the SLI and its target,\nthe alert that fires when users are affected — not when a machine is busy — the\ndashboard, and the trace or log field that ties a user report to a request.\n\n## 8. Cost\nThe dominant cost driver and roughly what it scales with. A design that is right\nand unaffordable is not right.\n\n## 9. Rollout and rollback\nOrder of deployment, compatibility during the window when both versions run,\nthe flag or toggle, what is migrated and when, and the exact rollback step. If\nrollback is impossible after a point, say where that point is.\n\n## Choosing between options\n\nWhere a real choice exists, state at least two options and pick one on a named\ncriterion. Record what would change the decision. A design that presents one\noption has hidden its reasoning rather than shown it.\n\n## Anti-patterns\n\n- Adjectives instead of numbers in the NFR section.\n- A component diagram with no decisions attached.\n- Failure handling reduced to \"retry\".\n- Alerts on CPU rather than on user-visible symptoms.\n- No rollback step, or a rollback step that has never been thought through.\n","# Senior system design\n\nA design is a set of decisions with stated consequences. Prose that describes\ncomponents without deciding anything is not a design.\n\nWrite the design to `architecture.md`, one section per heading below. Each\nsection must end in a decision or an explicitly recorded unknown.\n`references\u002Fnfr-checklist.md` holds the detailed prompts; consult it when a\nsection feels thin.\n\n## 1. Functional requirements\nWhat the system must do, as capabilities a caller can invoke. Number them so the\nrest of the document can refer to them.\n\n## 2. Non-functional requirements\nState numbers, not adjectives. Required: request rate, data volume, latency\ntarget and the percentile it applies to, availability target, durability\nexpectation, consistency model, retention. \"Fast\" and \"reliable\" are not\nrequirements.\n\n## 3. Capacity assumptions\nShow the arithmetic: requests per second, bytes per record, records per day,\nstorage at one year, peak-to-average ratio. Label every input as measured,\nestimated or assumed. A capacity section with no arithmetic is a guess wearing\na suit.\n\n## 4. Data\nEntities, ownership, access patterns, indexes implied by those patterns, and the\nmigration path from what exists today. Say which component owns each write.\n\n## 5. Failure modes\nFor each dependency: what happens when it is slow, when it is down, and when it\nreturns wrong data. Then decide, per call: timeout, retry policy with backoff and\njitter, retry budget, idempotency, and what the caller sees when you give up.\nRetries without a budget turn one failure into an outage.\n\n## 6. Security boundaries\nWhere trust changes hands. For each boundary: what authenticates the caller,\nwhat authorizes the action, what is validated, what is logged, and what must\nnever be logged. Name where secrets live and how they rotate.\n\n## 7. Observability\nThe signals that would let someone diagnose this at 3am: the SLI and its target,\nthe alert that fires when users are affected — not when a machine is busy — the\ndashboard, and the trace or log field that ties a user report to a request.\n\n## 8. Cost\nThe dominant cost driver and roughly what it scales with. A design that is right\nand unaffordable is not right.\n\n## 9. Rollout and rollback\nOrder of deployment, compatibility during the window when both versions run,\nthe flag or toggle, what is migrated and when, and the exact rollback step. If\nrollback is impossible after a point, say where that point is.\n\n## Choosing between options\n\nWhere a real choice exists, state at least two options and pick one on a named\ncriterion. Record what would change the decision. A design that presents one\noption has hidden its reasoning rather than shown it.\n\n## Anti-patterns\n\n- Adjectives instead of numbers in the NFR section.\n- A component diagram with no decisions attached.\n- Failure handling reduced to \"retry\".\n- Alerts on CPU rather than on user-visible symptoms.\n- No rollback step, or a rollback step that has never been thought through.\n",{"name":5,"license":14,"description":7},"main","0b45d399b5a5d7a6666c1df2b2218e4a0cddb8cc","skills\u002Fsenior-system-design",1,"https:\u002F\u002Fgithub.com\u002Fbadrabbitt\u002Fleanrigor","https:\u002F\u002Fgithub.com\u002Fbadrabbitt","2026-10-13 17:15:33",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add badrabbitt\u002Fleanrigor --skill senior-system-design",{"tool":36,"command":37},"bunx","bunx skills add badrabbitt\u002Fleanrigor --skill senior-system-design",{"tool":39,"command":40},"pnpm","pnpm dlx skills add badrabbitt\u002Fleanrigor --skill senior-system-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbadrabbitt\u002Fleanrigor\u002Fblob\u002Fmain\u002Fskills\u002Fsenior-system-design\u002FSKILL.md",true,[44,50,54],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"leanrigor.yaml","REFERENCE","参考文档",313,"https:\u002F\u002Fgithub.com\u002Fbadrabbitt\u002Fleanrigor\u002Fblob\u002Fmain\u002Fskills\u002Fsenior-system-design\u002Fleanrigor.yaml",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"provenance.yaml",605,"https:\u002F\u002Fgithub.com\u002Fbadrabbitt\u002Fleanrigor\u002Fblob\u002Fmain\u002Fskills\u002Fsenior-system-design\u002Fprovenance.yaml",{"path":55,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fnfr-checklist.md",2643,"https:\u002F\u002Fgithub.com\u002Fbadrabbitt\u002Fleanrigor\u002Fblob\u002Fmain\u002Fskills\u002Fsenior-system-design\u002Freferences\u002Fnfr-checklist.md",[59,66,73,79,87,93],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M7ASF9ZY5ZT88M951GTRP6S9","verification","Use before claiming that work is complete, fixed, passing or done — including before committing, opening a pull request or reporting a result. Requires running the checks and quoting their real output instead of asserting success.","https:\u002F\u002Fgithub.com\u002Fbadrabbitt\u002Fleanrigor\u002Fblob\u002Fmain\u002Fskills\u002Fverification\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M7ASF0NVC5XB3ZR2RM3Y2289","product-brainstorming","Use before building a feature, product or component when the problem, users or scope are not yet settled — including requests phrased as \"build X\", \"add X\" or \"we need X\" that have not stated who it is for or what breaks without it. Produces a scoped brief, not an implementation.","https:\u002F\u002Fgithub.com\u002Fbadrabbitt\u002Fleanrigor\u002Fblob\u002Fmain\u002Fskills\u002Fproduct-brainstorming\u002FSKILL.md",[],[],{"skillNo":74,"name":61,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M7ASEYCAQ7RRY7215KWQF2VB","Collect evidence before claiming that work is complete. Use when a task is about to be reported as done, fixed or passing.","https:\u002F\u002Fgithub.com\u002Fbadrabbitt\u002Fleanrigor\u002Fblob\u002Fmain\u002Fpackages\u002Fskill-router\u002Ftest\u002Ffixtures\u002Fskills\u002Fverification\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M7ASEV2E8BHTP0Q0TA7AP2PQ","undeclared-network","A skill shipping a script that reaches the network without declaring the capability.","MIT","https:\u002F\u002Fgithub.com\u002Fbadrabbitt\u002Fleanrigor\u002Fblob\u002Fmain\u002Fpackages\u002Fskill-router\u002Ftest\u002Ffixtures\u002Fskills\u002Fundeclared-network\u002FSKILL.md",[],[],{"skillNo":88,"name":5,"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":92,"publishedAt":18},"01M7ASERMH0E0Q44E280RWDEGS","Produce a system design with explicit non-functional requirements, capacity assumptions, failure modes, security boundaries, observability and rollout.","https:\u002F\u002Fgithub.com\u002Fbadrabbitt\u002Fleanrigor\u002Fblob\u002Fmain\u002Fpackages\u002Fskill-router\u002Ftest\u002Ffixtures\u002Fskills\u002Fsenior-system-design\u002FSKILL.md",[],[],{"skillNo":94,"name":68,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":18},"01M7ASEN6GGQ3NGWBKWDH805RR","Explore the problem, users, alternatives, scope and validation before any implementation work begins.","https:\u002F\u002Fgithub.com\u002Fbadrabbitt\u002Fleanrigor\u002Fblob\u002Fmain\u002Fpackages\u002Fskill-router\u002Ftest\u002Ffixtures\u002Fskills\u002Fproduct-brainstorming\u002FSKILL.md",[],[]]