claude-dev-env 1.93.1 → 1.95.0

package/skills/refine/templates/plan-template.md

@@ -1,60 +0,0 @@
----
-type: plan
-project: <project-or-topic-area>
-date: <YYYY-MM-DD>
-status: Draft
-tags: [refine, plan]
----
-
-# <Plan title>
-
-One-paragraph framing of what the plan delivers and why now.
-
-## Goal
-
-What completing this plan produces. Stated as an outcome, not an activity.
-
-## Non-goals
-
-What is intentionally out of scope. Each item is a thing a reader might assume is included.
-
-- <Non-goal one>
-- <Non-goal two>
-
-## Current state
-
-What exists today that this plan builds on or changes. Cite files, hooks, skills, decisions found during the fan-out. Each bullet is one concrete claim with a path or reference.
-
-- `<path/to/file>` — <what it currently does that matters>
-- `<vault note path>` — <decision or prior session this plan inherits from>
-
-## Implementation
-
-Ordered steps. Each step states the file or surface it touches and the concrete change. Subagents to spawn are named with their `subagent_type`.
-
-1. **<Step title>** — <file path or surface>. <Concrete change>.
-2. **<Step title>** — <file path or surface>. <Concrete change>.
-3. **<Step title>** — <file path or surface>. <Concrete change>.
-
-## Decisions log
-
-Each meaningful choice the interview surfaced, with the reasoning. Future-you reads this to understand why the plan looks the way it does.
-
-| Decision | Choice | Reasoning |
-|---|---|---|
-| <Question the interview answered> | <What was chosen> | <Why this over the alternatives> |
-| <Question the interview answered> | <What was chosen> | <Why this over the alternatives> |
-
-## Risks / open questions
-
-What could break this plan, and what is still unresolved. Each item is actionable — either has a mitigation or is flagged for the user to resolve before implementation begins.
-
-- **<Risk one>** — <Mitigation, or "open: needs decision before step N">
-- **<Risk two>** — <Mitigation, or "open: needs decision before step N">
-
-## Acceptance
-
-What "done" looks like. Observable behavior, file existence, command output — concrete and verifiable.
-
-- [ ] <Verifiable outcome one>
-- [ ] <Verifiable outcome two>

package/skills/research-mode/CLAUDE.md

@@ -1,35 +0,0 @@
-# research-mode
-
-Activates three anti-hallucination constraints: cite every claim, say "I don't know" when evidence is lacking, and quote directly from source documents.
-
-**Trigger:** "research mode", "toggle research", `/research-mode`.
-
-## Purpose
-
-Enforces factual accuracy for research tasks by requiring citations and explicit uncertainty. Stays active until the user exits with "exit research mode".
-
-## Key files
-
-| File | Purpose |
-|---|---|
-| `SKILL.md` | The complete skill — three constraints, source authority hierarchy, exit condition. No companion files. |
-
-## Three active constraints (all simultaneous)
-
-1. **Say "I don't know"** when no credible source backs a claim.
-2. **Verify with citations** — every recommendation cites a specific source (project file, URL, named expert, or official docs).
-3. **Direct quotes for factual grounding** — extract actual text before analyzing; ground in word-for-word quotes.
-
-## Source authority hierarchy
-
-1. Official vendor/creator documentation
-2. Files in the current project
-3. Academic papers, named researchers
-4. Reputable external sources with URLs
-5. Blog posts and community content (lowest; never cited alone when official docs exist)
-
-## Conventions
-
-- This mode is not the default; it applies only after the trigger fires.
-- Creative thinking and brainstorming are out of scope for this mode.
-- The global `~/.claude/rules/research-mode.md` carries the same three constraints as always-on background rules; this skill makes them explicit and surfaced during the session.

package/skills/research-mode/SKILL.md

@@ -1,53 +0,0 @@
----
-name: research-mode
-description: "Enforces anti-hallucination constraints by requiring citations, source grounding, and explicit 'I don't know' responses when evidence is lacking. Activates for research tasks where factual accuracy is critical. Triggers: 'research mode', 'toggle research', '/research-mode'."
----
-
-# Research Mode
-
-Activates three anti-hallucination constraints based on Anthropic's documentation. Stay in this mode until the user says to exit.
-
-Source: [Anthropic - Reduce Hallucinations](https://docs.anthropic.com/en/docs/test-and-evaluate/strengthen-guardrails/reduce-hallucinations)
-
-## Constraints (ALL active simultaneously)
-
-### 1. Say "I don't know"
-If you don't have a credible source for a claim, say so. Don't guess. Don't infer. "I don't have data on this" is always a valid answer.
-
-### 2. Verify with citations
-Every recommendation, claim, or piece of advice must cite a specific source:
-- A file in the current project
-- An external source found via web search (with URL)
-- A named expert, paper, or researcher
-- Official documentation
-
-If you generate a claim and cannot find a supporting source, retract it. Do not present it.
-
-### 3. Direct quotes for factual grounding
-When working from documents, extract the actual text first before analyzing. Ground your response in word-for-word quotes, not paraphrased summaries. Reference the quote when making your point.
-
-## Source Authority Hierarchy
-
-When evaluating sources, follow this priority order. Higher-tier sources take precedence when claims conflict.
-
-1. **Official vendor/creator documentation** — the authoritative source for any external tool, library, API, or protocol. Always check for this first.
-2. **Files in the current project** — for local code, the codebase is the source of truth.
-3. **Academic papers, named researchers** — peer-reviewed or attributed expert analysis.
-4. **Reputable external sources with URLs** — established publications, conference talks, verified technical content.
-5. **Blog posts, tutorials, community content** — useful for context but lowest authority. Never cite these alone when official docs exist.
-
-### When official docs don't exist
-
-If researching an external tool, library, or API and no official vendor/creator documentation can be found, state this explicitly. Do not silently fall back to secondary sources — the absence of official docs is itself a finding the user needs to know.
-
-### Local code exception
-
-For local project code — custom themes, workflows, databases, internal tools — the codebase itself is the authority. Official documentation applies only to the external tools and libraries the project uses, not to the project's own custom logic.
-
-## What this mode is NOT
-- It is NOT the default. Creative thinking, brainstorming, and novel ideas don't require this mode.
-- It does NOT mean "be slow." Research efficiently. Use tools in parallel.
-- It does NOT mean "only use existing ideas." You can synthesize across sources to reach new conclusions, but the inputs must be grounded.
-
-## How to exit
-Say "exit research mode" or switch to any other task.

package/skills/structure-prompt/CLAUDE.md

@@ -1,42 +0,0 @@
-# structure-prompt
-
-Restructures a prompt in one pass: orders blocks, converts persona framing to task constraints, enforces per-category dispositions, expands placeholder tokens, adds `file:line` citations, marks the canonical sub-bucket, and sharpens adversarial-pass phrasing.
-
-**Trigger:** `/structure-prompt`, "optimize this prompt", "minimally invasive edit" to a prompt artifact, "tighten this prompt".
-
-## Purpose
-
-Applies a spoke-based ruleset to a prompt artifact. Each spoke targets a specific structural problem (persona framing, narrative directives, missing citations, etc.). One pass per invocation.
-
-## Key files
-
-| File | Purpose |
-|---|---|
-| `SKILL.md` | Hub — pre-flight, first-invocation reads, spoke routing table |
-| `reference/block-classification.md` | How to classify each block in the input prompt |
-| `reference/research.md` | When a spoke needs information not in the input |
-| `reference/output-contract.md` | How to emit the rewritten prompt |
-| `reference/structure.md` | Re-ordering blocks and handling large content regions |
-| `reference/persona.md` | Converting role assignments to task constraints |
-| `reference/per-category.md` | Enforcing per-category dispositions |
-| `reference/directives.md` | Rewriting performance directives |
-| `reference/constraints.md` | Rewriting narrative directives |
-| `reference/instantiation.md` | Expanding placeholder tokens |
-| `reference/citation-depth.md` | Adding `file:line` citations |
-| `reference/canonical-case.md` | Marking the canonical sub-bucket with ⭐ |
-| `reference/adversarial-tuning.md` | Sharpening adversarial-pass phrasing |
-| `reference/cleanup.md` | Fixing typos, mixed bullet styles, untagged code blocks |
-| `reference/examples.md` | Spoke-matched examples for situations not covered above |
-
-## Subdirectories
-
-| Directory | Purpose |
-|---|---|
-| `reference/` | One file per spoke; loaded on demand based on the routing table in `SKILL.md` |
-
-## Conventions
-
-- On first invocation, read `block-classification.md`, `research.md`, and `output-contract.md` before anything else.
-- The input arrives as the user's message body, a fenced block within it, or a file path argument.
-- Emit the result as a single fenced block (paste mode) or rewrite the file in place (file-path mode).
-- Load only the reference files the input situation matches — not all of them.

package/skills/structure-prompt/SKILL.md

@@ -1,44 +0,0 @@
----
-name: structure-prompt
-description: >-
-  Restructures a user-provided prompt: orders blocks, swaps persona framing for
-  task constraints, expands placeholder tokens, and adds file:line citations.
-  Triggers: /structure-prompt, 'optimize this prompt', 'minimally invasive edit'
-  to a prompt artifact, or 'tighten this prompt'.
----
-
-# structure-prompt
-
-One pass per invocation. Classify each block of the input prompt, apply the matching spoke rules, and emit the rewritten prompt as a single fenced block (paste mode) or rewrite the file in place (file-path mode).
-
-## Pre-flight
-
-The input prompt arrives as the user's message body, as a fenced block within it, or as a file path argument. Treat the entire input as the artifact under optimization.
-
-## First invocation of a session
-
-Read [`reference/block-classification.md`](reference/block-classification.md), then [`reference/research.md`](reference/research.md), then [`reference/output-contract.md`](reference/output-contract.md).
-
-## Match situation, read spoke
-
-| Situation | Read |
-|---|---|
-| Starting any optimization | [`reference/block-classification.md`](reference/block-classification.md) |
-| A spoke needs information that isn't in the input | [`reference/research.md`](reference/research.md) |
-| Input contains a fenced code block, diff, dump, transcript, or single content region ≥ 500 characters, OR blocks appear out of canonical sequence (mission, metadata, framework, questions, output spec, data body) | [`reference/structure.md`](reference/structure.md) |
-| Input opens with a role assignment ("You are…", "Act as…", "Imagine you are…", "As a…", "Pretend to be…", "Role:…") | [`reference/persona.md`](reference/persona.md) |
-| Input names 2+ categories, surfaces, sub-buckets, items, checks, or criteria the agent processes | [`reference/per-category.md`](reference/per-category.md) |
-| Input contains performance directives ("be thorough", "think step by step", "you are an expert", "please", "kindly") | [`reference/directives.md`](reference/directives.md) |
-| Input contains narrative directives ("try to", "look at", "make sure", "consider", "be sure to", "think about") | [`reference/constraints.md`](reference/constraints.md) |
-| Input contains placeholder tokens (`[REPO/ARTIFACT]`, `[INLINE THE FULL ARTIFACT HERE]`, `[N]`, etc.) | [`reference/instantiation.md`](reference/instantiation.md) |
-| Sub-bucket bullets reference identifiers from the data body without `file:line` citations | [`reference/citation-depth.md`](reference/citation-depth.md) |
-| Framework has 5+ sub-buckets and no ⭐ canonical-case marker | [`reference/canonical-case.md`](reference/canonical-case.md) |
-| Output spec contains generic adversarial-pass phrasing ("missed at least N bugs/findings") | [`reference/adversarial-tuning.md`](reference/adversarial-tuning.md) |
-| Input has typos, mixed bullet styles, untagged code blocks, trailing whitespace, blank-line runs, or non-sequential heading levels | [`reference/cleanup.md`](reference/cleanup.md) |
-| Situation doesn't match any spoke above | [`reference/examples.md`](reference/examples.md) |
-| Emitting the rewritten prompt | [`reference/output-contract.md`](reference/output-contract.md) |
-
-## Folder map
-
-- `SKILL.md` — this hub.
-- `reference/` — rule detail per situation.

package/skills/structure-prompt/reference/CLAUDE.md

@@ -1,28 +0,0 @@
-# structure-prompt/reference
-
-One reference file per optimization spoke, loaded on demand by the routing table in `SKILL.md`.
-
-## Key files
-
-| File | Purpose |
-|---|---|
-| `block-classification.md` | How to classify each block in the input prompt (mission, metadata, framework, questions, output spec, data body). Read on every invocation. |
-| `research.md` | Steps to take when a spoke needs information not in the input. Read on every invocation. |
-| `output-contract.md` | How to emit the rewritten prompt (fenced paste mode or in-place file rewrite). Read on every invocation. |
-| `structure.md` | Re-ordering blocks and handling large content regions (≥500 chars, fenced code, diffs, transcripts). |
-| `persona.md` | Converting role assignments ("You are…", "Act as…") to task constraints. |
-| `per-category.md` | Enforcing per-category dispositions when the prompt names 2+ categories or criteria. |
-| `directives.md` | Rewriting performance directives ("be thorough", "think step by step"). |
-| `constraints.md` | Rewriting narrative directives ("try to", "make sure", "consider"). |
-| `instantiation.md` | Expanding placeholder tokens (`[REPO/ARTIFACT]`, `[N]`, etc.). |
-| `citation-depth.md` | Adding `file:line` citations to sub-bucket bullets that reference identifiers. |
-| `canonical-case.md` | Marking the ⭐ canonical sub-bucket when a framework has 5+ sub-buckets and none is marked. |
-| `adversarial-tuning.md` | Sharpening generic adversarial-pass phrasing. |
-| `cleanup.md` | Fixing typos, mixed bullet styles, untagged code blocks, trailing whitespace. |
-| `examples.md` | Spoke-matched examples for situations not covered by the named spokes above. |
-
-## Conventions
-
-- Read `block-classification.md`, `research.md`, and `output-contract.md` on every first invocation of a session.
-- For all other files: load only the one(s) that match the input situation — the `SKILL.md` routing table maps each situation to its spoke file.
-- Never load the full set; spoke files are designed for on-demand use to keep context lean.

package/skills/structure-prompt/reference/adversarial-tuning.md

@@ -1,62 +0,0 @@
-# Sharpen the adversarial-pass phrasing
-
-The output spec usually closes with an adversarial second-pass instruction like *assume your first pass missed at least 3 P1 bugs across these N sub-buckets — find them*. When that phrase uses a generic noun (`bugs`, `findings`, `issues`, `problems`), the skill replaces the noun with one that names the category's specific failure mode.
-
-## Detection
-
-The fix fires when the output spec contains a phrase matching this shape, with a generic noun:
-
-- "missed at least `<number>` [bugs / findings / issues / problems]" — optionally preceded by a severity tier (`P0` or `P1`) when the framework uses tiered findings.
-
-A noun is "generic" when it could apply to any audit category. A noun is "specific" when it names the failure mode of the category.
-
-## How to derive the specific noun
-
-Read the mission line and the framework header. Pull the category's domain from there. Match against this lookup:
-
-| Category domain | Specific failure-mode noun |
-|---|---|
-| API contracts (signatures, return types, callback shape) | contract drifts |
-| Selector / query / engine compatibility | engine-version incompatibilities |
-| Resource cleanup (handles, locks, subscriptions) | leaked resources |
-| Scoping and ordering | scope or ordering bugs |
-| Dead code | dead code paths |
-| Silent failures (swallowed exceptions, dropped errors) | silent failures |
-| Bounds and overflow | bounds or overflow bugs |
-| Security boundaries | trust-boundary violations |
-| Concurrency | concurrency hazards |
-| Code rules compliance | rule violations |
-| Codebase conflicts (incomplete propagation) | parallel sites that should have been updated alongside the diff |
-
-When the category sits outside this list, derive the noun from the framework's most prominent axis name (e.g., a framework whose axes all name "selectors" → "selector incompatibilities").
-
-## Procedure
-
-1. Find the adversarial-pass sentence in the output spec.
-2. Identify the generic noun in that sentence.
-3. Replace it with the specific noun from the table or framework.
-4. Keep the rest of the sentence intact: count (e.g., "3"), severity tier (e.g., "P1") when the original phrase carries one, and the closing "find them".
-
-## Examples
-
-Before (generic):
-> "assume your first pass missed at least 3 P1 bugs across these 7 sub-buckets — find them"
-
-After (Category B):
-> "assume your first pass missed at least 3 P1 engine-version incompatibilities across these 7 sub-buckets — find them"
-
-After (Category K):
-> "assume your first pass missed at least 3 P1 parallel sites that should have been updated alongside the diff across these 7 sub-buckets — find them"
-
-After (Category C):
-> "assume your first pass missed at least 3 P1 leaked resources across these 7 sub-buckets — find them"
-
-## What stays put
-
-When the adversarial phrase already names a specific failure mode, the noun stays. The skill changes only generic nouns.
-
-The count (e.g., 3) and severity tier (e.g., P1) stay intact when the original phrase carries them. Some categories name a noun that doesn't fit the P-tier model — Codebase Conflicts ("parallel sites that should have been updated alongside the diff") is the canonical example — but preservation still applies: if the original phrase includes a tier, the rewritten phrase includes it too. The rule is preservation, not insertion or removal.
-
-## Disposition reporting
-
-Every outcome emits an action note via the mechanism that [`output-contract.md`](output-contract.md) defines. When the noun was replaced: `> Gap: Adversarial-pass noun sharpened — "bugs" → "<specific noun>".` When the phrase already carries a specific noun: `> Gap: Adversarial-pass noun verified — "<specific noun>" already specific.` Silent pass is forbidden — see the [no silent action](output-contract.md#disposition-invariants) invariant.

package/skills/structure-prompt/reference/block-classification.md

@@ -1,27 +0,0 @@
-# Block classification
-
-Every input prompt decomposes into six block types. Tag each region of the input as exactly one type before applying any spoke rules.
-
-## Block types
-
-**Mission block.** One sentence stating what the agent does. The opening directive of the prompt.
-
-**Metadata block.** Identifiers, SHAs, PR numbers, target paths, ID prefixes, scope flags, mode toggles. Short atomic facts the agent uses as parameters.
-
-**Framework block.** The checklist, sub-bucket list, surface list, category list, or step list the agent processes. Multi-item structures with named entries.
-
-**Questions block.** Cross-cutting questions, synthesis questions, or open questions the agent answers after completing the framework.
-
-**Output spec block.** The format the agent's output takes — totals header, per-item shape, ordering, severity tags, locator format, length cap, lead phrase, closing phrase.
-
-**Data body block.** Any of:
-- Fenced code block (triple backtick) that sits INSIDE the prompt content — not the outer paste-mode fence that wraps the entire prompt artifact
-- Diff, file dump, transcript, log, table, or document inlined as content
-- Any single content region of 500 characters or more that the agent inspects rather than acts on
-
-## Tagging procedure
-
-1. Read the input prompt top to bottom.
-2. Annotate each region with exactly one tag.
-3. Confirm every content region is either tagged with one of the six block types or part of a gap-report block. Gap-note lines (`> Gap:`) and `<!-- gap-report:` comment blocks from a prior invocation form a passthrough region — preserved in place during classification and reordering, not re-tagged. During emission, the gap-report region is deterministically replaced by the current run's gap notes per [`output-contract.md`](output-contract.md). The gap-report region sits at the end of the prompt and carries no classification tag.
-4. Proceed to the matching spoke.

package/skills/structure-prompt/reference/canonical-case.md

@@ -1,48 +0,0 @@
-# Mark the canonical sub-bucket with ⭐
-
-When a framework has many sub-buckets, one of them usually carries the category's signature failure mode. Marking that sub-bucket with ⭐ helps the auditing agent give it extra attention.
-
-## Detection
-
-The marker fires when BOTH hold:
-
-- The framework has 5 or more sub-buckets
-- No sub-bucket already carries the ⭐ marker
-
-The third condition — whether a canonical signal exists — is determined during selection (below), not detection. When selection finds no clear canonical case, the marker pass does not mark and instead emits a gap note per the [no silent action](output-contract.md#disposition-invariants) invariant.
-
-## How to pick the canonical sub-bucket
-
-In order:
-
-1. **Rubric match.** When the calling framework provides a sibling rubric (e.g., at `../category_rubrics/<name>.md` in audit-rubric layouts) and that rubric describes a "Canonical example" or names one axis as the signature pattern, pick that sub-bucket. When no sibling rubric exists, skip this step and fall through to bullet density.
-2. **Bullet density.** When the rubric stays silent, count the concrete bullets per sub-bucket. The sub-bucket with the most bullets that cite a real identifier or line number wins.
-3. **Identifier density.** When two sub-buckets tie on bullet count, pick the one whose identifiers appear most often in the data body.
-
-## How to mark it
-
-Append `⭐ canonical <category-letter> case` after the sub-bucket title, on the same line.
-
-Derive `<category-letter>` from the leading letter of the sub-bucket id (`K3` → `K`, `A2` → `A`, `B1` → `B`). When the framework uses non-lettered sub-bucket ids or no ids at all (e.g., bullets titled `Surface 1`, `Item 1`, `Check 1`), drop the letter and write `⭐ canonical case`.
-
-Example before:
-```
-**K3. Primary path vs fallback path**
-- The file's `if resolved_skill_path is not None:` branch (line 121) is the PRIMARY path…
-```
-
-Example after:
-```
-**K3. Primary path vs fallback path** ⭐ canonical K case
-- The file's `if resolved_skill_path is not None:` branch (line 121) is the PRIMARY path…
-```
-
-## What stays put
-
-When a ⭐ marker already lives somewhere in the framework, the marker pass leaves it alone — the prompt's author already chose. The skill marks at most one sub-bucket per invocation.
-
-When research turns up no clear canonical case (the bullets are evenly weighted, no rubric guidance, no identifier-density signal), the marker pass leaves the framework unmarked AND MUST emit a gap note via the paste-mode or file-path-mode gap-report mechanism that [`output-contract.md`](output-contract.md) defines for the active emission mode. The framework reads fine without an arbitrary pick, but the deferral itself is recorded — see the [no silent action](output-contract.md#disposition-invariants) invariant.
-
-## Disposition reporting
-
-Every outcome emits an action note via the mechanism that [`output-contract.md`](output-contract.md) defines. When a sub-bucket was marked: `> Gap: ⭐ canonical <letter> case marker added to sub-bucket "<sub-bucket-id>".` When the framework has fewer than 5 sub-buckets or already carries a ⭐ marker: `> Gap: Canonical-case marker verified — <reason>.` When no clear canonical case exists: `> Gap: Canonical-case marker skipped — framework has 5+ sub-buckets but <rubric match / bullet density / identifier density> found no clear canonical case.` Silent pass is forbidden — see the [no silent action](output-contract.md#disposition-invariants) invariant.

package/skills/structure-prompt/reference/citation-depth.md

@@ -1,70 +0,0 @@
-# Add file:line citations on identifier mentions
-
-When a sub-bucket bullet names an identifier (a function, variable, cmdlet, file path) that also lives in the data body, the bullet earns more value with a `file:line` citation appended.
-
-## Detection
-
-Two separate paths, evaluated for every backtick-wrapped identifier in each bullet:
-
-**Citation-candidate path.** An identifier is a citation candidate when all three hold:
-- The bullet contains a backtick-wrapped identifier (e.g., `os.walk`, `New-ScheduledTaskTrigger`, `_log_walk_error`)
-- The identifier also appears in the data body
-- No `file:line` citation already follows that identifier within the bullet
-
-**Citation-unavailable path.** An identifier triggers the unavailable path when all three hold:
-- The bullet contains a backtick-wrapped identifier
-- The identifier does NOT appear in the data body — its file is not included in the diff or the identifier is external (e.g., a stdlib symbol, a framework API)
-- No `(citation unavailable: <reason>)` marker already follows that identifier within the bullet
-
-Both paths fire independently per identifier. A bullet can contain both citable and unciteable identifiers.
-
-## Procedure
-
-**For citation candidates:**
-1. For each citation candidate, search the data body for the identifier.
-2. Find every occurrence of the identifier in the data body. When the data body uses explicit line numbers (e.g., a code block prefixed with file:line annotations or a diff), use those. When the data body has no line numbers (e.g., a raw pasted dump), use the 1-based line index within the data-body block as `<line>`. Apply the multiple-occurrence policy below to determine which lines to cite.
-3. Append the citation in this format immediately after the backtick-wrapped identifier: `` `identifier` (`<file>:<line>`)``. When the bullet contains multiple identifiers, cite each one inline after its owning backtick span. The `<file>` value comes from the data-body block's heading or label (e.g., the filename in a `### file.py` heading, the diff header, or the code block's language tag). When the data body has no file identity at all (a raw paste with no heading or label), use `data-body:<line>`. The examples below illustrate both single-identifier and multi-identifier bullets.
-
-## Multiple occurrences
-
-When the identifier appears one or more times across the data body:
-
-- 1–3 occurrences → cite all of them: `(file_a.py:42, file_a.py:88, file_b.ps1:12)`
-- 4 or more → cite the first and last with `…` between: `(file_a.py:42, …, file_b.ps1:200)`
-
-## Examples
-
-Before:
-```
-- uses `os.walk` with `_log_walk_error` — `_log_walk_error` matches the exact signature stdlib calls.
-```
-
-After (2 occurrences: definition plus one call site):
-```
-- uses `os.walk` (`sweep_empty_dirs.py:23`) with `_log_walk_error` (`sweep_empty_dirs.py:23, sweep_empty_dirs.py:33`) — `_log_walk_error` matches the exact signature stdlib calls.
-```
-
-Before:
-```
-- `Get-ScheduledTask`, `New-ScheduledTaskTrigger`, `New-ScheduledTaskAction`, `Register-ScheduledTask`, `Unregister-ScheduledTask` — verify each call's parameter shape.
-```
-
-After (one occurrence per cmdlet):
-```
-- `Get-ScheduledTask` (`Install-SweepEmptyDirs.ps1:248`), `New-ScheduledTaskTrigger` (`Install-SweepEmptyDirs.ps1:297`), `New-ScheduledTaskAction` (`Install-SweepEmptyDirs.ps1:296`), `Register-ScheduledTask` (`Install-SweepEmptyDirs.ps1:300`), `Unregister-ScheduledTask` (`Install-SweepEmptyDirs.ps1:267`) — verify each call's parameter shape.
-```
-
-## What stays put
-
-When the identifier is a generic concept (e.g., `if version`, `if FLAG`) rather than a real symbol in the data body, the bullet stays as-written. Citations apply to actual identifiers, not category-shaped placeholders.
-
-When the identifier sits in a file the data body doesn't include (e.g., the bullet mentions `os.walk` but the diff doesn't define it), the citation skips that identifier. The skipped citation MUST emit BOTH:
-
-1. An inline gap marker adjacent to the identifier: `(citation unavailable: <reason>)` — so the bullet is not visually identical to a successful citation when read in isolation.
-2. A gap note via the paste-mode or file-path-mode gap-report mechanism that [`output-contract.md`](output-contract.md) defines for the active emission mode.
-
-Both records are required by the [no silent action](output-contract.md#disposition-invariants) invariant: the reader of the bullet alone must see the gap, and the reader of the output as a whole must see the gap.
-
-## Disposition reporting
-
-Every outcome emits an action note via the mechanism that [`output-contract.md`](output-contract.md) defines. When citations were added: `> Gap: Citations added — <N> identifier(s) cited at file:line.` When no citation candidates exist: `> Gap: Citation-depth verified — no uncited identifiers found.` When a citation was unavailable: `> Gap: Citation unavailable for "<identifier>" — <reason>.` Silent pass is forbidden — see the [no silent action](output-contract.md#disposition-invariants) invariant.

package/skills/structure-prompt/reference/cleanup.md

@@ -1,33 +0,0 @@
-# Surface cleanup
-
-The optimized prompt has consistent surface formatting.
-
-## Pass list
-
-| Surface | State after cleanup |
-|---|---|
-| Typos in mission, metadata, framework, output spec, or questions | Spelled correctly |
-| Bullet style within a single section | Single style throughout (`-`) |
-| Code block language tags | Every fenced block inside the prompt artifact carries a language tag |
-| Trailing whitespace on lines | Removed |
-| Runs of 3+ blank lines | Collapsed to one blank line |
-| Heading levels | Sequential within each block (no jumps from `#` to `###`) |
-
-## Scope
-
-This pass changes surface formatting only. Identifiers, content, and ordering pass through unchanged.
-
-## Typo-correction carve-out
-
-Typo fixes apply only to plain-language prose — narrative sentences, mission statements, instructions to the agent, and similar running text. The pass leaves these surfaces untouched even when they look like typos:
-
-- Text inside backtick code spans (e.g., `` `mispelled_var` `` stays as-is)
-- Text inside fenced code blocks (any language, any content)
-- Identifiers, file paths, URLs, IDs, SHAs, ID prefixes, proper names
-- Any quoted substring the user could be referencing literally (e.g., `"recieve"` in quotes stays as-is)
-
-These surfaces are subject to the byte-for-byte preservation invariant in [`output-contract.md`](output-contract.md). When in doubt about whether a token is prose or a literal reference, leave it unchanged.
-
-## Disposition reporting
-
-Every surface-formatting change emits an action note via the mechanism that [`output-contract.md`](output-contract.md) defines (e.g., `> Gap: Typo corrected in mission line — "recieve" → "receive".`, `> Gap: Code block language tag added — python.`). When the surface pass makes zero changes, emit a single note: `> Gap: Surface cleanup verified — no formatting issues found.` Silent pass is forbidden — see the [no silent action](output-contract.md#disposition-invariants) invariant.

package/skills/structure-prompt/reference/constraints.md

@@ -1,33 +0,0 @@
-# Narrative directives → measurable criteria
-
-Every narrative directive in the optimized prompt names a measurable criterion.
-
-## Detection patterns
-
-A narrative directive opens with a soft verb:
-- "Try to `<X>`"
-- "Look at `<X>`"
-- "Make sure to `<X>`"
-- "Consider `<X>`"
-- "Be sure to `<X>`"
-- "Think about `<X>`"
-
-## Transformation
-
-Rewrite each narrative directive as a hard constraint with a measurable criterion.
-
-| Narrative input | Constraint output |
-|---|---|
-| "Try to be concise" | "Output ≤ 200 words." |
-| "Look at the security aspects" | "Inspect: input validation, auth checks, secret handling." |
-| "Make sure to verify" | "Verify each claim against the source. Cite file:line." |
-| "Consider edge cases" | "Enumerate: empty input, max-size input, concurrent input, malformed input." |
-| "Think about performance" | "Report wall-clock cost and memory cost for each candidate." |
-
-## Omission carve-out
-
-When a narrative directive resists rewriting without inventing scope the original prompt did not authorize, omit the directive from the rewritten prompt AND emit a gap note that records both the omitted directive verbatim and the reason it could not be made measurable (e.g., `> Gap: Omitted directive "Consider the edge cases" — no measurable criterion authorized by the source.`). The gap note routes through the paste-mode or file-path-mode gap-report mechanism that [`output-contract.md`](output-contract.md) defines for the active emission mode. Silent omission is forbidden — see the [no silent no-op](output-contract.md#disposition-invariants) invariant.
-
-## Cross-spoke deduplication
-
-When the [`directives.md`](directives.md) spoke has already produced identical measurable criteria (e.g., both spokes derive the same surface enumeration from overlapping input), the constraints spoke does not emit a duplicate output line. Instead it reports a merged gap note (e.g., `> Gap: Narrative directive "Try to find" merged with directives output — both derived the same measurable criteria "Inspect: SQL injection, XSS, auth issues."`). The gap note records the deduplication, satisfying the [no silent action](output-contract.md#disposition-invariants) invariant without emitting a duplicate line that the rewritten prompt would carry twice.

package/skills/structure-prompt/reference/directives.md

@@ -1,37 +0,0 @@
-# Performance directives → measurable constraints
-
-Every performance directive in the optimized prompt maps to a measurable constraint or a specific scope.
-
-## Detection patterns
-
-Common performance directives:
-- "Take a deep breath"
-- "Think step by step" / "Let's think step by step"
-- "You are an expert"
-- "Be thorough"
-- "Be comprehensive"
-- "Be careful" / "carefully"
-- "Do your best"
-- "Please"
-- "Kindly"
-
-## Transformation
-
-Each directive maps to a measurable constraint or to omission:
-
-| Directive | Replacement |
-|---|---|
-| "Be thorough" | A surface enumeration. e.g., "Inspect: input validation, auth, secret handling." |
-| "Be comprehensive" | A count target. e.g., "Produce at least 8 findings." |
-| "Be careful" / "carefully" | A locator requirement. e.g., "Cite file:line for every claim." |
-| "Think step by step" / "Let's think step by step" | omitted |
-| "Take a deep breath" | omitted |
-| "Please" / "Kindly" | omitted |
-| "You are an expert" | omitted (covered by the mission line) — unless the persona spoke's creative-writing carve-out preserved the role line intact, in which case leave "You are an expert" in place |
-| "Do your best" | omitted |
-
-Every transformation outcome — whether the directive was mapped to a measurable constraint or omitted — MUST emit an action note recording what changed via the mechanism that [`output-contract.md`](output-contract.md) defines (e.g., `> Gap: Directive "Be thorough" replaced with surface enumeration "Inspect: input validation, auth, secret handling."` or `> Gap: Directive "Take a deep breath" omitted — no measurable equivalent.`). See the [no silent action](output-contract.md#disposition-invariants) invariant.
-
-## Show-reasoning carve-out
-
-"Think step by step" stays intact when the prompt explicitly requires the agent to show its reasoning chain in the output. The carve-out MUST emit a gap note via the paste-mode or file-path-mode mechanism that [`output-contract.md`](output-contract.md) defines. See the [no silent no-op](output-contract.md#disposition-invariants) invariant.