[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A7TM405F6F3GYVV15GR215":3,"skill-same:01M7A7TM405F6F3GYVV15GR215":60},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":45},"01M7A7TM405F6F3GYVV15GR215","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.","am-will\u002Fgooey-pi","am-will","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42459108?v=4","01M6DGTYZDSE8HR73NQBJ31689","am.will","01M7A7TJ263XAJ06M4HD6MTTJD",974,"MIT","https:\u002F\u002Fgithub.com\u002Fam-will\u002Fgooey-pi\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpstack\u002Farchitect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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\nDesign before implementing. Sketch types, function signatures, class shapes, and module boundaries with `not implemented` bodies and pseudocode. Synthesize across independent design perspectives, then fill in code against the chosen sketch. If implementation proves the sketch wrong, throw it out and redesign.\n\n## Start\n\nOpen a todolist with one entry per phase before starting. Autonomous mode without checkpoints needs the list to show phase position and keep phases from silently disappearing.\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. Critique mode if existing structure is the constraint or the design must push back on it.\n\nNaming a file isn't grounding. Produce the traced model `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. Each candidate produces a design package shaped per `references\u002Frationale-template.md`: the caller's usage written first, then the type sketch, function signatures, module map, and prose rationale derived from it.\n\nUse independent runners inheriting the current session model. Give candidates distinct structural approaches to explore; no model or provider change is required.\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. Reject or revise shallow modules, information leakage, temporal decomposition, and pass-through methods.\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. The synthesis decision populates 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. That's the \"scaffold first\" mode of the **foundational-thinking** principle skill; subsequent commits read as filling in bodies against a stable contract. 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.\n\nDeviations from the sketch are signal worth surfacing, 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. Surface it; don't bolt it on.\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. Surfacing deviations is Phase D's job; a repeated pattern of them is Phase E's trigger.\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. The rewrite signal is repeated friction of the same shape, not single hard cases.\n\nWhen you scrap:\n\n1. Re-run the **how** skill over what's been built. The implementation lessons enter the new design as inputs, not vibes.\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\nDesign before implementing. Sketch types, function signatures, class shapes, and module boundaries with `not implemented` bodies and pseudocode. Synthesize across independent design perspectives, then fill in code against the chosen sketch. If implementation proves the sketch wrong, throw it out and redesign.\n\n## Start\n\nOpen a todolist with one entry per phase before starting. Autonomous mode without checkpoints needs the list to show phase position and keep phases from silently disappearing.\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. Critique mode if existing structure is the constraint or the design must push back on it.\n\nNaming a file isn't grounding. Produce the traced model `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. Each candidate produces a design package shaped per `references\u002Frationale-template.md`: the caller's usage written first, then the type sketch, function signatures, module map, and prose rationale derived from it.\n\nUse independent runners inheriting the current session model. Give candidates distinct structural approaches to explore; no model or provider change is required.\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. Reject or revise shallow modules, information leakage, temporal decomposition, and pass-through methods.\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. The synthesis decision populates 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. That's the \"scaffold first\" mode of the **foundational-thinking** principle skill; subsequent commits read as filling in bodies against a stable contract. 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.\n\nDeviations from the sketch are signal worth surfacing, 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. Surface it; don't bolt it on.\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. Surfacing deviations is Phase D's job; a repeated pattern of them is Phase E's trigger.\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. The rewrite signal is repeated friction of the same shape, not single hard cases.\n\nWhen you scrap:\n\n1. Re-run the **how** skill over what's been built. The implementation lessons enter the new design as inputs, not vibes.\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":24},true,"main","f63b9cfa707488880eeb9f47984fbf383e397322",".agents\u002Fskills\u002Fpstack\u002Farchitect",87,"https:\u002F\u002Fgithub.com\u002Fam-will\u002Fgooey-pi","https:\u002F\u002Fgithub.com\u002Fam-will","Context Engineer, Developer, Husband, Father","2026-10-25 13:02:03",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":24},[35,38,41],{"tool":36,"command":37},"npx","npx skills add am-will\u002Fgooey-pi --skill architect",{"tool":39,"command":40},"bunx","bunx skills add am-will\u002Fgooey-pi --skill architect",{"tool":42,"command":43},"pnpm","pnpm dlx skills add am-will\u002Fgooey-pi --skill architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fam-will\u002Fgooey-pi\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpstack\u002Farchitect\u002FSKILL.md",[46,52,56],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fdesign-red-flags.md","REFERENCE","参考文档",1944,"https:\u002F\u002Fgithub.com\u002Fam-will\u002Fgooey-pi\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpstack\u002Farchitect\u002Freferences\u002Fdesign-red-flags.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Frationale-template.md",3050,"https:\u002F\u002Fgithub.com\u002Fam-will\u002Fgooey-pi\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpstack\u002Farchitect\u002Freferences\u002Frationale-template.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Frunner-prompt.md",3111,"https:\u002F\u002Fgithub.com\u002Fam-will\u002Fgooey-pi\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpstack\u002Farchitect\u002Freferences\u002Frunner-prompt.md",[61,68,75,82,89,96],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7A8040XWQF3KCYT7G12G1TA","prime-work-schedules","Create, inspect, edit, pause, resume, run, and delete durable GooeyPi scheduled tasks. Use when the user asks to schedule recurring or one-time work in the current project or thread. Use rlm-heartbeat instead for temporary internal polling while actively working.","https:\u002F\u002Fgithub.com\u002Fam-will\u002Fgooey-pi\u002Fblob\u002Fmain\u002Fassets\u002Fskills\u002Fprime-work-schedules\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7A7ZYRC65CS56VJV4CVKWFV","prime-work-browser","Drive the GooeyPi in-app browser for this thread with the browser_* tools - open tabs, navigate, read pages, click, type, scroll, screenshot, and extract data. Use when the user asks to open, test, inspect, or interact with a website or a local dev server inside GooeyPi.","https:\u002F\u002Fgithub.com\u002Fam-will\u002Fgooey-pi\u002Fblob\u002Fmain\u002Fassets\u002Fskills\u002Fprime-work-browser\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7A7ZV00WXP2QFC5YPDJXTNV","gooeypi-computer-use","Drive native applications on macOS, Windows, or Linux through the separately installed TryCUA driver CLI.","https:\u002F\u002Fgithub.com\u002Fam-will\u002Fgooey-pi\u002Fblob\u002Fmain\u002Fassets\u002Fskills\u002Fgooeypi-computer-use\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7A7ZNTPXAJ17VX4MTAND91G","verify-gooeypi","Launch and drive the GooeyPi desktop (Electron) app to prove user-facing behavior — sidebar navigation, Settings, and Capabilities — capturing screenshots and ARIA snapshots. Reach for this when verifying a GooeyPi UI change or confirming the app still works end to end.","https:\u002F\u002Fgithub.com\u002Fam-will\u002Fgooey-pi\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fverify-gooeypi\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7A7ZK9FBXTZC33HEAJ4C3HW","review-pr-viability","Review a pull request or issue for value, implementation quality, maintainability, regression risk, and reliance on upstream changes.","https:\u002F\u002Fgithub.com\u002Fam-will\u002Fgooey-pi\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Freview-pr-viability\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7A7ZDK2B6KE9ZE33GS4V180","why","Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.","https:\u002F\u002Fgithub.com\u002Fam-will\u002Fgooey-pi\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpstack\u002Fwhy\u002FSKILL.md",[],[]]