[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6P7HBX8G8W37RMASDN48XA7":3,"skill-same:01M6P7HBX8G8W37RMASDN48XA7":84},{"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":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":14,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":46,"updatedAt":47,"install":48,"resources":60},"01M6P7HBX8G8W37RMASDN48XA7","architect",null,"Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for \u002Farchitect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.","sarthchawla\u002FSetupMyAI","sarthchawla","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F41484686?v=4","01M6P7D22NFMY9MA11Q2YGPKV2","Sarthak Chawla","01M6P7D26JJ9KW98SD1G8BB83R",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsarthchawla\u002FSetupMyAI\u002Fblob\u002Fmain\u002Fpackages\u002Fpstack\u002Fskills\u002Farchitect\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"implementation","Wrong","for","lock","true","types","module","structure","signatures","design","shape","sketch","use","work","loop","code","2026-11-10 10:12:30",false,"---\nname: architect\ndescription: \"Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for \u002Farchitect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.\"\ndisable-model-invocation: true\n---\n\n# Architect\n\nSketch types, function signatures, class shapes, and module boundaries with `not implemented` bodies and pseudocode. Synthesize across multiple model perspectives, then fill in code against the chosen sketch.\n\n## Start\n\nOpen a todolist with one entry per phase before starting.\n\n1. Ground\n2. Sketch\n3. Agree\n4. Implement\n5. Scrap\n\n## Phase A: Ground the problem\n\nBuild a real mental model of every system the new code touches. Run the **how** skill over the relevant subsystems. Naming a file isn't grounding. Produce the architectural explanation `how` prescribes. If the design redefines ownership or layering, also run the **why** skill on the existing shape so the rationale becomes a constraint, not a guess.\n\nSkip Phase A only when the work is genuinely greenfield with no surrounding system to integrate.\n\n## Phase B: Sketch\n\nRun the **arena** skill with the design-sketch task and the Phase A grounding artifacts. Pass `references\u002Frunner-prompt.md` as each runner's prompt.\n\nTake the runners from the `architect runners` line in the pstack settings file (`~\u002F.cursor\u002Frules\u002Fpstack-models.mdc` in Cursor, `~\u002F.claude\u002Frules\u002Fpstack-models.md` in Claude Code, `~\u002F.agents\u002Fpstack-models.md` in other harnesses), in place of the `arena runners` line. If the file or that line is missing, use `claude-opus-5-5-xhigh` and `grok-4.7-xhigh-fast`. Alias and rejected entries follow the runner rules in the **arena** skill's Phase A.\n\nDesign it twice. Require at least two structurally distinct candidates before synthesis, even when the first looks sufficient. This is the **exhaust-the-design-space** principle skill made concrete. Whole-shape alternatives, not point fixes inside one shape.\n\nScreen every candidate against [`references\u002Fdesign-red-flags.md`](references\u002Fdesign-red-flags.md) before synthesis. Assume the next contributor is an agent that sees only the files it opened, copies the nearest example, and takes the shortest path that compiles. Prefer the design where a change that looks right from one file is right for the whole repo.\n\nCompare viable candidates on interface depth. Prefer the design that hides more complexity behind a smaller, simpler public surface. A rich interface can keep call chains short by concentrating capability instead of scattering it across layers.\n\nArena returns one synthesized design package. Its synthesis decision fills the rationale's \"Synthesis decision\" section.\n\n## Phase C: Agree (opt-in)\n\nDefault: proceed directly to implementation with the synthesized design. No human checkpoint.\n\nOpt in to a checkpoint when the invoker explicitly asks: \"\u002Farchitect with checkpoint,\" \"stop and show me before implementing,\" or similar. Then surface the synthesized design and pause for sign-off.\n\nThe synthesis can ship as its own commit either way, as the \"scaffold first\" mode of the **foundational-thinking** principle skill. Planned and scoped breakage during fill-in is fine, per the **outcome-oriented-execution** principle skill. For adversarial pressure on the design before implementing, run the **interrogate** skill on the synthesized sketch.\n\nIf the human pushes back on the shape (in a checkpoint or after the fact), treat that as Phase A evidence. Re-ground and re-run Phase B before writing more code.\n\n## Phase D: Implement against the sketch\n\nReplace `not implemented` bodies with code, pseudocode with logic. The synthesized sketch is the contract. Deviations from it are signal to surface, not friction to absorb silently. If a function needs a parameter the sketch didn't anticipate, ask whether the sketch was wrong, the requirement was missed, or the implementation is overreaching.\n\n## Phase E: Scrap when the architecture is wrong\n\nIf implementation keeps producing friction the sketch can't absorb, throw the sketch out. Don't bolt fixes onto a wrong design, per the **redesign-from-first-principles** and **fix-root-causes** principle skills.\n\nThe signal is a *pattern*, not single instances. Tells:\n\n- The same shape of workaround appearing repeatedly across unrelated code.\n- Multiple unrelated edge cases that all need special-case branches.\n- Types that need escape hatches (`any`, casts, optional fields always set in practice) to compile.\n- The \"we need a lock\" reflex when the sketch said the state wasn't shared.\n- Callers having to know the abstraction's internal rules to use it.\n- Two or more independent Phase D deviations of the same shape across the implementation.\n\nUse judgment. A few edge cases don't condemn an architecture. Some problems are legitimately complex. Complexity in the data is not complexity in the design.\n\nWhen you scrap:\n\n1. Re-run the **how** skill over what's been built.\n2. Redesign as if the new constraints had been day-one assumptions, per redesign-from-first-principles.\n3. Subtract before adding, per the **subtract-before-you-add** principle skill. The new sketch should be smaller than the old one before it grows.\n4. Return to Phase B and re-run arena.\n\n## Outputs\n\nThe caller's usage is written first and the type sketch derived from it. One file with new types and signatures for small changes. Module map plus type definitions for larger work. The rationale ships alongside, shaped per `references\u002Frationale-template.md`, including the usage sketch and the synthesis decision.\n","# Architect\n\nSketch types, function signatures, class shapes, and module boundaries with `not implemented` bodies and pseudocode. Synthesize across multiple model perspectives, then fill in code against the chosen sketch.\n\n## Start\n\nOpen a todolist with one entry per phase before starting.\n\n1. Ground\n2. Sketch\n3. Agree\n4. Implement\n5. Scrap\n\n## Phase A: Ground the problem\n\nBuild a real mental model of every system the new code touches. Run the **how** skill over the relevant subsystems. Naming a file isn't grounding. Produce the architectural explanation `how` prescribes. If the design redefines ownership or layering, also run the **why** skill on the existing shape so the rationale becomes a constraint, not a guess.\n\nSkip Phase A only when the work is genuinely greenfield with no surrounding system to integrate.\n\n## Phase B: Sketch\n\nRun the **arena** skill with the design-sketch task and the Phase A grounding artifacts. Pass `references\u002Frunner-prompt.md` as each runner's prompt.\n\nTake the runners from the `architect runners` line in the pstack settings file (`~\u002F.cursor\u002Frules\u002Fpstack-models.mdc` in Cursor, `~\u002F.claude\u002Frules\u002Fpstack-models.md` in Claude Code, `~\u002F.agents\u002Fpstack-models.md` in other harnesses), in place of the `arena runners` line. If the file or that line is missing, use `claude-opus-5-5-xhigh` and `grok-4.7-xhigh-fast`. Alias and rejected entries follow the runner rules in the **arena** skill's Phase A.\n\nDesign it twice. Require at least two structurally distinct candidates before synthesis, even when the first looks sufficient. This is the **exhaust-the-design-space** principle skill made concrete. Whole-shape alternatives, not point fixes inside one shape.\n\nScreen every candidate against [`references\u002Fdesign-red-flags.md`](references\u002Fdesign-red-flags.md) before synthesis. Assume the next contributor is an agent that sees only the files it opened, copies the nearest example, and takes the shortest path that compiles. Prefer the design where a change that looks right from one file is right for the whole repo.\n\nCompare viable candidates on interface depth. Prefer the design that hides more complexity behind a smaller, simpler public surface. A rich interface can keep call chains short by concentrating capability instead of scattering it across layers.\n\nArena returns one synthesized design package. Its synthesis decision fills the rationale's \"Synthesis decision\" section.\n\n## Phase C: Agree (opt-in)\n\nDefault: proceed directly to implementation with the synthesized design. No human checkpoint.\n\nOpt in to a checkpoint when the invoker explicitly asks: \"\u002Farchitect with checkpoint,\" \"stop and show me before implementing,\" or similar. Then surface the synthesized design and pause for sign-off.\n\nThe synthesis can ship as its own commit either way, as the \"scaffold first\" mode of the **foundational-thinking** principle skill. Planned and scoped breakage during fill-in is fine, per the **outcome-oriented-execution** principle skill. For adversarial pressure on the design before implementing, run the **interrogate** skill on the synthesized sketch.\n\nIf the human pushes back on the shape (in a checkpoint or after the fact), treat that as Phase A evidence. Re-ground and re-run Phase B before writing more code.\n\n## Phase D: Implement against the sketch\n\nReplace `not implemented` bodies with code, pseudocode with logic. The synthesized sketch is the contract. Deviations from it are signal to surface, not friction to absorb silently. If a function needs a parameter the sketch didn't anticipate, ask whether the sketch was wrong, the requirement was missed, or the implementation is overreaching.\n\n## Phase E: Scrap when the architecture is wrong\n\nIf implementation keeps producing friction the sketch can't absorb, throw the sketch out. Don't bolt fixes onto a wrong design, per the **redesign-from-first-principles** and **fix-root-causes** principle skills.\n\nThe signal is a *pattern*, not single instances. Tells:\n\n- The same shape of workaround appearing repeatedly across unrelated code.\n- Multiple unrelated edge cases that all need special-case branches.\n- Types that need escape hatches (`any`, casts, optional fields always set in practice) to compile.\n- The \"we need a lock\" reflex when the sketch said the state wasn't shared.\n- Callers having to know the abstraction's internal rules to use it.\n- Two or more independent Phase D deviations of the same shape across the implementation.\n\nUse judgment. A few edge cases don't condemn an architecture. Some problems are legitimately complex. Complexity in the data is not complexity in the design.\n\nWhen you scrap:\n\n1. Re-run the **how** skill over what's been built.\n2. Redesign as if the new constraints had been day-one assumptions, per redesign-from-first-principles.\n3. Subtract before adding, per the **subtract-before-you-add** principle skill. The new sketch should be smaller than the old one before it grows.\n4. Return to Phase B and re-run arena.\n\n## Outputs\n\nThe caller's usage is written first and the type sketch derived from it. One file with new types and signatures for small changes. Module map plus type definitions for larger work. The rationale ships alongside, shaped per `references\u002Frationale-template.md`, including the usage sketch and the synthesis decision.\n",{"name":5,"description":7,"disable-model-invocation":40},true,"main","3934845b800ff514cb89eb81d43f3dc4cbf51ff2","packages\u002Fpstack\u002Fskills\u002Farchitect","https:\u002F\u002Fgithub.com\u002Fsarthchawla\u002FSetupMyAI","https:\u002F\u002Fgithub.com\u002Fsarthchawla","there ain't no problem i can't solve","2026-10-23 01:26:57",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":40},[50,53,56],{"tool":51,"command":52},"npx","npx skills add sarthchawla\u002FSetupMyAI --skill architect",{"tool":54,"command":55},"bunx","bunx skills add sarthchawla\u002FSetupMyAI --skill architect",{"tool":57,"command":58},"pnpm","pnpm dlx skills add sarthchawla\u002FSetupMyAI --skill architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsarthchawla\u002FSetupMyAI\u002Fblob\u002Fmain\u002Fpackages\u002Fpstack\u002Fskills\u002Farchitect\u002FSKILL.md",[61,67,72,76,80],{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"agents\u002Fopenai.yaml","REFERENCE","参考文档",43,"https:\u002F\u002Fgithub.com\u002Fsarthchawla\u002FSetupMyAI\u002Fblob\u002Fmain\u002Fpackages\u002Fpstack\u002Fskills\u002Farchitect\u002Fagents\u002Fopenai.yaml",{"path":68,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"LICENSE","许可证",1067,"https:\u002F\u002Fgithub.com\u002Fsarthchawla\u002FSetupMyAI\u002Fblob\u002Fmain\u002Fpackages\u002Fpstack\u002Fskills\u002Farchitect\u002FLICENSE",{"path":73,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fdesign-red-flags.md",3009,"https:\u002F\u002Fgithub.com\u002Fsarthchawla\u002FSetupMyAI\u002Fblob\u002Fmain\u002Fpackages\u002Fpstack\u002Fskills\u002Farchitect\u002Freferences\u002Fdesign-red-flags.md",{"path":77,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Frationale-template.md",3050,"https:\u002F\u002Fgithub.com\u002Fsarthchawla\u002FSetupMyAI\u002Fblob\u002Fmain\u002Fpackages\u002Fpstack\u002Fskills\u002Farchitect\u002Freferences\u002Frationale-template.md",{"path":81,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Frunner-prompt.md",3092,"https:\u002F\u002Fgithub.com\u002Fsarthchawla\u002FSetupMyAI\u002Fblob\u002Fmain\u002Fpackages\u002Fpstack\u002Fskills\u002Farchitect\u002Freferences\u002Frunner-prompt.md",[85,98,114,123,133,153],{"skillNo":86,"name":87,"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":88,"categories":89,"keywords":95,"publishedAt":35},"01M6P8953HNC422WFQSPP2FMQE","sample-skill","https:\u002F\u002Fgithub.com\u002Fsarthchawla\u002FSetupMyAI\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fmock-repo\u002F.claude\u002Fskills\u002Fsample-skill\u002FSKILL.md",[90],{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[96,97],"sample","sample skill",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":35},"01M6P8924ZSDAZ88Y5Q9P3KAQV","synthetic-review-candidate","Candidate for smoke testing an evaluation runner only.","https:\u002F\u002Fgithub.com\u002Fsarthchawla\u002FSetupMyAI\u002Fblob\u002Fmain\u002Fscripts\u002Fskill-eval\u002Ffixtures\u002Fcandidate\u002FSKILL.md",[],[105,106,107,108,109,110,111,112,113,21],"synthetic review candidate","candidate","synthetic","review","only","testing","Evaluation","smoke","runner",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":35},"01M6P88FEGGNH8EZY0PDHD9KQA","synthetic-review-baseline","Baseline for smoke testing an evaluation runner only.","https:\u002F\u002Fgithub.com\u002Fsarthchawla\u002FSetupMyAI\u002Fblob\u002Fmain\u002Fscripts\u002Fskill-eval\u002Ffixtures\u002Fbaseline\u002FSKILL.md",[],[121,107,122,108,112,113,21,109,110,111],"synthetic review baseline","baseline",{"skillNo":124,"name":108,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":35},"01M6P87ZXVEHRM860960DB5FEQ","Run the existing user-invoked review bundle and independently adjudicate its findings.","https:\u002F\u002Fgithub.com\u002Fsarthchawla\u002FSetupMyAI\u002Fblob\u002Fmain\u002Fpackages\u002Funiversal\u002Fskills\u002Freview\u002FSKILL.md",[],[108,129,130,131,132],"run","user","bundle","Existing",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":35},"01M6P87FC73MZTRB6ZBP4GR1VQ","review-adjudication","Verify generated or human review findings before fixing, defending, replying, resolving, or reusing them as learned guidance. Use within a review, review-comment fix, monitor, or readiness workflow.","https:\u002F\u002Fgithub.com\u002Fsarthchawla\u002FSetupMyAI\u002Fblob\u002Fmain\u002Fpackages\u002Funiversal\u002Fskills\u002Freview-adjudication\u002FSKILL.md",[],[140,108,141,142,143,144,145,146,147,148,149,150,31,151,152],"review adjudication","workflow","generated","human review","guidance","human","as","readiness","learned","review findings","fix","verify","monitor",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":35},"01M6P871Q44KQES293T60JQETA","monitor-mr","Monitor review findings and CI using the shared adjudication procedure.","https:\u002F\u002Fgithub.com\u002Fsarthchawla\u002FSetupMyAI\u002Fblob\u002Fmain\u002Fpackages\u002Funiversal\u002Fskills\u002Fmonitor-mr\u002FSKILL.md",[],[152,160,161,149,162,163,108],"mr","monitor mr","shared","ci"]