[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72SV6SPB0TC0YMMX159KV30":3,"skill-same:01M72SV6SPB0TC0YMMX159KV30":45},{"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":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":44},"01M72SV6SPB0TC0YMMX159KV30","matt-pocock-ask-matt",null,"Ask which skill or flow fits your situation. A router over the skills in this repo.","NickSuomi\u002Fmorpheus","NickSuomi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F79413822?v=4","01M72STZM7GHTS3H3CTJ2N217T","nicksuomi","01M72STZN7EW8D5FH93RPKFTVH",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FNickSuomi\u002Fmorpheus\u002Fblob\u002Fmain\u002Fpackages\u002Fruntime\u002Fbundled-skills\u002Fmatt-pocock-ask-matt\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: matt-pocock-ask-matt\ndescription: Ask which skill or flow fits your situation. A router over the skills in this repo.\ndisable-model-invocation: true\n---\n\n# Ask Matt\n\nYou don't remember every skill, so ask.\n\nA **flow** is a path through the skills. Most paths run along one **main flow**, and two **on-ramps** merge onto it. Everything else is standalone, or a vocabulary layer that runs underneath.\n\n## The main flow: idea → ship\n\nThe route most work travels. You have an idea and want it built.\n\n1. **`\u002Fgrill-with-docs`** — sharpen the idea by interview. Start here when you **have a codebase**: it's stateful, retaining what it learns in `CONTEXT.md` and ADRs. (No codebase? Use `\u002Fgrilling` in stateless mode; `grill-with-docs` is the one that leaves a paper trail.)\n2. **Branch — can you settle every question in conversation?** If a question needs a runnable answer (state, business logic, a UI you have to see), detour through a prototype, bridged by **`\u002Fhandoff`** in both directions (see Crossing sessions):\n   - **`\u002Fhandoff`** out, then open a fresh session against that file,\n   - **`\u002Fprototype`** to answer the question with throwaway code,\n   - **`\u002Fhandoff`** back what you learned, and reference it from the original idea thread.\n3. **Branch — is this a multi-session build?**\n   - **Yes** → **`\u002Fto-spec`** (turn the thread into a spec), then **`\u002Fto-tickets`** to split it into tracer-bullet tickets, each declaring its **blocking edges**. On a local tracker that's one file per ticket under `.scratch\u002F\u003Cfeature>\u002Fissues\u002F`, worked blockers-first by hand; on a real tracker the edges become native blocking links, so any ticket whose blockers are done can be grabbed — kick off **`\u002Fimplement`** per ticket, **clearing context between each one**.\n   - **No** → **`\u002Fimplement`** right here, in the same context window.\n\n   Either way, **`\u002Fimplement`** builds each issue by driving **`\u002Ftdd`** internally — one red-green slice at a time — then closes out by running **`\u002Fcode-review`**, a two-axis review (Standards + Spec) of the diff, before committing. Reach for **`\u002Ftdd`** on its own when you just want to build a concrete behaviour test-first without a full spec, and **`\u002Fcode-review`** on its own whenever you want to review a branch or PR against a fixed point.\n\n### Context hygiene\n\nKeep steps 1–3 in **one unbroken context window** — don't compact or clear until after `\u002Fto-tickets` — so the grilling, spec, and tickets all build on the same thinking. Each `\u002Fimplement` then starts fresh, working from the ticket.\n\nThe limit on this is the **[smart zone](https:\u002F\u002Fwww.aihero.dev\u002Fai-coding-dictionary\u002Fsmart-zone)**: the window (~120k tokens on state-of-the-art models) within which the model still reasons sharply. If a session approaches it before `\u002Fto-tickets`, don't push on degraded — `\u002Fhandoff` and continue in a fresh thread.\n\n## On-ramps\n\nA starting situation that generates work, then merges onto the main flow.\n\n- **Bugs and requests piling up** → **`\u002Ftriage`**. It moves issues through triage roles and produces agent-ready issues, which **`\u002Fimplement`** later picks up.\n\n  Triage is only for issues **you didn't create** — bug reports, incoming feature requests, anything that arrives raw. Tickets that `\u002Fto-tickets` produced are already agent-ready, so **don't triage them**.\n\n- **Something's broken** → **`\u002Fdiagnosing-bugs`**. For the hard ones: the bug that resists a first glance, the intermittent flake, the regression that crept in between two known-good states. It refuses to theorise until it has a **tight feedback loop** — one command that already goes red on *this* bug — then fixes with a regression test. Its post-mortem hands off to **`\u002Fimprove-codebase-architecture`** when the real finding is that there's no good seam to lock the bug down.\n\n- **A huge, foggy effort — a greenfield project or a huge feature build, too big for one session** → **`\u002Fwayfinder`**. When the way from here to the destination isn't visible yet, it charts a **shared map** of investigation tickets on the issue tracker and resolves them one at a time — producing **decisions, not deliverables** — until the fog is pushed back and the way is clear. Then it merges onto the main flow at **`\u002Fto-spec`** (or, if the effort turned out small enough, straight to **`\u002Fimplement`**). Where **`\u002Fgrill-with-docs`** sharpens an idea you can hold in one session, wayfinder is for the idea you can't.\n\n## Codebase health\n\nNot feature work — upkeep.\n\n- **`\u002Fimprove-codebase-architecture`** — run whenever you have a spare moment to keep the codebase good for agents to operate in. It surfaces **deepening opportunities**; picking one _generates an idea_ you can take into the main flow at `\u002Fgrill-with-docs`. It's the survey that finds the candidates; **`\u002Fcodebase-design`** (below) is the bench you design the chosen one on.\n\n## Vocabulary underneath\n\nTwo model-invoked references that run *beneath* the other skills — each the single source of truth for its vocabulary. Reach for them directly when the **words**, not the process, are the problem; or let the skills above pull them in.\n\n- **`\u002Fdomain-modeling`** — sharpen the project's *domain* language: challenge a fuzzy term, resolve an overloaded word (\"account\" doing three jobs), record a hard-to-reverse decision as an ADR. It's the active discipline `\u002Fgrill-with-docs` drives to keep `CONTEXT.md` a clean glossary.\n- **`\u002Fcodebase-design`** — the deep-module vocabulary (module, interface, depth, seam, adapter, leverage, locality) for designing a module's *shape*: a lot of behaviour behind a small interface at a clean seam. `\u002Ftdd` and `\u002Fimprove-codebase-architecture` both speak it.\n\n## Crossing sessions\n\n- **`\u002Fhandoff`** — when a thread is full or you need to branch off (e.g. into a `\u002Fprototype` session), this compacts the conversation into a markdown file. You don't continue in place — you **open a new session and reference that file** to carry the context across. It's the bridge between context windows, in either direction. Use it when you want a **fresh session** but need the **current conversation preserved**.\n- **`\u002Fcompact`** (built-in) — stay in the **same conversation**, letting the earlier turns be summarized. Use it at **intentional breaks between phases**, when you don't mind losing the verbatim history. Don't compact mid-phase — the agent can lose its way. `\u002Fhandoff` forks; `\u002Fcompact` continues.\n\n## Standalone\n\nOff the main flow entirely.\n\n- **`\u002Fgrilling`** — the same relentless interview as `\u002Fgrill-with-docs`, but for when you have **no codebase**. Stateless: it saves nothing locally, builds no `CONTEXT.md`. Reach for it to sharpen any plan or design that doesn't live in a repo.\n- **`\u002Fprototype`** — a small, throwaway program that answers one design question: does this state model feel right, or what should this UI look like. Throwaway from day one — keep the answer, delete the code. It's the detour in step 2 of the main flow, but reach for it any time a design question is hard to settle on paper.\n- **`\u002Fresearch`** — delegate reading legwork to a **background agent**: it investigates a question against **primary sources**, then leaves a cited Markdown file in the repo. Keep working while it reads. The file it produces is something to take *into* the main flow at `\u002Fgrill-with-docs` — research feeds the thinking, it doesn't replace it.\n- **`\u002Fteach`** — learn a concept over multiple sessions, using the current directory as a stateful workspace.\n- **`\u002Fwriting-great-skills`** — reference for writing and editing skills well.\n\n## Precondition\n\n**`\u002Fsetup-matt-pocock-skills`** — run before your first engineering flow to configure the issue tracker, triage labels, and doc layout the other skills assume. Custom issue trackers also work.\n","# Ask Matt\n\nYou don't remember every skill, so ask.\n\nA **flow** is a path through the skills. Most paths run along one **main flow**, and two **on-ramps** merge onto it. Everything else is standalone, or a vocabulary layer that runs underneath.\n\n## The main flow: idea → ship\n\nThe route most work travels. You have an idea and want it built.\n\n1. **`\u002Fgrill-with-docs`** — sharpen the idea by interview. Start here when you **have a codebase**: it's stateful, retaining what it learns in `CONTEXT.md` and ADRs. (No codebase? Use `\u002Fgrilling` in stateless mode; `grill-with-docs` is the one that leaves a paper trail.)\n2. **Branch — can you settle every question in conversation?** If a question needs a runnable answer (state, business logic, a UI you have to see), detour through a prototype, bridged by **`\u002Fhandoff`** in both directions (see Crossing sessions):\n   - **`\u002Fhandoff`** out, then open a fresh session against that file,\n   - **`\u002Fprototype`** to answer the question with throwaway code,\n   - **`\u002Fhandoff`** back what you learned, and reference it from the original idea thread.\n3. **Branch — is this a multi-session build?**\n   - **Yes** → **`\u002Fto-spec`** (turn the thread into a spec), then **`\u002Fto-tickets`** to split it into tracer-bullet tickets, each declaring its **blocking edges**. On a local tracker that's one file per ticket under `.scratch\u002F\u003Cfeature>\u002Fissues\u002F`, worked blockers-first by hand; on a real tracker the edges become native blocking links, so any ticket whose blockers are done can be grabbed — kick off **`\u002Fimplement`** per ticket, **clearing context between each one**.\n   - **No** → **`\u002Fimplement`** right here, in the same context window.\n\n   Either way, **`\u002Fimplement`** builds each issue by driving **`\u002Ftdd`** internally — one red-green slice at a time — then closes out by running **`\u002Fcode-review`**, a two-axis review (Standards + Spec) of the diff, before committing. Reach for **`\u002Ftdd`** on its own when you just want to build a concrete behaviour test-first without a full spec, and **`\u002Fcode-review`** on its own whenever you want to review a branch or PR against a fixed point.\n\n### Context hygiene\n\nKeep steps 1–3 in **one unbroken context window** — don't compact or clear until after `\u002Fto-tickets` — so the grilling, spec, and tickets all build on the same thinking. Each `\u002Fimplement` then starts fresh, working from the ticket.\n\nThe limit on this is the **[smart zone](https:\u002F\u002Fwww.aihero.dev\u002Fai-coding-dictionary\u002Fsmart-zone)**: the window (~120k tokens on state-of-the-art models) within which the model still reasons sharply. If a session approaches it before `\u002Fto-tickets`, don't push on degraded — `\u002Fhandoff` and continue in a fresh thread.\n\n## On-ramps\n\nA starting situation that generates work, then merges onto the main flow.\n\n- **Bugs and requests piling up** → **`\u002Ftriage`**. It moves issues through triage roles and produces agent-ready issues, which **`\u002Fimplement`** later picks up.\n\n  Triage is only for issues **you didn't create** — bug reports, incoming feature requests, anything that arrives raw. Tickets that `\u002Fto-tickets` produced are already agent-ready, so **don't triage them**.\n\n- **Something's broken** → **`\u002Fdiagnosing-bugs`**. For the hard ones: the bug that resists a first glance, the intermittent flake, the regression that crept in between two known-good states. It refuses to theorise until it has a **tight feedback loop** — one command that already goes red on *this* bug — then fixes with a regression test. Its post-mortem hands off to **`\u002Fimprove-codebase-architecture`** when the real finding is that there's no good seam to lock the bug down.\n\n- **A huge, foggy effort — a greenfield project or a huge feature build, too big for one session** → **`\u002Fwayfinder`**. When the way from here to the destination isn't visible yet, it charts a **shared map** of investigation tickets on the issue tracker and resolves them one at a time — producing **decisions, not deliverables** — until the fog is pushed back and the way is clear. Then it merges onto the main flow at **`\u002Fto-spec`** (or, if the effort turned out small enough, straight to **`\u002Fimplement`**). Where **`\u002Fgrill-with-docs`** sharpens an idea you can hold in one session, wayfinder is for the idea you can't.\n\n## Codebase health\n\nNot feature work — upkeep.\n\n- **`\u002Fimprove-codebase-architecture`** — run whenever you have a spare moment to keep the codebase good for agents to operate in. It surfaces **deepening opportunities**; picking one _generates an idea_ you can take into the main flow at `\u002Fgrill-with-docs`. It's the survey that finds the candidates; **`\u002Fcodebase-design`** (below) is the bench you design the chosen one on.\n\n## Vocabulary underneath\n\nTwo model-invoked references that run *beneath* the other skills — each the single source of truth for its vocabulary. Reach for them directly when the **words**, not the process, are the problem; or let the skills above pull them in.\n\n- **`\u002Fdomain-modeling`** — sharpen the project's *domain* language: challenge a fuzzy term, resolve an overloaded word (\"account\" doing three jobs), record a hard-to-reverse decision as an ADR. It's the active discipline `\u002Fgrill-with-docs` drives to keep `CONTEXT.md` a clean glossary.\n- **`\u002Fcodebase-design`** — the deep-module vocabulary (module, interface, depth, seam, adapter, leverage, locality) for designing a module's *shape*: a lot of behaviour behind a small interface at a clean seam. `\u002Ftdd` and `\u002Fimprove-codebase-architecture` both speak it.\n\n## Crossing sessions\n\n- **`\u002Fhandoff`** — when a thread is full or you need to branch off (e.g. into a `\u002Fprototype` session), this compacts the conversation into a markdown file. You don't continue in place — you **open a new session and reference that file** to carry the context across. It's the bridge between context windows, in either direction. Use it when you want a **fresh session** but need the **current conversation preserved**.\n- **`\u002Fcompact`** (built-in) — stay in the **same conversation**, letting the earlier turns be summarized. Use it at **intentional breaks between phases**, when you don't mind losing the verbatim history. Don't compact mid-phase — the agent can lose its way. `\u002Fhandoff` forks; `\u002Fcompact` continues.\n\n## Standalone\n\nOff the main flow entirely.\n\n- **`\u002Fgrilling`** — the same relentless interview as `\u002Fgrill-with-docs`, but for when you have **no codebase**. Stateless: it saves nothing locally, builds no `CONTEXT.md`. Reach for it to sharpen any plan or design that doesn't live in a repo.\n- **`\u002Fprototype`** — a small, throwaway program that answers one design question: does this state model feel right, or what should this UI look like. Throwaway from day one — keep the answer, delete the code. It's the detour in step 2 of the main flow, but reach for it any time a design question is hard to settle on paper.\n- **`\u002Fresearch`** — delegate reading legwork to a **background agent**: it investigates a question against **primary sources**, then leaves a cited Markdown file in the repo. Keep working while it reads. The file it produces is something to take *into* the main flow at `\u002Fgrill-with-docs` — research feeds the thinking, it doesn't replace it.\n- **`\u002Fteach`** — learn a concept over multiple sessions, using the current directory as a stateful workspace.\n- **`\u002Fwriting-great-skills`** — reference for writing and editing skills well.\n\n## Precondition\n\n**`\u002Fsetup-matt-pocock-skills`** — run before your first engineering flow to configure the issue tracker, triage labels, and doc layout the other skills assume. Custom issue trackers also work.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","0e23c08904ca612c8e13c47b92e931aee35ba17d","packages\u002Fruntime\u002Fbundled-skills\u002Fmatt-pocock-ask-matt",0,"https:\u002F\u002Fgithub.com\u002FNickSuomi\u002Fmorpheus","https:\u002F\u002Fgithub.com\u002FNickSuomi","2026-09-30 11:36:16",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":24},[34,37,40],{"tool":35,"command":36},"npx","npx skills add NickSuomi\u002Fmorpheus --skill matt-pocock-ask-matt",{"tool":38,"command":39},"bunx","bunx skills add NickSuomi\u002Fmorpheus --skill matt-pocock-ask-matt",{"tool":41,"command":42},"pnpm","pnpm dlx skills add NickSuomi\u002Fmorpheus --skill matt-pocock-ask-matt","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNickSuomi\u002Fmorpheus\u002Fblob\u002Fmain\u002Fpackages\u002Fruntime\u002Fbundled-skills\u002Fmatt-pocock-ask-matt\u002FSKILL.md",[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M72SY50253N686JJJZAE7YGJ","matt-pocock-writing-shape","Writing, exploit — shape raw material into an article, paragraph by paragraph.","https:\u002F\u002Fgithub.com\u002FNickSuomi\u002Fmorpheus\u002Fblob\u002Fmain\u002Fpackages\u002Fruntime\u002Fbundled-skills\u002Fmatt-pocock-writing-shape\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M72SY1YHA30ZTJQRS9Y3QA1K","matt-pocock-writing-great-skills","Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.","https:\u002F\u002Fgithub.com\u002FNickSuomi\u002Fmorpheus\u002Fblob\u002Fmain\u002Fpackages\u002Fruntime\u002Fbundled-skills\u002Fmatt-pocock-writing-great-skills\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M72SXZBA993FT9XKANG0T3RG","matt-pocock-writing-fragments","Writing, explore — mine raw fragments, no structure yet.","https:\u002F\u002Fgithub.com\u002FNickSuomi\u002Fmorpheus\u002Fblob\u002Fmain\u002Fpackages\u002Fruntime\u002Fbundled-skills\u002Fmatt-pocock-writing-fragments\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M72SXXC8J36HRMW3MD4F3ZT9","matt-pocock-writing-beats","Writing, exploit — assemble raw material into a journey of beats, grounding each term before a beat leans on it.","https:\u002F\u002Fgithub.com\u002FNickSuomi\u002Fmorpheus\u002Fblob\u002Fmain\u002Fpackages\u002Fruntime\u002Fbundled-skills\u002Fmatt-pocock-writing-beats\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M72SXTHD3B6HMK8CECZ1Z0T8","matt-pocock-wizard","Generate an interactive bash wizard that walks a human through a manual procedure — third-party setup, a one-off migration, an A→B state transition — opening URLs, capturing values, confirming each step, and writing .env files and GitHub Actions secrets.","https:\u002F\u002Fgithub.com\u002FNickSuomi\u002Fmorpheus\u002Fblob\u002Fmain\u002Fpackages\u002Fruntime\u002Fbundled-skills\u002Fmatt-pocock-wizard\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M72SXQ1VR21MR9K7A7Y5BRHG","matt-pocock-wayfinder","Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002FNickSuomi\u002Fmorpheus\u002Fblob\u002Fmain\u002Fpackages\u002Fruntime\u002Fbundled-skills\u002Fmatt-pocock-wayfinder\u002FSKILL.md",[],[]]