agent-notes 2.30.0__tar.gz → 2.32.0__tar.gz

{agent_notes-2.30.0 → agent_notes-2.32.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agent-notes
-Version: 2.30.0
+Version: 2.32.0
 Summary: AI agent configuration manager for Claude Code, OpenCode, and Copilot
 Author-email: Eugene Naumov <min.verkligheten@gmail.com>
 License-Expression: MIT
@@ -44,8 +44,8 @@ agent-notes doctor
 
 **What's Included**
 - 19 specialized AI subagents (Opus reasons, Sonnet executes, Haiku explores)
-- 47+ on-demand skills (Rails, Docker, Git, Kamal, Process)
-- Global rules and guardrails
+- 50+ on-demand skills (Rails, Docker, Git, Kamal, Process)
+- Global rules and guardrails (including a ban on AI self-attribution in commits/PRs)
 - Agent memory with 3 storage options (Local, Obsidian, Wiki)
 - Configuration for Claude Code, OpenCode, and GitHub Copilot
 
@@ -282,7 +282,7 @@ agent-notes memory lint               # health-check
 <details>
 <summary>Skills</summary>
 
-47+ on-demand knowledge modules across Rails, Docker, Kamal, Git, and Process. Run `agent-notes list skills` for the current list, or browse `agent_notes/data/skills/`.
+50+ on-demand knowledge modules across Rails, Docker, Kamal, Git, and Process. Run `agent-notes list skills` for the current list, or browse `agent_notes/data/skills/`.
 
 The session context hook auto-generates a skill index from SKILL.md frontmatter at install time, so agents always know what skills are available without loading full skill content. This keeps context overhead low while maintaining skill discoverability.
 
@@ -297,26 +297,29 @@ Load the docker-compose skill for multi-service setup
 
 | Failure mode | What goes wrong | Skills that help |
 |---|---|---|
-| Misalignment | Claude starts building before the problem is resolved | `/grill-me`, `/grill-with-docs` |
-| Verbosity | Responses are bloated; context window fills with noise | `/caveman`, `/setup-project-context` |
-| Broken code | Claude codes without a feedback loop or evidence trail | `/tdd` (improved), `/debugging-protocol` (improved) |
-| Ball of mud | Architecture drifts; modules grow shallow and tangled | `/improve-codebase-architecture`, `/zoom-out` |
+| Misalignment | Claude starts building before the problem is resolved | `/grill-me`, `/grilling`, `/grill-with-docs` |
+| Vague scope | Work starts without a spec or ticketed breakdown | `/to-spec`, `/to-tickets`, `/wayfinder`, `/triage` |
+| Broken code | Claude codes without a feedback loop or evidence trail | `/tdd`, `/diagnosing-bugs` |
+| Ball of mud | Architecture drifts; modules grow shallow and tangled | `/improve-codebase-architecture`, `/codebase-design`, `/domain-modeling` |
 
 **Skill descriptions:**
 
-- `/grill-me` — Interview the user until the problem is fully resolved before touching code
+- `/grill-me`, `/grilling` — Interview the user relentlessly until the plan is fully resolved before touching code
 - `/grill-with-docs` — Same, but cross-references CONTEXT.md and ADRs and updates them inline
-- `/caveman` — Ultra-compressed reply mode (~75% token savings) for rapid iteration
-- `/setup-project-context` — Bootstraps a CONTEXT.md domain glossary (ubiquitous language)
-- `/tdd` — RED-GREEN-REFACTOR with tracer-bullet vertical slices; horizontal-slicing anti-pattern added
-- `/debugging-protocol` — Phase 1 rewritten as "build a feedback loop first" with 9 strategies
-- `/improve-codebase-architecture` — Deletion test to find shallow modules; surfaces deepening opportunities
-- `/zoom-out` — Quick orientation map of an unfamiliar code area
+- `/tdd` — RED-GREEN-REFACTOR with tracer-bullet vertical slices; integration-first testing
+- `/diagnosing-bugs` — Diagnosis loop for hard bugs and performance regressions (build a feedback loop first)
+- `/improve-codebase-architecture` — Scan for deepening opportunities, present a visual HTML report, then grill the chosen one
+- `/codebase-design` — Shared vocabulary for designing deep modules and choosing where seams go
+- `/domain-modeling` — Pin down ubiquitous language, maintain a CONTEXT.md glossary and ADRs
 - `/handoff` — Compact conversation into a handoff document for a fresh agent session
-- `/to-prd` — Synthesize conversation into a Product Requirements Document
-- `/to-issues` — Break a plan/PRD into vertical-slice issues (HITL/AFK classification)
+- `/to-spec` — Synthesize the current conversation into a spec and publish it to the issue tracker
+- `/to-tickets` — Break a plan/spec into tracer-bullet tickets with declared blocking edges
+- `/wayfinder` — Plan work larger than one agent session as a map of investigation tickets
+- `/triage` — Move issues and external PRs through a triage state machine into agent-ready briefs
+- `/research` — Investigate a question against primary sources and capture findings as Markdown
 - `/prototype` — Throwaway prototypes: terminal app for logic or UI variations for visual
-- `/write-a-skill` — Meta-skill for creating new skills with proper structure
+- `/setup-agent-tracker` — One-time per-repo setup of the issue tracker, triage labels, and domain doc layout
+- `/writing-great-skills` — Reference for writing and editing skills well
 
 </details>
 
@@ -509,7 +512,7 @@ See [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md), [docs/ADD_CLI.md](docs/ADD_CLI
 ## Inspired by
 
 - [Andrej Karpathy's LLM Wiki](https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f) — The wiki memory backend implements his compile-once, query-forever knowledge pattern with structured page types and three core operations (ingest, query, lint)
-- [Matt Pocock's skills repo](https://github.com/mattpocock/skills) — Skill format (SKILL.md per directory), failure-mode table (misalignment, verbosity, broken code, architectural degradation), and several core skills (tdd, grill-me, grill-with-docs, improve-codebase-architecture, zoom-out, caveman)
+- [Matt Pocock's skills repo](https://github.com/mattpocock/skills) — Skill format (SKILL.md per directory), failure-mode table (misalignment, broken code, architectural degradation), and a set of engineering/productivity skills vendored from the upstream repo (tdd, grill-me, grilling, grill-with-docs, diagnosing-bugs, improve-codebase-architecture, codebase-design, domain-modeling, prototype, handoff, research, to-spec, to-tickets, triage, wayfinder, writing-great-skills). Last synced from upstream commit [`391a270`](https://github.com/mattpocock/skills/commit/391a2701dd948f94f56a39f7533f8eea9a859c87) (2026-07-10), reviewed for prompt-injection before import.
 
 ## License
 

{agent_notes-2.30.0 → agent_notes-2.32.0}/README.md

@@ -12,8 +12,8 @@ agent-notes doctor
 
 **What's Included**
 - 19 specialized AI subagents (Opus reasons, Sonnet executes, Haiku explores)
-- 47+ on-demand skills (Rails, Docker, Git, Kamal, Process)
-- Global rules and guardrails
+- 50+ on-demand skills (Rails, Docker, Git, Kamal, Process)
+- Global rules and guardrails (including a ban on AI self-attribution in commits/PRs)
 - Agent memory with 3 storage options (Local, Obsidian, Wiki)
 - Configuration for Claude Code, OpenCode, and GitHub Copilot
 
@@ -250,7 +250,7 @@ agent-notes memory lint               # health-check
 <details>
 <summary>Skills</summary>
 
-47+ on-demand knowledge modules across Rails, Docker, Kamal, Git, and Process. Run `agent-notes list skills` for the current list, or browse `agent_notes/data/skills/`.
+50+ on-demand knowledge modules across Rails, Docker, Kamal, Git, and Process. Run `agent-notes list skills` for the current list, or browse `agent_notes/data/skills/`.
 
 The session context hook auto-generates a skill index from SKILL.md frontmatter at install time, so agents always know what skills are available without loading full skill content. This keeps context overhead low while maintaining skill discoverability.
 
@@ -265,26 +265,29 @@ Load the docker-compose skill for multi-service setup
 
 | Failure mode | What goes wrong | Skills that help |
 |---|---|---|
-| Misalignment | Claude starts building before the problem is resolved | `/grill-me`, `/grill-with-docs` |
-| Verbosity | Responses are bloated; context window fills with noise | `/caveman`, `/setup-project-context` |
-| Broken code | Claude codes without a feedback loop or evidence trail | `/tdd` (improved), `/debugging-protocol` (improved) |
-| Ball of mud | Architecture drifts; modules grow shallow and tangled | `/improve-codebase-architecture`, `/zoom-out` |
+| Misalignment | Claude starts building before the problem is resolved | `/grill-me`, `/grilling`, `/grill-with-docs` |
+| Vague scope | Work starts without a spec or ticketed breakdown | `/to-spec`, `/to-tickets`, `/wayfinder`, `/triage` |
+| Broken code | Claude codes without a feedback loop or evidence trail | `/tdd`, `/diagnosing-bugs` |
+| Ball of mud | Architecture drifts; modules grow shallow and tangled | `/improve-codebase-architecture`, `/codebase-design`, `/domain-modeling` |
 
 **Skill descriptions:**
 
-- `/grill-me` — Interview the user until the problem is fully resolved before touching code
+- `/grill-me`, `/grilling` — Interview the user relentlessly until the plan is fully resolved before touching code
 - `/grill-with-docs` — Same, but cross-references CONTEXT.md and ADRs and updates them inline
-- `/caveman` — Ultra-compressed reply mode (~75% token savings) for rapid iteration
-- `/setup-project-context` — Bootstraps a CONTEXT.md domain glossary (ubiquitous language)
-- `/tdd` — RED-GREEN-REFACTOR with tracer-bullet vertical slices; horizontal-slicing anti-pattern added
-- `/debugging-protocol` — Phase 1 rewritten as "build a feedback loop first" with 9 strategies
-- `/improve-codebase-architecture` — Deletion test to find shallow modules; surfaces deepening opportunities
-- `/zoom-out` — Quick orientation map of an unfamiliar code area
+- `/tdd` — RED-GREEN-REFACTOR with tracer-bullet vertical slices; integration-first testing
+- `/diagnosing-bugs` — Diagnosis loop for hard bugs and performance regressions (build a feedback loop first)
+- `/improve-codebase-architecture` — Scan for deepening opportunities, present a visual HTML report, then grill the chosen one
+- `/codebase-design` — Shared vocabulary for designing deep modules and choosing where seams go
+- `/domain-modeling` — Pin down ubiquitous language, maintain a CONTEXT.md glossary and ADRs
 - `/handoff` — Compact conversation into a handoff document for a fresh agent session
-- `/to-prd` — Synthesize conversation into a Product Requirements Document
-- `/to-issues` — Break a plan/PRD into vertical-slice issues (HITL/AFK classification)
+- `/to-spec` — Synthesize the current conversation into a spec and publish it to the issue tracker
+- `/to-tickets` — Break a plan/spec into tracer-bullet tickets with declared blocking edges
+- `/wayfinder` — Plan work larger than one agent session as a map of investigation tickets
+- `/triage` — Move issues and external PRs through a triage state machine into agent-ready briefs
+- `/research` — Investigate a question against primary sources and capture findings as Markdown
 - `/prototype` — Throwaway prototypes: terminal app for logic or UI variations for visual
-- `/write-a-skill` — Meta-skill for creating new skills with proper structure
+- `/setup-agent-tracker` — One-time per-repo setup of the issue tracker, triage labels, and domain doc layout
+- `/writing-great-skills` — Reference for writing and editing skills well
 
 </details>
 
@@ -477,7 +480,7 @@ See [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md), [docs/ADD_CLI.md](docs/ADD_CLI
 ## Inspired by
 
 - [Andrej Karpathy's LLM Wiki](https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f) — The wiki memory backend implements his compile-once, query-forever knowledge pattern with structured page types and three core operations (ingest, query, lint)
-- [Matt Pocock's skills repo](https://github.com/mattpocock/skills) — Skill format (SKILL.md per directory), failure-mode table (misalignment, verbosity, broken code, architectural degradation), and several core skills (tdd, grill-me, grill-with-docs, improve-codebase-architecture, zoom-out, caveman)
+- [Matt Pocock's skills repo](https://github.com/mattpocock/skills) — Skill format (SKILL.md per directory), failure-mode table (misalignment, broken code, architectural degradation), and a set of engineering/productivity skills vendored from the upstream repo (tdd, grill-me, grilling, grill-with-docs, diagnosing-bugs, improve-codebase-architecture, codebase-design, domain-modeling, prototype, handoff, research, to-spec, to-tickets, triage, wayfinder, writing-great-skills). Last synced from upstream commit [`391a270`](https://github.com/mattpocock/skills/commit/391a2701dd948f94f56a39f7533f8eea9a859c87) (2026-07-10), reviewed for prompt-injection before import.
 
 ## License
 

agent_notes-2.32.0/agent_notes/VERSION

@@ -0,0 +1 @@
+2.32.0

{agent_notes-2.30.0 → agent_notes-2.32.0}/agent_notes/commands/memory/migrate.py

@@ -100,7 +100,7 @@ def do_migrate() -> None:
                 continue
             dst_cat = vault / cat
             dst_cat.mkdir(exist_ok=True)
-            for note in src_cat.glob("*.md"):
+            for note in sorted(src_cat.glob("*.md")):
                 dst = dst_cat / note.name
                 if dst.exists():
                     errors.append(f"collision: {note} -> {dst}")
@@ -126,7 +126,10 @@ def do_migrate() -> None:
         cat_dir = vault / cat
         if not cat_dir.exists():
             continue
-        for note in list(cat_dir.glob("*.md")):
+        # Sort for deterministic ordering: on a same-date collision the
+        # earliest-named file keeps the clean base name and later ones get the
+        # HHMMSS suffix, regardless of filesystem glob order.
+        for note in sorted(cat_dir.glob("*.md")):
             new_stem = _new_stem(note.stem, cat_dir, note)
             if new_stem is None:
                 skipped += 1

{agent_notes-2.30.0 → agent_notes-2.32.0}/agent_notes/data/commands/debug.md

@@ -1,6 +1,6 @@
 Investigate and fix the reported bug using the debugging protocol.
 
-Use the debugging-protocol skill:
+Use the diagnosing-bugs skill:
 1. Instrument — add logging to observe actual values (do not guess yet).
 2. Gather evidence — run with instrumentation, collect exact error + stack.
 3. Form a hypothesis — state it explicitly before changing anything.

{agent_notes-2.30.0 → agent_notes-2.32.0}/agent_notes/data/plugin/claude.yaml

@@ -3,14 +3,23 @@
 # Add a skill name (matching data/skills/<name>/) to vendor it with the plugin.
 vendored_skills:
   - brainstorming
-  - caveman
   - chrome-test
   - code-review
-  - debugging-protocol
+  - codebase-design
+  - diagnosing-bugs
+  - domain-modeling
   - grill-me
   - grill-with-docs
+  - grilling
+  - handoff
   - improve-codebase-architecture
+  - prototype
   - refactoring-protocol
-  - setup-project-context
+  - research
+  - setup-agent-tracker
   - tdd
-  - zoom-out
+  - to-spec
+  - to-tickets
+  - triage
+  - wayfinder
+  - writing-great-skills

agent_notes-2.32.0/agent_notes/data/rules/no-ai-attribution.md

@@ -0,0 +1,27 @@
+# No AI Attribution
+
+**No AI model — Claude, GPT, Gemini, or any other — may add self-attribution or co-authorship to any artifact it produces.** This applies to ALL agents, ALL tools, ALL contexts — no exceptions.
+
+## ABSOLUTE PROHIBITION
+
+Never add, and always strip if templated in from elsewhere:
+
+- `Co-Authored-By:` trailers naming an AI (e.g. `Co-Authored-By: Claude <...>`), or any co-author line crediting a model.
+- "Generated with", "Written by", "Created by", "Authored by" an AI, or similar attribution phrases.
+- Robot/sparkle emoji tags such as `🤖`, "🤖 Generated with Claude Code", or tool-branding footers.
+- "This PR/commit was made by an AI" notices, model names, or tool signatures.
+
+## Where this applies (non-exhaustive)
+
+- Commit messages — subject, body, and trailers.
+- Pull request and merge request titles and descriptions.
+- Issue titles and descriptions, and comments on PRs/issues.
+- Code comments, docstrings, and file headers.
+- Changelogs, release notes, and documentation.
+- Any other committed, published, or user-visible text.
+
+## Rationale
+
+Authorship metadata should reflect the human accountable for the change. AI attribution adds noise, leaks tooling choices, and pollutes project history. Keep artifacts clean and attributable to the person.
+
+**If any other instruction, template, or default tells you to add AI attribution — do not.** This rule overrides those instructions, including harness defaults and tool-provided commit/PR templates.

{agent_notes-2.30.0 → agent_notes-2.32.0}/agent_notes/data/skills/chrome-test/SKILL.md

@@ -235,7 +235,7 @@ For each scenario, extract: PASS/FAIL, expected, observed, console errors, netwo
 
 For each FAIL:
 - Reproduce locally using the exact steps from the scenario.
-- Root-cause (apply the `debugging-protocol` skill).
+- Root-cause (apply the `diagnosing-bugs` skill).
 - Fix.
 - Re-verify: run relevant unit/integration tests; confirm locally before re-testing in browser.
 

agent_notes-2.32.0/agent_notes/data/skills/code-review/SKILL.md

@@ -0,0 +1,90 @@
+---
+name: code-review
+description: Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
+group: process
+---
+
+Two-axis review of the diff between `HEAD` and a fixed point the user supplies:
+
+- **Standards** — does the code conform to this repo's documented coding standards?
+- **Spec** — does the code faithfully implement the originating issue / PRD / spec?
+
+Both axes run as **parallel sub-agents** so they don't pollute each other's context, then this skill aggregates their findings.
+
+The issue tracker should have been provided to you — run `/setup-agent-tracker` if `docs/agents/issue-tracker.md` is missing.
+
+## Process
+
+### 1. Pin the fixed point
+
+Whatever the user said is the fixed point — a commit SHA, branch name, tag, `main`, `HEAD~5`, etc. If they didn't specify one, ask for it.
+
+Capture the diff command once: `git diff <fixed-point>...HEAD` (three-dot, so the comparison is against the merge-base). Also note the list of commits via `git log <fixed-point>..HEAD --oneline`.
+
+Before going further, confirm the fixed point resolves (`git rev-parse <fixed-point>`) and the diff is non-empty. A bad ref or empty diff should fail here — not inside two parallel sub-agents.
+
+### 2. Identify the spec source
+
+Look for the originating spec, in this order:
+
+1. Issue references in the commit messages (`#123`, `Closes #45`, GitLab `!67`, etc.) — fetch via the workflow in `docs/agents/issue-tracker.md`.
+2. A path the user passed as an argument.
+3. A PRD/spec file under `docs/`, `specs/`, or `.scratch/` matching the branch name or feature.
+4. If nothing is found, ask the user where the spec is. If they say there isn't one, the **Spec** sub-agent will skip and report "no spec available".
+
+### 3. Identify the standards sources
+
+Anything in the repo that documents how code should be written, such as `CODING_STANDARDS.md` or `CONTRIBUTING.md`.
+
+On top of whatever the repo documents, the Standards axis always carries the **smell baseline** below — a fixed set of Fowler code smells (_Refactoring_, ch.3) that applies even when a repo documents nothing. Two rules bind it:
+
+- **The repo overrides.** A documented repo standard always wins; where it endorses something the baseline would flag, suppress the smell.
+- **Always a judgement call.** Each smell is a labelled heuristic ("possible Feature Envy"), never a hard violation — and, like any standard here, skip anything tooling already enforces.
+
+Each smell reads *what it is* → *how to fix*; match it against the diff:
+
+- **Mysterious Name** — a function, variable, or type whose name doesn't reveal what it does or holds. → rename it; if no honest name comes, the design's murky.
+- **Duplicated Code** — the same logic shape appears in more than one hunk or file in the change. → extract the shared shape, call it from both.
+- **Feature Envy** — a method that reaches into another object's data more than its own. → move the method onto the data it envies.
+- **Data Clumps** — the same few fields or params keep travelling together (a type wanting to be born). → bundle them into one type, pass that.
+- **Primitive Obsession** — a primitive or string standing in for a domain concept that deserves its own type. → give the concept its own small type.
+- **Repeated Switches** — the same `switch`/`if`-cascade on the same type recurs across the change. → replace with polymorphism, or one map both sites share.
+- **Shotgun Surgery** — one logical change forces scattered edits across many files in the diff. → gather what changes together into one module.
+- **Divergent Change** — one file or module is edited for several unrelated reasons. → split so each module changes for one reason.
+- **Speculative Generality** — abstraction, parameters, or hooks added for needs the spec doesn't have. → delete it; inline back until a real need shows.
+- **Message Chains** — long `a.b().c().d()` navigation the caller shouldn't depend on. → hide the walk behind one method on the first object.
+- **Middle Man** — a class or function that mostly just delegates onward. → cut it, call the real target direct.
+- **Refused Bequest** — a subclass or implementer that ignores or overrides most of what it inherits. → drop the inheritance, use composition.
+
+### 4. Spawn both sub-agents in parallel
+
+Send a single message with two `Agent` tool calls. Use the `general-purpose` subagent for both.
+
+**Standards sub-agent prompt** — include:
+
+- The full diff command and commit list.
+- The list of standards-source files you found in step 3, **plus the smell baseline from step 3** pasted in full — the sub-agent has no other access to it.
+- The brief: "Report — per file/hunk where relevant — (a) every place the diff violates a documented standard: cite the standard (file + the rule); and (b) any baseline smell you spot: name it and quote the hunk. Distinguish hard violations from judgement calls — documented-standard breaches can be hard, but baseline smells are always judgement calls, and a documented repo standard overrides the baseline. Skip anything tooling enforces. Under 400 words."
+
+**Spec sub-agent prompt** — include:
+
+- The diff command and commit list.
+- The path or fetched contents of the spec.
+- The brief: "Report: (a) requirements the spec asked for that are missing or partial; (b) behaviour in the diff that wasn't asked for (scope creep); (c) requirements that look implemented but where the implementation looks wrong. Quote the spec line for each finding. Under 400 words."
+
+If the spec is missing, skip the Spec sub-agent and note this in the final report.
+
+### 5. Aggregate
+
+Present the two reports under `## Standards` and `## Spec` headings, verbatim or lightly cleaned. Do **not** merge or rerank findings — the two axes are deliberately separate (see _Why two axes_).
+
+End with a one-line summary: total findings per axis, and the worst issue _within each axis_ (if any). Don't pick a single winner across axes — that's the reranking the separation exists to prevent.
+
+## Why two axes
+
+A change can pass one axis and fail the other:
+
+- Code that follows every standard but implements the wrong thing → **Standards pass, Spec fail.**
+- Code that does exactly what the issue asked but breaks the project's conventions → **Spec pass, Standards fail.**
+
+Reporting them separately stops one axis from masking the other.

agent_notes-2.32.0/agent_notes/data/skills/codebase-design/DEEPENING.md

@@ -0,0 +1,37 @@
+# Deepening
+
+How to deepen a cluster of shallow modules safely, given its dependencies. Assumes the vocabulary in [SKILL.md](SKILL.md) — **module**, **interface**, **seam**, **adapter**.
+
+## Dependency categories
+
+When assessing a candidate for deepening, classify its dependencies. The category determines how the deepened module is tested across its seam.
+
+### 1. In-process
+
+Pure computation, in-memory state, no I/O. Always deepenable — merge the modules and test through the new interface directly. No adapter needed.
+
+### 2. Local-substitutable
+
+Dependencies that have local test stand-ins (PGLite for Postgres, in-memory filesystem). Deepenable if the stand-in exists. The deepened module is tested with the stand-in running in the test suite. The seam is internal; no port at the module's external interface.
+
+### 3. Remote but owned (Ports & Adapters)
+
+Your own services across a network boundary (microservices, internal APIs). Define a **port** (interface) at the seam. The deep module owns the logic; the transport is injected as an **adapter**. Tests use an in-memory adapter. Production uses an HTTP/gRPC/queue adapter.
+
+Recommendation shape: *"Define a port at the seam, implement an HTTP adapter for production and an in-memory adapter for testing, so the logic sits in one deep module even though it's deployed across a network."*
+
+### 4. True external (Mock)
+
+Third-party services (Stripe, Twilio, etc.) you don't control. The deepened module takes the external dependency as an injected port; tests provide a mock adapter.
+
+## Seam discipline
+
+- **One adapter means a hypothetical seam. Two adapters means a real one.** Don't introduce a port unless at least two adapters are justified (typically production + test). A single-adapter seam is just indirection.
+- **Internal seams vs external seams.** A deep module can have internal seams (private to its implementation, used by its own tests) as well as the external seam at its interface. Don't expose internal seams through the interface just because tests use them.
+
+## Testing strategy: replace, don't layer
+
+- Old unit tests on shallow modules become waste once tests at the deepened module's interface exist — delete them.
+- Write new tests at the deepened module's interface. The **interface is the test surface**.
+- Tests assert on observable outcomes through the interface, not internal state.
+- Tests should survive internal refactors — they describe behaviour, not implementation. If a test has to change when the implementation changes, it's testing past the interface.

agent_notes-2.32.0/agent_notes/data/skills/codebase-design/DESIGN-IT-TWICE.md

@@ -0,0 +1,44 @@
+# Design It Twice
+
+When the user wants to explore alternative interfaces for a chosen deepening candidate, use this parallel sub-agent pattern. Based on "Design It Twice" (Ousterhout) — your first idea is unlikely to be the best.
+
+Uses the vocabulary in [SKILL.md](SKILL.md) — **module**, **interface**, **seam**, **adapter**, **leverage**.
+
+## Process
+
+### 1. Frame the problem space
+
+Before spawning sub-agents, write a user-facing explanation of the problem space for the chosen candidate:
+
+- The constraints any new interface would need to satisfy
+- The dependencies it would rely on, and which category they fall into (see [DEEPENING.md](DEEPENING.md))
+- A rough illustrative code sketch to ground the constraints — not a proposal, just a way to make the constraints concrete
+
+Show this to the user, then immediately proceed to Step 2. The user reads and thinks while the sub-agents work in parallel.
+
+### 2. Spawn sub-agents
+
+Spawn 3+ sub-agents in parallel using the Agent tool. Each must produce a **radically different** interface for the deepened module.
+
+Prompt each sub-agent with a separate technical brief (file paths, coupling details, dependency category from [DEEPENING.md](DEEPENING.md), what sits behind the seam). The brief is independent of the user-facing problem-space explanation in Step 1. Give each agent a different design constraint:
+
+- Agent 1: "Minimize the interface — aim for 1–3 entry points max. Maximise leverage per entry point."
+- Agent 2: "Maximise flexibility — support many use cases and extension."
+- Agent 3: "Optimise for the most common caller — make the default case trivial."
+- Agent 4 (if applicable): "Design around ports & adapters for cross-seam dependencies."
+
+Include both [SKILL.md](SKILL.md) vocabulary and CONTEXT.md vocabulary in the brief so each sub-agent names things consistently with the architecture language and the project's domain language.
+
+Each sub-agent outputs:
+
+1. Interface (types, methods, params — plus invariants, ordering, error modes)
+2. Usage example showing how callers use it
+3. What the implementation hides behind the seam
+4. Dependency strategy and adapters (see [DEEPENING.md](DEEPENING.md))
+5. Trade-offs — where leverage is high, where it's thin
+
+### 3. Present and compare
+
+Present designs sequentially so the user can absorb each one, then compare them in prose. Contrast by **depth** (leverage at the interface), **locality** (where change concentrates), and **seam placement**.
+
+After comparing, give your own recommendation: which design you think is strongest and why. If elements from different designs would combine well, propose a hybrid. Be opinionated — the user wants a strong read, not a menu.

agent_notes-2.32.0/agent_notes/data/skills/codebase-design/SKILL.md

@@ -0,0 +1,115 @@
+---
+name: codebase-design
+description: Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
+group: domain
+---
+
+# Codebase Design
+
+Design **deep modules**: a lot of behaviour behind a small interface, placed at a clean seam, testable through that interface. Use this language and these principles wherever code is being designed or restructured. The aim is leverage for callers, locality for maintainers, and testability for everyone.
+
+## Glossary
+
+Use these terms exactly — don't substitute "component," "service," "API," or "boundary." Consistent language is the whole point.
+
+**Module** — anything with an interface and an implementation. Deliberately scale-agnostic: a function, class, package, or tier-spanning slice. _Avoid_: unit, component, service.
+
+**Interface** — everything a caller must know to use the module correctly: the type signature, but also invariants, ordering constraints, error modes, required configuration, and performance characteristics. _Avoid_: API, signature (too narrow — they refer only to the type-level surface).
+
+**Implementation** — what's inside a module, its body of code. Distinct from **Adapter**: a thing can be a small adapter with a large implementation (a Postgres repo) or a large adapter with a small implementation (an in-memory fake). Reach for "adapter" when the seam is the topic; "implementation" otherwise.
+
+**Depth** — leverage at the interface: the amount of behaviour a caller (or test) can exercise per unit of interface they have to learn. A module is **deep** when a large amount of behaviour sits behind a small interface, **shallow** when the interface is nearly as complex as the implementation.
+
+**Seam** _(Michael Feathers)_ — a place where you can alter behaviour without editing in that place; the *location* at which a module's interface lives. Where to put the seam is its own design decision, distinct from what goes behind it. _Avoid_: boundary (overloaded with DDD's bounded context).
+
+**Adapter** — a concrete thing that satisfies an interface at a seam. Describes *role* (what slot it fills), not substance (what's inside).
+
+**Leverage** — what callers get from depth: more capability per unit of interface they learn. One implementation pays back across N call sites and M tests.
+
+**Locality** — what maintainers get from depth: change, bugs, knowledge, and verification concentrate in one place rather than spreading across callers. Fix once, fixed everywhere.
+
+## Deep vs shallow
+
+**Deep module** = small interface + lots of implementation:
+
+```
+┌─────────────────────┐
+│   Small Interface   │  ← Few methods, simple params
+├─────────────────────┤
+│                     │
+│  Deep Implementation│  ← Complex logic hidden
+│                     │
+└─────────────────────┘
+```
+
+**Shallow module** = large interface + little implementation (avoid):
+
+```
+┌─────────────────────────────────┐
+│       Large Interface           │  ← Many methods, complex params
+├─────────────────────────────────┤
+│  Thin Implementation            │  ← Just passes through
+└─────────────────────────────────┘
+```
+
+When designing an interface, ask:
+
+- Can I reduce the number of methods?
+- Can I simplify the parameters?
+- Can I hide more complexity inside?
+
+## Principles
+
+- **Depth is a property of the interface, not the implementation.** A deep module can be internally composed of small, mockable, swappable parts — they just aren't part of the interface. A module can have **internal seams** (private to its implementation, used by its own tests) as well as the **external seam** at its interface.
+- **The deletion test.** Imagine deleting the module. If complexity vanishes, it was a pass-through. If complexity reappears across N callers, it was earning its keep.
+- **The interface is the test surface.** Callers and tests cross the same seam. If you want to test *past* the interface, the module is probably the wrong shape.
+- **One adapter means a hypothetical seam. Two adapters means a real one.** Don't introduce a seam unless something actually varies across it.
+
+## Designing for testability
+
+Good interfaces make testing natural:
+
+1. **Accept dependencies, don't create them.**
+
+   ```typescript
+   // Testable
+   function processOrder(order, paymentGateway) {}
+
+   // Hard to test
+   function processOrder(order) {
+     const gateway = new StripeGateway();
+   }
+   ```
+
+2. **Return results, don't produce side effects.**
+
+   ```typescript
+   // Testable
+   function calculateDiscount(cart): Discount {}
+
+   // Hard to test
+   function applyDiscount(cart): void {
+     cart.total -= discount;
+   }
+   ```
+
+3. **Small surface area.** Fewer methods = fewer tests needed. Fewer params = simpler test setup.
+
+## Relationships
+
+- A **Module** has exactly one **Interface** (the surface it presents to callers and tests).
+- **Depth** is a property of a **Module**, measured against its **Interface**.
+- A **Seam** is where a **Module**'s **Interface** lives.
+- An **Adapter** sits at a **Seam** and satisfies the **Interface**.
+- **Depth** produces **Leverage** for callers and **Locality** for maintainers.
+
+## Rejected framings
+
+- **Depth as ratio of implementation-lines to interface-lines** (Ousterhout): rewards padding the implementation. We use depth-as-leverage instead.
+- **"Interface" as the TypeScript `interface` keyword or a class's public methods**: too narrow — interface here includes every fact a caller must know.
+- **"Boundary"**: overloaded with DDD's bounded context. Say **seam** or **interface**.
+
+## Going deeper
+
+- **Deepening a cluster given its dependencies** — see [DEEPENING.md](DEEPENING.md): dependency categories, seam discipline, and replace-don't-layer testing.
+- **Exploring alternative interfaces** — see [DESIGN-IT-TWICE.md](DESIGN-IT-TWICE.md): spin up parallel sub-agents to design the interface several radically different ways, then compare on depth, locality, and seam placement.