[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75VTF79Y8M4E1V33BXNPJS3":3,"skill-same:01M75VTF79Y8M4E1V33BXNPJS3":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},"01M75VTF79Y8M4E1V33BXNPJS3","ask-matt",null,"Ask which skill or flow fits your situation. A router over the user-invoked skills in this repo.","gahjelle\u002Fkoalaty","gahjelle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F728076?v=4","01M75VTC8W2B5QA7KB4B9V1ZZP","Geir Arne Hjelle","01M75VTCB045WMQ7QCX6ESDRC3",1,"MIT","https:\u002F\u002Fgithub.com\u002Fgahjelle\u002Fkoalaty\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fask-matt\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: ask-matt\ndescription: Ask which skill or flow fits your situation. A router over the user-invoked 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.\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 `\u002Fgrill-me` — see Standalone.)\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-prd`** (turn the thread into a PRD) → **`\u002Fto-issues`** (split the PRD into independently-grabbable issues). Because the issues are independent, **clear context between each one**: start a fresh session per issue and kick off **`\u002Fimplement`** by passing it the PRD and the single issue to work on.\n   - **No** → **`\u002Fimplement`** right here, in the same context window.\n\n### Context hygiene\n\nKeep steps 1–3 in **one unbroken context window** — don't compact or clear until after `\u002Fto-issues` — so the grilling, PRD, and issues all build on the same thinking. Each `\u002Fimplement` then starts fresh, working from the issue.\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-issues`, 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. Issues that `\u002Fto-issues` produced are already agent-ready, so **don't triage them**.\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`.\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- **`\u002Fgrill-me`** — 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- **`\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.\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 `\u002Fgrill-me` — see Standalone.)\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-prd`** (turn the thread into a PRD) → **`\u002Fto-issues`** (split the PRD into independently-grabbable issues). Because the issues are independent, **clear context between each one**: start a fresh session per issue and kick off **`\u002Fimplement`** by passing it the PRD and the single issue to work on.\n   - **No** → **`\u002Fimplement`** right here, in the same context window.\n\n### Context hygiene\n\nKeep steps 1–3 in **one unbroken context window** — don't compact or clear until after `\u002Fto-issues` — so the grilling, PRD, and issues all build on the same thinking. Each `\u002Fimplement` then starts fresh, working from the issue.\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-issues`, 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. Issues that `\u002Fto-issues` produced are already agent-ready, so **don't triage them**.\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`.\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- **`\u002Fgrill-me`** — 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- **`\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","2ce876312b6a0f10550c2aedce874ca56f7d3df6",".agents\u002Fskills\u002Fask-matt",0,"https:\u002F\u002Fgithub.com\u002Fgahjelle\u002Fkoalaty","https:\u002F\u002Fgithub.com\u002Fgahjelle","2026-06-27 08:32:31",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":24},[34,37,40],{"tool":35,"command":36},"npx","npx skills add gahjelle\u002Fkoalaty --skill ask-matt",{"tool":38,"command":39},"bunx","bunx skills add gahjelle\u002Fkoalaty --skill ask-matt",{"tool":41,"command":42},"pnpm","pnpm dlx skills add gahjelle\u002Fkoalaty --skill ask-matt","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgahjelle\u002Fkoalaty\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fask-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},"01M75VYPDPMFSN2TFWA2VVH5XH","writing-great-skills","Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.","https:\u002F\u002Fgithub.com\u002Fgahjelle\u002Fkoalaty\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Fwriting-great-skills\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},"01M75VYKSA7CY2M6XQX31MN25W","triage","Move issues through a state machine of triage roles — categorise, reproduce, grill if needed, and write agent-ready briefs.","https:\u002F\u002Fgithub.com\u002Fgahjelle\u002Fkoalaty\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Ftriage\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},"01M75VYHXPF87ZYWEGR6XZ5YHY","to-prd","Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.","https:\u002F\u002Fgithub.com\u002Fgahjelle\u002Fkoalaty\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Fto-prd\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},"01M75VYEY7MPKGW7XGMYP60PWS","to-issues","Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.","https:\u002F\u002Fgithub.com\u002Fgahjelle\u002Fkoalaty\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Fto-issues\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},"01M75VYD2ZN01F1CPSWSDAXWN0","teach","Teach the user a new skill or concept, within this workspace.","https:\u002F\u002Fgithub.com\u002Fgahjelle\u002Fkoalaty\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Fteach\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},"01M75VYAHEBQSPVWEGVFZN3A9V","tdd","Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions \"red-green-refactor\", or wants integration tests.","https:\u002F\u002Fgithub.com\u002Fgahjelle\u002Fkoalaty\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Ftdd\u002FSKILL.md",[],[]]