From e112a6b03cd7893a36760fea1d387dffa6cba80a Mon Sep 17 00:00:00 2001 From: Matt Pocock Date: Wed, 17 Jun 2026 14:19:52 +0100 Subject: [PATCH] Remove zoom-out skill and all references Co-Authored-By: Claude Opus 4.8 (1M context) --- .claude-plugin/plugin.json | 1 - README.md | 2 -- ...01-explicit-setup-pointer-only-for-hard-dependencies.md | 2 +- skills/engineering/README.md | 1 - skills/engineering/zoom-out/SKILL.md | 7 ------- 5 files changed, 1 insertion(+), 12 deletions(-) delete mode 100644 skills/engineering/zoom-out/SKILL.md diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json index 174bcbc..fdf6f50 100644 --- a/.claude-plugin/plugin.json +++ b/.claude-plugin/plugin.json @@ -9,7 +9,6 @@ "./skills/engineering/tdd", "./skills/engineering/to-issues", "./skills/engineering/to-prd", - "./skills/engineering/zoom-out", "./skills/engineering/prototype", "./skills/engineering/domain-modeling", "./skills/engineering/codebase-design", diff --git a/README.md b/README.md index 672320b..ba5ea70 100644 --- a/README.md +++ b/README.md @@ -132,7 +132,6 @@ For debugging, I've also built a **[`/diagnosing-bugs`](./skills/engineering/dia This is built in to every layer of these skills: - [`/to-prd`](./skills/engineering/to-prd/SKILL.md) quizzes you about which modules you're touching before creating a PRD -- [`/zoom-out`](./skills/engineering/zoom-out/SKILL.md) tells the agent to explain code in the context of the whole system And crucially, [`/improve-codebase-architecture`](./skills/engineering/improve-codebase-architecture/SKILL.md) helps you rescue a codebase that has become a ball of mud. I recommend running it on your codebase once every few days. @@ -156,7 +155,6 @@ Skills I use daily for code work. - **[setup-matt-pocock-skills](./skills/engineering/setup-matt-pocock-skills/SKILL.md)** — Configure this repo for the engineering skills (issue tracker, triage labels, domain doc layout). Run once per repo before using the other engineering skills. - **[to-issues](./skills/engineering/to-issues/SKILL.md)** — Break any plan, spec, or PRD into independently-grabbable issues using vertical slices. - **[to-prd](./skills/engineering/to-prd/SKILL.md)** — Turn the current conversation into a PRD and publish it to the issue tracker. No interview — just synthesizes what you've already discussed. -- **[zoom-out](./skills/engineering/zoom-out/SKILL.md)** — Ask the agent to zoom out a level and map the relevant modules and callers on an unfamiliar section of code. - **[prototype](./skills/engineering/prototype/SKILL.md)** — Build a throwaway prototype to flesh out a design — either a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. **Model-invoked** diff --git a/docs/adr/0001-explicit-setup-pointer-only-for-hard-dependencies.md b/docs/adr/0001-explicit-setup-pointer-only-for-hard-dependencies.md index 7636786..37918f9 100644 --- a/docs/adr/0001-explicit-setup-pointer-only-for-hard-dependencies.md +++ b/docs/adr/0001-explicit-setup-pointer-only-for-hard-dependencies.md @@ -5,6 +5,6 @@ Engineering skills depend on per-repo config (issue tracker, triage label vocabu We split these into **hard-dependency** and **soft-dependency** skills: - **Hard dependency** (`to-issues`, `to-prd`, `triage`) — include an explicit one-liner: _"… should have been provided to you — run `/setup-matt-pocock-skills` if not."_ Without the mapping, output is wrong, not just fuzzy. -- **Soft dependency** (`diagnose`, `tdd`, `improve-codebase-architecture`, `zoom-out`) — reference "the project's domain glossary" and "ADRs in the area you're touching" in vague prose only. If the docs aren't there, the skill still works; output is just less sharp. +- **Soft dependency** (`diagnose`, `tdd`, `improve-codebase-architecture`) — reference "the project's domain glossary" and "ADRs in the area you're touching" in vague prose only. If the docs aren't there, the skill still works; output is just less sharp. The split keeps soft-dependency skills token-light and avoids cargo-culting the setup pointer into places where it isn't load-bearing. diff --git a/skills/engineering/README.md b/skills/engineering/README.md index bdec4f2..444cb43 100644 --- a/skills/engineering/README.md +++ b/skills/engineering/README.md @@ -12,7 +12,6 @@ Reachable only when you type them (`disable-model-invocation: true`). - **[setup-matt-pocock-skills](./setup-matt-pocock-skills/SKILL.md)** — Configure this repo for the engineering skills (issue tracker, triage labels, domain doc layout). Run once per repo. - **[to-issues](./to-issues/SKILL.md)** — Break any plan, spec, or PRD into independently-grabbable issues using vertical slices. - **[to-prd](./to-prd/SKILL.md)** — Turn the current conversation into a PRD and publish it to the issue tracker. -- **[zoom-out](./zoom-out/SKILL.md)** — Ask the agent to zoom out a level and map the relevant modules and callers. - **[prototype](./prototype/SKILL.md)** — Build a throwaway prototype — a runnable terminal app for state/logic questions, or several toggleable UI variations. ## Model-invoked diff --git a/skills/engineering/zoom-out/SKILL.md b/skills/engineering/zoom-out/SKILL.md deleted file mode 100644 index 8cc007c..0000000 --- a/skills/engineering/zoom-out/SKILL.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -name: zoom-out -description: Ask the agent to zoom out a level and map the relevant modules and callers using the project's domain language. -disable-model-invocation: true ---- - -I don't know this area of code well. Go up a layer of abstraction. Give me a map of all the relevant modules and callers, using the project's domain glossary vocabulary.