From 7d88f13f58a184b3fb02d52d76c699efc5f13cbf Mon Sep 17 00:00:00 2001 From: garrytan Date: Thu, 8 Oct 2026 14:53:02 +0000 Subject: [PATCH 1/6] review: testing specialist treats negative assertions as decisions A new assertion that something is absent records a behavior removal and needs cited intent. A rename or removal in the diff can empty a standing negative assertion so it passes forever; the specialist now greps the suite for negative assertions naming the old value. Adopted from the testing-specialist part of a community PR; the scope-check hunk targeted text that no longer exists. Co-authored-by: EmilianoU26 <314541067+EmilianoU26@users.noreply.github.com> Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --- review/specialists/testing.md | 11 +++++++++++ test/review-workflow-clarity.test.ts | 13 ++++++++++++- 2 files changed, 23 insertions(+), 1 deletion(-) diff --git a/review/specialists/testing.md b/review/specialists/testing.md index 475ebfb4c..743dde892 100644 --- a/review/specialists/testing.md +++ b/review/specialists/testing.md @@ -58,6 +58,17 @@ red tests. Unit tests suit logic; real integration/E2E tests protect boundaries - Unicode and special characters in user-facing inputs - Concurrent access patterns with no race-condition test +### Negative Assertions +- A new assertion that something is absent (`not.toContain`, `not in`, `assertNotIn`, + `pytest.raises` on a call that used to succeed) records a behavior removal, not coverage. + Cite the spec line, plan item or PR text that authorizes the removal; with none, report it + as a product decision shipped as a test. +- A rename or removal in this diff can empty a standing negative assertion: a test asserting + the old token is absent now passes forever and guards nothing. For each identifier, flag, + heading or string the diff renames or deletes, grep the test suite for negative assertions + naming the old value, including inside tests that assert something else, and report each + as a coverage gap whose fix names the new value. + ### Test Isolation Violations - Tests sharing mutable state (class variables, global singletons, DB records not cleaned up) - Order-dependent tests (pass in sequence, fail when randomized) diff --git a/test/review-workflow-clarity.test.ts b/test/review-workflow-clarity.test.ts index bf46bc7aa..c267b58d4 100644 --- a/test/review-workflow-clarity.test.ts +++ b/test/review-workflow-clarity.test.ts @@ -7,7 +7,7 @@ import { generatePlanCompletionAuditReview, generatePlanCompletionAuditShip, gen import { generateQAReview } from '../scripts/resolvers/qa'; import { generateConfidenceCalibration } from '../scripts/resolvers/confidence'; import { HOST_PATHS, type TemplateContext } from '../scripts/resolvers/types'; -import { expectMentions } from './helpers/prompt-structure'; +import { between, compact, expectMentions, expectTokens } from './helpers/prompt-structure'; const root = join(import.meta.dir, '..'); const skill = readFileSync(join(root, 'review/SKILL.md.tmpl'), 'utf8'); @@ -466,3 +466,14 @@ test('ship and review count unverified or unavailable outside reviews as missing expect(read(rel)).toMatch(/`unverified` or `unavailable` is (listed as )?missing coverage[^.]*never (as )?(a )?pass/i); } }); + +test('testing specialist treats negative assertions as decisions and catches ones a rename emptied', () => { + const specialist = between(readFileSync(join(root, 'review/specialists/testing.md'), 'utf8'), '### Negative Assertions', '\n### '); + expectTokens(specialist, ['not.toContain', 'assertNotIn'], 'testing specialist'); + expectMentions(compact(specialist), [ + ['new', 'absent', 'removal', 'not coverage'], + ['authorizes', 'removal'], + ['rename', 'negative assertion', 'passes forever'], + ['grep', 'negative assertions', 'old value'], + ], 'testing specialist'); +}); From 574a0c8dbb179dd764ece99b19a76d80c4c109c3 Mon Sep 17 00:00:00 2001 From: garrytan Date: Thu, 8 Oct 2026 14:53:25 +0000 Subject: [PATCH 2/6] review: security specialist checks authorization a route-guard read misses Four access-control classes where the guard is correct and the object still leaks: error pages composed outside the guard, ownership surviving a role downgrade, list/detail/download paths checked as one, and a session mutated before the identity-switch callback is validated. Adopted to review/specialists/security.md only; the /cso hunk targeted a bullet list that is now an OWASP/ASVS table. Co-authored-by: EmilianoU26 <314541067+EmilianoU26@users.noreply.github.com> Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --- review/specialists/security.md | 4 ++++ test/review-workflow-clarity.test.ts | 10 ++++++++++ 2 files changed, 14 insertions(+) diff --git a/review/specialists/security.md b/review/specialists/security.md index b1d2e30c1..de7586585 100644 --- a/review/specialists/security.md +++ b/review/specialists/security.md @@ -26,6 +26,10 @@ This checklist goes deeper than the main CRITICAL pass. The main agent already c - Direct object reference vulnerabilities (user A accesses user B's data by changing an ID) - Session fixation or session hijacking opportunities - Token/API key validation that doesn't check expiration +- Error pages that leak past a correct guard: the shared 403/404/500 renderer builds its body outside the authorization path, so a blocked request still returns internal names, counts or navigation the role must not see. Read the error template and its context builder, not just the guard +- Ownership that survives a role downgrade: a grant recorded at creation still opens the object after the user's role is reduced and they sign in again. Ownership must be re-checked against the current role on every read +- List, detail and file/download access to one object audited as a single entry: each usually resolves the object through a different code path, so check each against the role matrix separately +- Account or identity switch that clears, regenerates or rebinds the session before validating the callback's single-use state value: any forced navigation to that URL logs the user out (CSRF). Also check the denied, cancelled and error branches, where leaving the prior session live keeps the user acting as the previous identity ### Injection Vectors (beyond SQL) - Command injection via subprocess calls with user-controlled arguments diff --git a/test/review-workflow-clarity.test.ts b/test/review-workflow-clarity.test.ts index c267b58d4..dd655cdf5 100644 --- a/test/review-workflow-clarity.test.ts +++ b/test/review-workflow-clarity.test.ts @@ -477,3 +477,13 @@ test('testing specialist treats negative assertions as decisions and catches one ['grep', 'negative assertions', 'old value'], ], 'testing specialist'); }); + +test('security specialist checks authorization paths a route-guard read misses', () => { + const auth = compact(between(readFileSync(join(root, 'review/specialists/security.md'), 'utf8'), '### Auth & Authorization Bypass', '\n### ')); + expectMentions(auth, [ + ['error', 'renderer', 'outside', 'guard'], + ['ownership', 'role', 'downgrade'], + ['list', 'detail', 'download', 'separately'], + ['session', 'before', 'validating', 'callback'], + ], 'security specialist'); +}); From 7707f5383ca94b709ba3b7251b165198db9a0f01 Mon Sep 17 00:00:00 2001 From: garrytan Date: Thu, 8 Oct 2026 14:54:05 +0000 Subject: [PATCH 3/6] review: zero findings is valid; suppress six common false positives The checklist now says a clean diff may come back clean, and suppresses framework-owned error handling, long exhaustive switches, null derefs a type guard already narrows, N+1 on fixed-cardinality loops, hardcoded test fixture values and non-cryptographic Math.random(). The contributor's "missing input validation on an internal function" and "missing await on fire-and-forget" suppressions are left out: both can hide real bugs. Co-authored-by: frosimanuel Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --- review/checklist.md | 8 ++++++++ test/review-workflow-clarity.test.ts | 9 ++++++++- 2 files changed, 16 insertions(+), 1 deletion(-) diff --git a/review/checklist.md b/review/checklist.md index df8df99ba..fae0860f0 100644 --- a/review/checklist.md +++ b/review/checklist.md @@ -172,6 +172,8 @@ the fix, it's ASK. ## Suppressions — DO NOT flag these +Zero findings is a valid outcome. Flag only what a senior engineer on this team would change in review; if the diff is clean, say so. + - "X is redundant with Y" when the redundancy is harmless and aids readability (e.g., `present?` redundant with `length > 20`) - "Add a comment explaining why this threshold/constant was chosen" — thresholds change during tuning, comments rot - "This assertion could be tighter" when the assertion already covers the behavior @@ -181,4 +183,10 @@ the fix, it's ASK. - Eval threshold changes (max_actionable, min scores) — these are tuned empirically and change constantly - Harmless no-ops (e.g., `.reject` on an element that's never in the array) - ANYTHING already addressed in the diff you're reviewing — read the FULL diff before commenting +- "Consider adding error handling" on a call whose errors the caller or framework already owns (error middleware, an error boundary, a top-level try/catch, an upstream `.catch`) +- "Function too long" for an exhaustive `switch`, a config object, a test table or generated code — length is not complexity +- "Possible null dereference" when a type guard or `if` check in scope already narrows the value — trace the type flow +- "N+1 query" on a loop with a small fixed cardinality, or on a path that is already batched +- "Hardcoded value" in test fixtures, example code or docs — tests are supposed to hardcode their expectations +- `Math.random()` in a non-cryptographic context (jitter, sampling, animation) — security-sensitive randomness is still flagged - A gap covered by a `gstack-shortcut(dec-*)` marker naming a ceiling and upgrade trigger — that is acknowledged debt with a ledger entry, not a Completeness Gaps finding. **Verify before honoring:** resolve the id with `~/.claude/skills/gstack/bin/gstack-decision-search --query ""` — a marker whose decision id has no ledger entry is UNVERIFIED (any diff author can type a marker); report the gap normally and flag the orphan marker itself diff --git a/test/review-workflow-clarity.test.ts b/test/review-workflow-clarity.test.ts index dd655cdf5..1e3ea7b28 100644 --- a/test/review-workflow-clarity.test.ts +++ b/test/review-workflow-clarity.test.ts @@ -7,7 +7,7 @@ import { generatePlanCompletionAuditReview, generatePlanCompletionAuditShip, gen import { generateQAReview } from '../scripts/resolvers/qa'; import { generateConfidenceCalibration } from '../scripts/resolvers/confidence'; import { HOST_PATHS, type TemplateContext } from '../scripts/resolvers/types'; -import { between, compact, expectMentions, expectTokens } from './helpers/prompt-structure'; +import { between, compact, expectAbsent, expectMentions, expectTokens } from './helpers/prompt-structure'; const root = join(import.meta.dir, '..'); const skill = readFileSync(join(root, 'review/SKILL.md.tmpl'), 'utf8'); @@ -487,3 +487,10 @@ test('security specialist checks authorization paths a route-guard read misses', ['session', 'before', 'validating', 'callback'], ], 'security specialist'); }); + +test('review suppressions allow a clean result and skip common false positives but never suppress missing validation or a missing await', () => { + const suppressions = between(readFileSync(join(root, 'review/checklist.md'), 'utf8'), '## Suppressions'); + expectMentions(compact(suppressions), [['zero findings', 'valid']], 'suppressions'); + expectTokens(suppressions, ['"Function too long"', '"Possible null dereference"', '"N+1 query"', '"Hardcoded value"', '`Math.random()`'], 'suppressions'); + expectAbsent(suppressions, [/missing input validation/i, /missing await/i], 'suppressions'); +}); From e32cbe5fca8fe770df36404b5b915500dade0709 Mon Sep 17 00:00:00 2001 From: garrytan Date: Thu, 8 Oct 2026 14:55:18 +0000 Subject: [PATCH 4/6] design-review: capture code tokens before universal principles /design-review read only DESIGN.md and otherwise fell back to universal principles, so a project whose system lives in CSS custom properties, tailwind.config or a theme file got audited and mocked up against an invented aesthetic. The skill now reads code tokens before falling back, and the target-mockup brief reuses the captured colors, fonts, radii and spacing, changing layout only. The contributor's optional microcopy checks (domain vocabulary, human register) are not adopted here. Co-authored-by: Tom Lam Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --- design-review/SKILL.md | 8 ++++---- design-review/SKILL.md.tmpl | 6 +++--- scripts/resolvers/design.ts | 2 +- test/review-entry-and-design-clarity-au.test.ts | 12 +++++++++++- 4 files changed, 19 insertions(+), 9 deletions(-) diff --git a/design-review/SKILL.md b/design-review/SKILL.md index d4dac091a..48dc45843 100644 --- a/design-review/SKILL.md +++ b/design-review/SKILL.md @@ -403,9 +403,9 @@ You are a senior product designer AND a frontend engineer. Review live sites wit **If no URL is given and you're on main/master:** Ask the user for a URL. -**Check for DESIGN.md:** +**Capture the project's design system:** -Look for `DESIGN.md`, `design-system.md`, or similar in the repo root. If found, read it — all design decisions must be calibrated against it. Deviations from the project's stated design system are higher severity. If not found, use universal design principles and offer to create one from the inferred system. +Look for `DESIGN.md`, `design-system.md`, or similar in the repo root, then for the tokens the code ships: `:root` CSS custom properties, `tailwind.config.*`, and theme or tokens files. Read what exists; Phase 2 adds what the page renders. All design decisions are calibrated against this system, and deviations from it are higher severity. Use universal design principles only when the project has neither a design doc nor code tokens, and offer to create a DESIGN.md from the inferred system. **DESIGN.md format:** @@ -413,7 +413,7 @@ Look for `DESIGN.md`, `design-system.md`, or similar in the repo root. If found, bun --no-env-file run $HOME/.claude/skills/gstack/bin/gstack-design-md.ts check DESIGN.md ``` -`DESIGN_MD_FORMAT: spec`: the front matter is normative. Run `bun --no-env-file run $HOME/.claude/skills/gstack/bin/gstack-design-md.ts tokens DESIGN.md` and calibrate against the flat token map: a value present there is never a finding, and a finding that departs from a token names the token. `legacy` or `unknown`: read the file as prose. The `DESIGN_MD_MARKER` line is the user's persisted format choice; respect it and never offer a conversion here (that is /design-consultation's question). `missing`: universal principles. +`DESIGN_MD_FORMAT: spec`: the front matter is normative. Run `bun --no-env-file run $HOME/.claude/skills/gstack/bin/gstack-design-md.ts tokens DESIGN.md` and calibrate against the flat token map: a value present there is never a finding, and a finding that departs from a token names the token. `legacy` or `unknown`: read the file as prose. The `DESIGN_MD_MARKER` line is the user's persisted format choice; respect it and never offer a conversion here (that is /design-consultation's question). `missing`: calibrate against the code tokens captured above, or universal principles when there are none. **Check for clean working tree:** @@ -1764,7 +1764,7 @@ For each fixable finding, in impact order: ### 8a.5. Target Mockup (if DESIGN_READY) -If the gstack designer is available and the finding involves visual layout, hierarchy, or spacing (not just a CSS value fix like wrong color or font-size), generate a target mockup showing what the corrected version should look like. Write the description of the page or component with the finding fixed, referencing DESIGN.md constraints, into a private file: +If the gstack designer is available and the finding involves visual layout, hierarchy, or spacing (not just a CSS value fix like wrong color or font-size), generate a target mockup showing what the corrected version should look like. Write the description of the page or component with the finding fixed into a private file. The brief reuses the captured system verbatim (the same colors, fonts, radii and spacing scale) and changes layout or structure only; never introduce a new palette or typeface for a product that already has one: ```bash _GT="$(git rev-parse --show-toplevel 2>/dev/null || pwd)/.gstack/tmp" diff --git a/design-review/SKILL.md.tmpl b/design-review/SKILL.md.tmpl index 896e8cc17..4e7960250 100644 --- a/design-review/SKILL.md.tmpl +++ b/design-review/SKILL.md.tmpl @@ -48,9 +48,9 @@ You are a senior product designer AND a frontend engineer. Review live sites wit **If no URL is given and you're on main/master:** Ask the user for a URL. -**Check for DESIGN.md:** +**Capture the project's design system:** -Look for `DESIGN.md`, `design-system.md`, or similar in the repo root. If found, read it — all design decisions must be calibrated against it. Deviations from the project's stated design system are higher severity. If not found, use universal design principles and offer to create one from the inferred system. +Look for `DESIGN.md`, `design-system.md`, or similar in the repo root, then for the tokens the code ships: `:root` CSS custom properties, `tailwind.config.*`, and theme or tokens files. Read what exists; Phase 2 adds what the page renders. All design decisions are calibrated against this system, and deviations from it are higher severity. Use universal design principles only when the project has neither a design doc nor code tokens, and offer to create a DESIGN.md from the inferred system. {{DESIGN_MD_CHECK:calibrate}} @@ -176,7 +176,7 @@ For each fixable finding, in impact order: ### 8a.5. Target Mockup (if DESIGN_READY) -If the gstack designer is available and the finding involves visual layout, hierarchy, or spacing (not just a CSS value fix like wrong color or font-size), generate a target mockup showing what the corrected version should look like. Write the description of the page or component with the finding fixed, referencing DESIGN.md constraints, into a private file: +If the gstack designer is available and the finding involves visual layout, hierarchy, or spacing (not just a CSS value fix like wrong color or font-size), generate a target mockup showing what the corrected version should look like. Write the description of the page or component with the finding fixed into a private file. The brief reuses the captured system verbatim (the same colors, fonts, radii and spacing scale) and changes layout or structure only; never introduce a new palette or typeface for a product that already has one: {{FREE_TEXT_FILE:BRIEF_FILE=brief}} diff --git a/scripts/resolvers/design.ts b/scripts/resolvers/design.ts index 32d90d871..be1e68ba6 100644 --- a/scripts/resolvers/design.ts +++ b/scripts/resolvers/design.ts @@ -982,7 +982,7 @@ ${bin} check DESIGN.md ${check} -\`${SENTINEL.DESIGN_MD_FORMAT}: spec\`: the front matter is normative. Run \`${bin} tokens DESIGN.md\` and calibrate against the flat token map: a value present there is never a finding, and a finding that departs from a token names the token. \`legacy\` or \`unknown\`: read the file as prose. The \`DESIGN_MD_MARKER\` line is the user's persisted format choice; respect it and never offer a conversion here (that is /design-consultation's question). \`missing\`: universal principles.`; +\`${SENTINEL.DESIGN_MD_FORMAT}: spec\`: the front matter is normative. Run \`${bin} tokens DESIGN.md\` and calibrate against the flat token map: a value present there is never a finding, and a finding that departs from a token names the token. \`legacy\` or \`unknown\`: read the file as prose. The \`DESIGN_MD_MARKER\` line is the user's persisted format choice; respect it and never offer a conversion here (that is /design-consultation's question). \`missing\`: calibrate against the code tokens captured above, or universal principles when there are none.`; } return `**Update-only gate:** Only **Update** with DESIGN.md enters this block (command and all result branches). **Start fresh**, **No existing file**, or a lone design-system.md: skip to **Gather product context from the codebase**. **Cancel** has already stopped the skill. diff --git a/test/review-entry-and-design-clarity-au.test.ts b/test/review-entry-and-design-clarity-au.test.ts index ca5093b77..2dfc25ab5 100644 --- a/test/review-entry-and-design-clarity-au.test.ts +++ b/test/review-entry-and-design-clarity-au.test.ts @@ -8,7 +8,7 @@ import {generatePreambleBash} from '../scripts/resolvers/preamble/generate-pream import {generatePlanModeInfo} from '../scripts/resolvers/preamble/generate-completion-status'; import {generateDesignHardRules} from '../scripts/resolvers/design'; import {E2E_TOUCHFILES, LLM_JUDGE_TOUCHFILES, selectTests} from './helpers/touchfiles'; -import { expectMentions } from './helpers/prompt-structure'; +import { between, compact, expectMentions, expectTokens } from './helpers/prompt-structure'; const root = path.resolve(import.meta.dir, '..'); const announcement = 'Scope gate: plan mode — auto-selected B (reviewing ).'; @@ -105,3 +105,13 @@ test('new regression and changed preamble sources select all Design and Eng owne } } }); + +test('design-review captures code tokens before universal principles and reuses them in target mockups', () => { + const skill = fs.readFileSync(path.join(root, 'design-review/SKILL.md'), 'utf8'); + const capture = between(skill, '**Capture the project\'s design system:**', '## Phase 1'); + expectTokens(capture, ['`tailwind.config.*`', '`:root`'], 'design-system capture'); + expectMentions(compact(capture), [['universal', 'only', 'neither', 'code tokens']], 'design-system capture'); + const mockup = compact(between(skill, '### 8a.5. Target Mockup', '### 8b.')); + expectMentions(mockup, [['brief', 'reuses', 'captured', 'colors', 'fonts']], 'target mockup'); + expectMentions(mockup, [['never', 'new palette', 'already has one']], 'target mockup'); +}); From 8d1db315afcd7cf28ddc90a8719de2ec00a0b6a6 Mon Sep 17 00:00:00 2001 From: garrytan Date: Thu, 8 Oct 2026 14:58:33 +0000 Subject: [PATCH 5/6] voice: ban the "load-bearing" stock phrase Models overuse "load-bearing"; it joins the AI-vocabulary ban line in both voice tiers. The tier-2 voice directive is also tightened (the meta "compressed for runtime" tag and the bounded closer's restated exemption clause) so the shared preamble shrinks by 163 bytes per tier-2+ skill, which also pays for the reply-language rule that follows. The ship goldens are refreshed for the new render. Co-authored-by: Nader Helmy Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --- SKILL.md | 2 +- autoplan/SKILL.md | 6 +++--- benchmark-models/SKILL.md | 2 +- benchmark/SKILL.md | 2 +- browse/SKILL.md | 2 +- canary/SKILL.md | 6 +++--- codex/SKILL.md | 6 +++--- context-restore/SKILL.md | 6 +++--- context-save/SKILL.md | 6 +++--- design-consultation/SKILL.md | 6 +++--- design-html/SKILL.md | 6 +++--- design-review/SKILL.md | 6 +++--- design-shotgun/SKILL.md | 6 +++--- devex-review/SKILL.md | 6 +++--- diagram/SKILL.md | 2 +- document-generate/SKILL.md | 6 +++--- document-release/SKILL.md | 6 +++--- health/SKILL.md | 6 +++--- investigate/SKILL.md | 6 +++--- ios-clean/SKILL.md | 6 +++--- ios-design-review/SKILL.md | 6 +++--- ios-fix/SKILL.md | 6 +++--- ios-qa/SKILL.md | 6 +++--- ios-sync/SKILL.md | 6 +++--- land-and-deploy/SKILL.md | 6 +++--- landing-report/SKILL.md | 6 +++--- learn/SKILL.md | 6 +++--- make-pdf/SKILL.md | 2 +- office-hours/SKILL.md | 6 +++--- open-gstack-browser/SKILL.md | 2 +- pair-agent/SKILL.md | 6 +++--- plan-ceo-review/SKILL.md | 6 +++--- plan-design-review/SKILL.md | 6 +++--- plan-devex-review/SKILL.md | 6 +++--- plan-eng-review/SKILL.md | 6 +++--- plan-tune/SKILL.md | 6 +++--- qa-only/SKILL.md | 6 +++--- qa/SKILL.md | 6 +++--- retro/SKILL.md | 6 +++--- review/SKILL.md | 6 +++--- scrape/SKILL.md | 2 +- .../resolvers/preamble/generate-voice-directive.ts | 8 ++++---- setup-browser-cookies/SKILL.md | 2 +- setup-deploy/SKILL.md | 6 +++--- setup-gbrain/SKILL.md | 6 +++--- ship/SKILL.md | 6 +++--- skillify/SKILL.md | 6 +++--- spec/SKILL.md | 6 +++--- sync-gbrain/SKILL.md | 6 +++--- test-audit/SKILL.md | 6 +++--- test/fixtures/golden/claude-ship-SKILL.md | 6 +++--- test/fixtures/golden/codex-ship-SKILL.md | 6 +++--- test/fixtures/golden/factory-ship-SKILL.md | 6 +++--- test/voice-directive.test.ts | 14 ++++++++++++++ 54 files changed, 156 insertions(+), 142 deletions(-) create mode 100644 test/voice-directive.test.ts diff --git a/SKILL.md b/SKILL.md index 9105de88e..0c23dcdbf 100644 --- a/SKILL.md +++ b/SKILL.md @@ -96,7 +96,7 @@ find, grep). The dedicated tools are cheaper and clearer. Direct, concrete, builder-to-builder. Name the file, function, command, and user-visible impact. No filler. -No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted. Never corporate or academic. Short paragraphs. End with what to do. +No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, load-bearing. Never corporate or academic. Short paragraphs. End with what to do. The user has context you do not. Cross-model agreement is a recommendation, not a decision. The user decides. diff --git a/autoplan/SKILL.md b/autoplan/SKILL.md index d3dfbcdca..c94df5a77 100644 --- a/autoplan/SKILL.md +++ b/autoplan/SKILL.md @@ -228,7 +228,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -236,13 +236,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/benchmark-models/SKILL.md b/benchmark-models/SKILL.md index 9dedb187b..b0b56f3a6 100644 --- a/benchmark-models/SKILL.md +++ b/benchmark-models/SKILL.md @@ -100,7 +100,7 @@ find, grep). The dedicated tools are cheaper and clearer. Direct, concrete, builder-to-builder. Name the file, function, command, and user-visible impact. No filler. -No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted. Never corporate or academic. Short paragraphs. End with what to do. +No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, load-bearing. Never corporate or academic. Short paragraphs. End with what to do. The user has context you do not. Cross-model agreement is a recommendation, not a decision. The user decides. diff --git a/benchmark/SKILL.md b/benchmark/SKILL.md index 924ea0269..0b2c0e0d1 100644 --- a/benchmark/SKILL.md +++ b/benchmark/SKILL.md @@ -101,7 +101,7 @@ find, grep). The dedicated tools are cheaper and clearer. Direct, concrete, builder-to-builder. Name the file, function, command, and user-visible impact. No filler. -No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted. Never corporate or academic. Short paragraphs. End with what to do. +No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, load-bearing. Never corporate or academic. Short paragraphs. End with what to do. The user has context you do not. Cross-model agreement is a recommendation, not a decision. The user decides. diff --git a/browse/SKILL.md b/browse/SKILL.md index 94df6eefa..f80939f3a 100644 --- a/browse/SKILL.md +++ b/browse/SKILL.md @@ -96,7 +96,7 @@ find, grep). The dedicated tools are cheaper and clearer. Direct, concrete, builder-to-builder. Name the file, function, command, and user-visible impact. No filler. -No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted. Never corporate or academic. Short paragraphs. End with what to do. +No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, load-bearing. Never corporate or academic. Short paragraphs. End with what to do. The user has context you do not. Cross-model agreement is a recommendation, not a decision. The user decides. diff --git a/canary/SKILL.md b/canary/SKILL.md index 11226e9d4..d4c2b2157 100644 --- a/canary/SKILL.md +++ b/canary/SKILL.md @@ -209,7 +209,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -217,13 +217,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/codex/SKILL.md b/codex/SKILL.md index 7e9f2ecf3..777ce5cb2 100644 --- a/codex/SKILL.md +++ b/codex/SKILL.md @@ -212,7 +212,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -220,13 +220,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/context-restore/SKILL.md b/context-restore/SKILL.md index 29969b1f7..8dfe9b8d4 100644 --- a/context-restore/SKILL.md +++ b/context-restore/SKILL.md @@ -211,7 +211,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -219,13 +219,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/context-save/SKILL.md b/context-save/SKILL.md index 9caf2e13c..f1db7349d 100644 --- a/context-save/SKILL.md +++ b/context-save/SKILL.md @@ -210,7 +210,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -218,13 +218,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/design-consultation/SKILL.md b/design-consultation/SKILL.md index e7a1d2139..688369d6d 100644 --- a/design-consultation/SKILL.md +++ b/design-consultation/SKILL.md @@ -235,7 +235,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -243,13 +243,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/design-html/SKILL.md b/design-html/SKILL.md index ca10c55b6..491e9c957 100644 --- a/design-html/SKILL.md +++ b/design-html/SKILL.md @@ -216,7 +216,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -224,13 +224,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/design-review/SKILL.md b/design-review/SKILL.md index 48dc45843..c9d913831 100644 --- a/design-review/SKILL.md +++ b/design-review/SKILL.md @@ -213,7 +213,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -221,13 +221,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/design-shotgun/SKILL.md b/design-shotgun/SKILL.md index 6ed709651..6d59b14b5 100644 --- a/design-shotgun/SKILL.md +++ b/design-shotgun/SKILL.md @@ -229,7 +229,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -237,13 +237,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/devex-review/SKILL.md b/devex-review/SKILL.md index 35c3f2cd3..b1b9f5617 100644 --- a/devex-review/SKILL.md +++ b/devex-review/SKILL.md @@ -215,7 +215,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -223,13 +223,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/diagram/SKILL.md b/diagram/SKILL.md index 74c64cdd1..1a44c768d 100644 --- a/diagram/SKILL.md +++ b/diagram/SKILL.md @@ -99,7 +99,7 @@ find, grep). The dedicated tools are cheaper and clearer. Direct, concrete, builder-to-builder. Name the file, function, command, and user-visible impact. No filler. -No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted. Never corporate or academic. Short paragraphs. End with what to do. +No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, load-bearing. Never corporate or academic. Short paragraphs. End with what to do. The user has context you do not. Cross-model agreement is a recommendation, not a decision. The user decides. diff --git a/document-generate/SKILL.md b/document-generate/SKILL.md index c417c387c..53b380dab 100644 --- a/document-generate/SKILL.md +++ b/document-generate/SKILL.md @@ -215,7 +215,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -223,13 +223,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/document-release/SKILL.md b/document-release/SKILL.md index e307f55ad..c6cdb946a 100644 --- a/document-release/SKILL.md +++ b/document-release/SKILL.md @@ -213,7 +213,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -221,13 +221,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/health/SKILL.md b/health/SKILL.md index 735cf4826..4acaef9b6 100644 --- a/health/SKILL.md +++ b/health/SKILL.md @@ -211,7 +211,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -219,13 +219,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/investigate/SKILL.md b/investigate/SKILL.md index 7c33545d9..597292536 100644 --- a/investigate/SKILL.md +++ b/investigate/SKILL.md @@ -255,7 +255,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -263,13 +263,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/ios-clean/SKILL.md b/ios-clean/SKILL.md index 392167498..b76c5785a 100644 --- a/ios-clean/SKILL.md +++ b/ios-clean/SKILL.md @@ -213,7 +213,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -221,13 +221,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/ios-design-review/SKILL.md b/ios-design-review/SKILL.md index 7baf2877d..3bd297c4d 100644 --- a/ios-design-review/SKILL.md +++ b/ios-design-review/SKILL.md @@ -215,7 +215,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -223,13 +223,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/ios-fix/SKILL.md b/ios-fix/SKILL.md index 29dc12111..012adc18b 100644 --- a/ios-fix/SKILL.md +++ b/ios-fix/SKILL.md @@ -216,7 +216,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -224,13 +224,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/ios-qa/SKILL.md b/ios-qa/SKILL.md index d9c68e49d..615d47f1c 100644 --- a/ios-qa/SKILL.md +++ b/ios-qa/SKILL.md @@ -220,7 +220,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -228,13 +228,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/ios-sync/SKILL.md b/ios-sync/SKILL.md index abec253c6..274363991 100644 --- a/ios-sync/SKILL.md +++ b/ios-sync/SKILL.md @@ -213,7 +213,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -221,13 +221,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/land-and-deploy/SKILL.md b/land-and-deploy/SKILL.md index 46e0da65f..398107100 100644 --- a/land-and-deploy/SKILL.md +++ b/land-and-deploy/SKILL.md @@ -208,7 +208,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -216,13 +216,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/landing-report/SKILL.md b/landing-report/SKILL.md index a973c4108..de688d27c 100644 --- a/landing-report/SKILL.md +++ b/landing-report/SKILL.md @@ -210,7 +210,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -218,13 +218,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/learn/SKILL.md b/learn/SKILL.md index 2184050cb..b7bdf2ec9 100644 --- a/learn/SKILL.md +++ b/learn/SKILL.md @@ -211,7 +211,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -219,13 +219,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/make-pdf/SKILL.md b/make-pdf/SKILL.md index a7984fea1..fb9a83200 100644 --- a/make-pdf/SKILL.md +++ b/make-pdf/SKILL.md @@ -137,7 +137,7 @@ find, grep). The dedicated tools are cheaper and clearer. Direct, concrete, builder-to-builder. Name the file, function, command, and user-visible impact. No filler. -No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted. Never corporate or academic. Short paragraphs. End with what to do. +No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, load-bearing. Never corporate or academic. Short paragraphs. End with what to do. The user has context you do not. Cross-model agreement is a recommendation, not a decision. The user decides. diff --git a/office-hours/SKILL.md b/office-hours/SKILL.md index bb982c76f..7b7179f7b 100644 --- a/office-hours/SKILL.md +++ b/office-hours/SKILL.md @@ -256,7 +256,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -264,13 +264,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/open-gstack-browser/SKILL.md b/open-gstack-browser/SKILL.md index aa4071bb7..72b5a1916 100644 --- a/open-gstack-browser/SKILL.md +++ b/open-gstack-browser/SKILL.md @@ -98,7 +98,7 @@ find, grep). The dedicated tools are cheaper and clearer. Direct, concrete, builder-to-builder. Name the file, function, command, and user-visible impact. No filler. -No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted. Never corporate or academic. Short paragraphs. End with what to do. +No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, load-bearing. Never corporate or academic. Short paragraphs. End with what to do. The user has context you do not. Cross-model agreement is a recommendation, not a decision. The user decides. diff --git a/pair-agent/SKILL.md b/pair-agent/SKILL.md index 9e64c039a..4acea278a 100644 --- a/pair-agent/SKILL.md +++ b/pair-agent/SKILL.md @@ -212,7 +212,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -220,13 +220,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/plan-ceo-review/SKILL.md b/plan-ceo-review/SKILL.md index 89c40f04c..aa908bf83 100644 --- a/plan-ceo-review/SKILL.md +++ b/plan-ceo-review/SKILL.md @@ -237,7 +237,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -245,13 +245,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/plan-design-review/SKILL.md b/plan-design-review/SKILL.md index 4ece30f26..b1f893e4a 100644 --- a/plan-design-review/SKILL.md +++ b/plan-design-review/SKILL.md @@ -237,7 +237,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -245,13 +245,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/plan-devex-review/SKILL.md b/plan-devex-review/SKILL.md index 3959013ed..087d1e9c5 100644 --- a/plan-devex-review/SKILL.md +++ b/plan-devex-review/SKILL.md @@ -209,7 +209,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -217,13 +217,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/plan-eng-review/SKILL.md b/plan-eng-review/SKILL.md index 4a7a4b981..0aa8cdc2b 100644 --- a/plan-eng-review/SKILL.md +++ b/plan-eng-review/SKILL.md @@ -253,7 +253,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -261,13 +261,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- Do not add em dashes in prose you compose during the review. Existing templates, quoted text, command output, and required copied labels may contain them. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- Do not add em dashes in prose you compose during the review. Existing templates, quoted text, command output, and required copied labels may contain them. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/plan-tune/SKILL.md b/plan-tune/SKILL.md index 12110f1a8..94ff1312a 100644 --- a/plan-tune/SKILL.md +++ b/plan-tune/SKILL.md @@ -221,7 +221,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -229,13 +229,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/qa-only/SKILL.md b/qa-only/SKILL.md index a08d041bf..126bf4a80 100644 --- a/qa-only/SKILL.md +++ b/qa-only/SKILL.md @@ -211,7 +211,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -219,13 +219,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/qa/SKILL.md b/qa/SKILL.md index ecd1a11f4..b9d25474b 100644 --- a/qa/SKILL.md +++ b/qa/SKILL.md @@ -215,7 +215,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -223,13 +223,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/retro/SKILL.md b/retro/SKILL.md index bf2f65e72..7ad8a1cfa 100644 --- a/retro/SKILL.md +++ b/retro/SKILL.md @@ -229,7 +229,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -237,13 +237,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/review/SKILL.md b/review/SKILL.md index 3ccab19c5..2a65e6385 100644 --- a/review/SKILL.md +++ b/review/SKILL.md @@ -213,7 +213,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -221,13 +221,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/scrape/SKILL.md b/scrape/SKILL.md index a054f1698..fda2ef1e0 100644 --- a/scrape/SKILL.md +++ b/scrape/SKILL.md @@ -95,7 +95,7 @@ find, grep). The dedicated tools are cheaper and clearer. Direct, concrete, builder-to-builder. Name the file, function, command, and user-visible impact. No filler. -No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted. Never corporate or academic. Short paragraphs. End with what to do. +No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, load-bearing. Never corporate or academic. Short paragraphs. End with what to do. The user has context you do not. Cross-model agreement is a recommendation, not a decision. The user decides. diff --git a/scripts/resolvers/preamble/generate-voice-directive.ts b/scripts/resolvers/preamble/generate-voice-directive.ts index 80856c8b6..4bf9a0011 100644 --- a/scripts/resolvers/preamble/generate-voice-directive.ts +++ b/scripts/resolvers/preamble/generate-voice-directive.ts @@ -11,14 +11,14 @@ export function generateVoiceDirective(ctx: TemplateContext, tier: number): stri Direct, concrete, builder-to-builder. Name the file, function, command, and user-visible impact. No filler. -${emDashRule} No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted. Never corporate or academic. Short paragraphs. End with what to do. +${emDashRule} No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, load-bearing. Never corporate or academic. Short paragraphs. End with what to do. The user has context you do not. Cross-model agreement is a recommendation, not a decision. The user decides.`; } return `## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -26,13 +26,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- ${emDashRule} No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- ${emDashRule} No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned.`; diff --git a/setup-browser-cookies/SKILL.md b/setup-browser-cookies/SKILL.md index 1814e7dda..45e56c06b 100644 --- a/setup-browser-cookies/SKILL.md +++ b/setup-browser-cookies/SKILL.md @@ -94,7 +94,7 @@ find, grep). The dedicated tools are cheaper and clearer. Direct, concrete, builder-to-builder. Name the file, function, command, and user-visible impact. No filler. -No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted. Never corporate or academic. Short paragraphs. End with what to do. +No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, load-bearing. Never corporate or academic. Short paragraphs. End with what to do. The user has context you do not. Cross-model agreement is a recommendation, not a decision. The user decides. diff --git a/setup-deploy/SKILL.md b/setup-deploy/SKILL.md index f6b6671e1..6fca5618e 100644 --- a/setup-deploy/SKILL.md +++ b/setup-deploy/SKILL.md @@ -212,7 +212,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -220,13 +220,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/setup-gbrain/SKILL.md b/setup-gbrain/SKILL.md index 66e6942fe..e16b9517b 100644 --- a/setup-gbrain/SKILL.md +++ b/setup-gbrain/SKILL.md @@ -211,7 +211,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -219,13 +219,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/ship/SKILL.md b/ship/SKILL.md index 05022421d..b64ddf867 100644 --- a/ship/SKILL.md +++ b/ship/SKILL.md @@ -213,7 +213,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -221,13 +221,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/skillify/SKILL.md b/skillify/SKILL.md index 4b57e3fb2..ea2107677 100644 --- a/skillify/SKILL.md +++ b/skillify/SKILL.md @@ -210,7 +210,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -218,13 +218,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/spec/SKILL.md b/spec/SKILL.md index 04e1f195f..54ab08e2d 100644 --- a/spec/SKILL.md +++ b/spec/SKILL.md @@ -211,7 +211,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -219,13 +219,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/sync-gbrain/SKILL.md b/sync-gbrain/SKILL.md index cedb2eb6c..d4ed3bd82 100644 --- a/sync-gbrain/SKILL.md +++ b/sync-gbrain/SKILL.md @@ -212,7 +212,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -220,13 +220,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/test-audit/SKILL.md b/test-audit/SKILL.md index 0b6a8d46d..6f3c6c210 100644 --- a/test-audit/SKILL.md +++ b/test-audit/SKILL.md @@ -207,7 +207,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -215,13 +215,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/test/fixtures/golden/claude-ship-SKILL.md b/test/fixtures/golden/claude-ship-SKILL.md index 05022421d..b64ddf867 100644 --- a/test/fixtures/golden/claude-ship-SKILL.md +++ b/test/fixtures/golden/claude-ship-SKILL.md @@ -213,7 +213,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -221,13 +221,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/test/fixtures/golden/codex-ship-SKILL.md b/test/fixtures/golden/codex-ship-SKILL.md index c65a05df7..5873804e7 100644 --- a/test/fixtures/golden/codex-ship-SKILL.md +++ b/test/fixtures/golden/codex-ship-SKILL.md @@ -216,7 +216,7 @@ Completion bias does not override safety gates. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -224,13 +224,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/test/fixtures/golden/factory-ship-SKILL.md b/test/fixtures/golden/factory-ship-SKILL.md index 67e586767..dae060274 100644 --- a/test/fixtures/golden/factory-ship-SKILL.md +++ b/test/fixtures/golden/factory-ship-SKILL.md @@ -197,7 +197,7 @@ find, grep). The dedicated tools are cheaper and clearer. ## Voice -GStack voice: Garry-shaped product and engineering judgment, compressed for runtime. +GStack voice: Garry-shaped product and engineering judgment. - Lead with the point. Say what it does, why it matters, and what changes for the builder. - Be concrete. Name files, functions, line numbers, commands, outputs, evals, and real numbers. @@ -205,13 +205,13 @@ GStack voice: Garry-shaped product and engineering judgment, compressed for runt - Be direct about quality. Bugs matter. Edge cases matter. Fix the whole thing, not the demo path. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. -- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant. +- No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours, no unrequested design notes. If the explanation outgrows the change, cut the explanation. Exempt: AskUserQuestion decision briefs, completion-status blocks, anything the user explicitly asked to be explained, and a skill's mandated report format — the report IS the work in report-shaped skills (/qa-only, /plan-*-review, /retro, /document-generate); this rule governs unrequested prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/test/voice-directive.test.ts b/test/voice-directive.test.ts new file mode 100644 index 000000000..14bfae690 --- /dev/null +++ b/test/voice-directive.test.ts @@ -0,0 +1,14 @@ +import { describe, expect, test } from 'bun:test'; +import { generateVoiceDirective } from '../scripts/resolvers/preamble/generate-voice-directive'; +import { HOST_PATHS, type TemplateContext } from '../scripts/resolvers/types'; + +const ctx: TemplateContext = { skillName: 'review', tmplPath: 'review/SKILL.md.tmpl', host: 'claude', paths: HOST_PATHS.claude }; +const tiers: number[] = [1, 3]; + +describe('shared voice directive', () => { + test.each(tiers)('tier %i bans the load-bearing stock phrase on the AI-vocabulary line', tier => { + const banLine = generateVoiceDirective(ctx, tier).split('\n').find(line => line.includes('No AI vocabulary:')); + expect(banLine).toBeDefined(); + expect(banLine!).toContain('load-bearing'); + }); +}); From e5dc011b7ceca4d5e9578afc5cde48ddccb2f6e7 Mon Sep 17 00:00:00 2001 From: garrytan Date: Thu, 8 Oct 2026 15:02:53 +0000 Subject: [PATCH 6/6] voice: reply in the language of the user's latest message Every skill's voice directive now tells the agent to reply in the language of the user's latest message unless asked otherwise, so long English skill text no longer drags a Chinese (or any non-English) session into English. Mixed-language sessions follow the latest message. Code, commands, paths, identifiers and quoted output stay verbatim, and at tier 2+ so do the machine-read question markers (D, option letters, (recommended)). The rule costs 205 bytes per tier-2+ skill and 144 per tier-1 skill. A further 25-byte cut to the bounded closer's exemption list leaves the net for this wave at +17 bytes per tier-2+ skill and +158 per tier-1 skill. review, qa and browse caps rise with measured notes; the ship goldens are refreshed. Co-authored-by: Xianying Tan Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --- SKILL.md | 2 ++ autoplan/SKILL.md | 3 ++- benchmark-models/SKILL.md | 2 ++ benchmark/SKILL.md | 2 ++ browse/SKILL.md | 2 ++ canary/SKILL.md | 3 ++- codex/SKILL.md | 3 ++- context-restore/SKILL.md | 3 ++- context-save/SKILL.md | 3 ++- design-consultation/SKILL.md | 3 ++- design-html/SKILL.md | 3 ++- design-review/SKILL.md | 3 ++- design-shotgun/SKILL.md | 3 ++- devex-review/SKILL.md | 3 ++- diagram/SKILL.md | 2 ++ document-generate/SKILL.md | 3 ++- document-release/SKILL.md | 3 ++- health/SKILL.md | 3 ++- investigate/SKILL.md | 3 ++- ios-clean/SKILL.md | 3 ++- ios-design-review/SKILL.md | 3 ++- ios-fix/SKILL.md | 3 ++- ios-qa/SKILL.md | 3 ++- ios-sync/SKILL.md | 3 ++- land-and-deploy/SKILL.md | 3 ++- landing-report/SKILL.md | 3 ++- learn/SKILL.md | 3 ++- make-pdf/SKILL.md | 2 ++ office-hours/SKILL.md | 3 ++- open-gstack-browser/SKILL.md | 2 ++ pair-agent/SKILL.md | 3 ++- plan-ceo-review/SKILL.md | 3 ++- plan-design-review/SKILL.md | 3 ++- plan-devex-review/SKILL.md | 3 ++- plan-eng-review/SKILL.md | 3 ++- plan-tune/SKILL.md | 3 ++- qa-only/SKILL.md | 3 ++- qa/SKILL.md | 3 ++- retro/SKILL.md | 3 ++- review/SKILL.md | 3 ++- scrape/SKILL.md | 2 ++ .../preamble/generate-voice-directive.ts | 5 +++- setup-browser-cookies/SKILL.md | 2 ++ setup-deploy/SKILL.md | 3 ++- setup-gbrain/SKILL.md | 3 ++- ship/SKILL.md | 3 ++- skillify/SKILL.md | 3 ++- spec/SKILL.md | 3 ++- sync-gbrain/SKILL.md | 3 ++- test-audit/SKILL.md | 3 ++- test/fixtures/golden/claude-ship-SKILL.md | 3 ++- test/fixtures/golden/codex-ship-SKILL.md | 3 ++- test/fixtures/golden/factory-ship-SKILL.md | 3 ++- test/helpers/carve-guards.ts | 6 ++--- test/helpers/manual-judge-review-fixture.ts | 2 ++ test/voice-directive.test.ts | 25 +++++++++++++++++++ 56 files changed, 138 insertions(+), 47 deletions(-) diff --git a/SKILL.md b/SKILL.md index 0c23dcdbf..252e62612 100644 --- a/SKILL.md +++ b/SKILL.md @@ -98,6 +98,8 @@ Direct, concrete, builder-to-builder. Name the file, function, command, and user No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, load-bearing. Never corporate or academic. Short paragraphs. End with what to do. +Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers and quoted output stay verbatim. + The user has context you do not. Cross-model agreement is a recommendation, not a decision. The user decides. ## Completion Status Protocol diff --git a/autoplan/SKILL.md b/autoplan/SKILL.md index c94df5a77..5e5ec3af6 100644 --- a/autoplan/SKILL.md +++ b/autoplan/SKILL.md @@ -237,12 +237,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/benchmark-models/SKILL.md b/benchmark-models/SKILL.md index b0b56f3a6..5c7af4c9e 100644 --- a/benchmark-models/SKILL.md +++ b/benchmark-models/SKILL.md @@ -102,6 +102,8 @@ Direct, concrete, builder-to-builder. Name the file, function, command, and user No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, load-bearing. Never corporate or academic. Short paragraphs. End with what to do. +Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers and quoted output stay verbatim. + The user has context you do not. Cross-model agreement is a recommendation, not a decision. The user decides. ## Completion Status Protocol diff --git a/benchmark/SKILL.md b/benchmark/SKILL.md index 0b2c0e0d1..dc53eafd4 100644 --- a/benchmark/SKILL.md +++ b/benchmark/SKILL.md @@ -103,6 +103,8 @@ Direct, concrete, builder-to-builder. Name the file, function, command, and user No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, load-bearing. Never corporate or academic. Short paragraphs. End with what to do. +Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers and quoted output stay verbatim. + The user has context you do not. Cross-model agreement is a recommendation, not a decision. The user decides. ## Completion Status Protocol diff --git a/browse/SKILL.md b/browse/SKILL.md index f80939f3a..57db3e8e0 100644 --- a/browse/SKILL.md +++ b/browse/SKILL.md @@ -98,6 +98,8 @@ Direct, concrete, builder-to-builder. Name the file, function, command, and user No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, load-bearing. Never corporate or academic. Short paragraphs. End with what to do. +Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers and quoted output stay verbatim. + The user has context you do not. Cross-model agreement is a recommendation, not a decision. The user decides. ## Completion Status Protocol diff --git a/canary/SKILL.md b/canary/SKILL.md index d4c2b2157..cdb951ccb 100644 --- a/canary/SKILL.md +++ b/canary/SKILL.md @@ -218,12 +218,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/codex/SKILL.md b/codex/SKILL.md index 777ce5cb2..eb0f1b472 100644 --- a/codex/SKILL.md +++ b/codex/SKILL.md @@ -221,12 +221,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/context-restore/SKILL.md b/context-restore/SKILL.md index 8dfe9b8d4..66ff74d24 100644 --- a/context-restore/SKILL.md +++ b/context-restore/SKILL.md @@ -220,12 +220,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/context-save/SKILL.md b/context-save/SKILL.md index f1db7349d..68c13f7d2 100644 --- a/context-save/SKILL.md +++ b/context-save/SKILL.md @@ -219,12 +219,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/design-consultation/SKILL.md b/design-consultation/SKILL.md index 688369d6d..979cd2099 100644 --- a/design-consultation/SKILL.md +++ b/design-consultation/SKILL.md @@ -244,12 +244,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/design-html/SKILL.md b/design-html/SKILL.md index 491e9c957..b16ac6adc 100644 --- a/design-html/SKILL.md +++ b/design-html/SKILL.md @@ -225,12 +225,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/design-review/SKILL.md b/design-review/SKILL.md index c9d913831..697f58374 100644 --- a/design-review/SKILL.md +++ b/design-review/SKILL.md @@ -222,12 +222,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/design-shotgun/SKILL.md b/design-shotgun/SKILL.md index 6d59b14b5..735aee2d0 100644 --- a/design-shotgun/SKILL.md +++ b/design-shotgun/SKILL.md @@ -238,12 +238,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/devex-review/SKILL.md b/devex-review/SKILL.md index b1b9f5617..77e8c51de 100644 --- a/devex-review/SKILL.md +++ b/devex-review/SKILL.md @@ -224,12 +224,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/diagram/SKILL.md b/diagram/SKILL.md index 1a44c768d..990e88400 100644 --- a/diagram/SKILL.md +++ b/diagram/SKILL.md @@ -101,6 +101,8 @@ Direct, concrete, builder-to-builder. Name the file, function, command, and user No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, load-bearing. Never corporate or academic. Short paragraphs. End with what to do. +Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers and quoted output stay verbatim. + The user has context you do not. Cross-model agreement is a recommendation, not a decision. The user decides. ## Completion Status Protocol diff --git a/document-generate/SKILL.md b/document-generate/SKILL.md index 53b380dab..65682972f 100644 --- a/document-generate/SKILL.md +++ b/document-generate/SKILL.md @@ -224,12 +224,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/document-release/SKILL.md b/document-release/SKILL.md index c6cdb946a..b8cd7dd2b 100644 --- a/document-release/SKILL.md +++ b/document-release/SKILL.md @@ -222,12 +222,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/health/SKILL.md b/health/SKILL.md index 4acaef9b6..5623c066e 100644 --- a/health/SKILL.md +++ b/health/SKILL.md @@ -220,12 +220,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/investigate/SKILL.md b/investigate/SKILL.md index 597292536..bdf28b4a7 100644 --- a/investigate/SKILL.md +++ b/investigate/SKILL.md @@ -264,12 +264,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/ios-clean/SKILL.md b/ios-clean/SKILL.md index b76c5785a..65ebd5ba0 100644 --- a/ios-clean/SKILL.md +++ b/ios-clean/SKILL.md @@ -222,12 +222,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/ios-design-review/SKILL.md b/ios-design-review/SKILL.md index 3bd297c4d..caf53acf4 100644 --- a/ios-design-review/SKILL.md +++ b/ios-design-review/SKILL.md @@ -224,12 +224,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/ios-fix/SKILL.md b/ios-fix/SKILL.md index 012adc18b..ff87a17ff 100644 --- a/ios-fix/SKILL.md +++ b/ios-fix/SKILL.md @@ -225,12 +225,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/ios-qa/SKILL.md b/ios-qa/SKILL.md index 615d47f1c..84f6c0566 100644 --- a/ios-qa/SKILL.md +++ b/ios-qa/SKILL.md @@ -229,12 +229,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/ios-sync/SKILL.md b/ios-sync/SKILL.md index 274363991..f45ac524e 100644 --- a/ios-sync/SKILL.md +++ b/ios-sync/SKILL.md @@ -222,12 +222,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/land-and-deploy/SKILL.md b/land-and-deploy/SKILL.md index 398107100..ffc947d56 100644 --- a/land-and-deploy/SKILL.md +++ b/land-and-deploy/SKILL.md @@ -217,12 +217,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/landing-report/SKILL.md b/landing-report/SKILL.md index de688d27c..069a023ba 100644 --- a/landing-report/SKILL.md +++ b/landing-report/SKILL.md @@ -219,12 +219,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/learn/SKILL.md b/learn/SKILL.md index b7bdf2ec9..916d36df1 100644 --- a/learn/SKILL.md +++ b/learn/SKILL.md @@ -220,12 +220,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/make-pdf/SKILL.md b/make-pdf/SKILL.md index fb9a83200..15234412a 100644 --- a/make-pdf/SKILL.md +++ b/make-pdf/SKILL.md @@ -139,6 +139,8 @@ Direct, concrete, builder-to-builder. Name the file, function, command, and user No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, load-bearing. Never corporate or academic. Short paragraphs. End with what to do. +Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers and quoted output stay verbatim. + The user has context you do not. Cross-model agreement is a recommendation, not a decision. The user decides. ## Completion Status Protocol diff --git a/office-hours/SKILL.md b/office-hours/SKILL.md index 7b7179f7b..04bb8d147 100644 --- a/office-hours/SKILL.md +++ b/office-hours/SKILL.md @@ -265,12 +265,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/open-gstack-browser/SKILL.md b/open-gstack-browser/SKILL.md index 72b5a1916..974319239 100644 --- a/open-gstack-browser/SKILL.md +++ b/open-gstack-browser/SKILL.md @@ -100,6 +100,8 @@ Direct, concrete, builder-to-builder. Name the file, function, command, and user No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, load-bearing. Never corporate or academic. Short paragraphs. End with what to do. +Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers and quoted output stay verbatim. + The user has context you do not. Cross-model agreement is a recommendation, not a decision. The user decides. ## Completion Status Protocol diff --git a/pair-agent/SKILL.md b/pair-agent/SKILL.md index 4acea278a..95470a1d5 100644 --- a/pair-agent/SKILL.md +++ b/pair-agent/SKILL.md @@ -221,12 +221,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/plan-ceo-review/SKILL.md b/plan-ceo-review/SKILL.md index aa908bf83..5b578c4f0 100644 --- a/plan-ceo-review/SKILL.md +++ b/plan-ceo-review/SKILL.md @@ -246,12 +246,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/plan-design-review/SKILL.md b/plan-design-review/SKILL.md index b1f893e4a..bde83e878 100644 --- a/plan-design-review/SKILL.md +++ b/plan-design-review/SKILL.md @@ -246,12 +246,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/plan-devex-review/SKILL.md b/plan-devex-review/SKILL.md index 087d1e9c5..0a0e5b9c6 100644 --- a/plan-devex-review/SKILL.md +++ b/plan-devex-review/SKILL.md @@ -218,12 +218,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/plan-eng-review/SKILL.md b/plan-eng-review/SKILL.md index 0aa8cdc2b..5897d402a 100644 --- a/plan-eng-review/SKILL.md +++ b/plan-eng-review/SKILL.md @@ -262,12 +262,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - Do not add em dashes in prose you compose during the review. Existing templates, quoted text, command output, and required copied labels may contain them. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/plan-tune/SKILL.md b/plan-tune/SKILL.md index 94ff1312a..2ae8c9963 100644 --- a/plan-tune/SKILL.md +++ b/plan-tune/SKILL.md @@ -230,12 +230,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/qa-only/SKILL.md b/qa-only/SKILL.md index 126bf4a80..e37fb42f0 100644 --- a/qa-only/SKILL.md +++ b/qa-only/SKILL.md @@ -220,12 +220,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/qa/SKILL.md b/qa/SKILL.md index b9d25474b..352524525 100644 --- a/qa/SKILL.md +++ b/qa/SKILL.md @@ -224,12 +224,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/retro/SKILL.md b/retro/SKILL.md index 7ad8a1cfa..0c1933a21 100644 --- a/retro/SKILL.md +++ b/retro/SKILL.md @@ -238,12 +238,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/review/SKILL.md b/review/SKILL.md index 2a65e6385..2c7026082 100644 --- a/review/SKILL.md +++ b/review/SKILL.md @@ -222,12 +222,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/scrape/SKILL.md b/scrape/SKILL.md index fda2ef1e0..79af85129 100644 --- a/scrape/SKILL.md +++ b/scrape/SKILL.md @@ -97,6 +97,8 @@ Direct, concrete, builder-to-builder. Name the file, function, command, and user No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, load-bearing. Never corporate or academic. Short paragraphs. End with what to do. +Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers and quoted output stay verbatim. + The user has context you do not. Cross-model agreement is a recommendation, not a decision. The user decides. ## Completion Status Protocol diff --git a/scripts/resolvers/preamble/generate-voice-directive.ts b/scripts/resolvers/preamble/generate-voice-directive.ts index 4bf9a0011..13813bf4c 100644 --- a/scripts/resolvers/preamble/generate-voice-directive.ts +++ b/scripts/resolvers/preamble/generate-voice-directive.ts @@ -13,6 +13,8 @@ Direct, concrete, builder-to-builder. Name the file, function, command, and user ${emDashRule} No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, load-bearing. Never corporate or academic. Short paragraphs. End with what to do. +Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers and quoted output stay verbatim. + The user has context you do not. Cross-model agreement is a recommendation, not a decision. The user decides.`; } @@ -27,12 +29,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - ${emDashRule} No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (\`D\`, option letters, \`(recommended)\`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned.`; diff --git a/setup-browser-cookies/SKILL.md b/setup-browser-cookies/SKILL.md index 45e56c06b..5b63eb26b 100644 --- a/setup-browser-cookies/SKILL.md +++ b/setup-browser-cookies/SKILL.md @@ -96,6 +96,8 @@ Direct, concrete, builder-to-builder. Name the file, function, command, and user No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, load-bearing. Never corporate or academic. Short paragraphs. End with what to do. +Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers and quoted output stay verbatim. + The user has context you do not. Cross-model agreement is a recommendation, not a decision. The user decides. ## Completion Status Protocol diff --git a/setup-deploy/SKILL.md b/setup-deploy/SKILL.md index 6fca5618e..40ca65c88 100644 --- a/setup-deploy/SKILL.md +++ b/setup-deploy/SKILL.md @@ -221,12 +221,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/setup-gbrain/SKILL.md b/setup-gbrain/SKILL.md index e16b9517b..4dc19ec3a 100644 --- a/setup-gbrain/SKILL.md +++ b/setup-gbrain/SKILL.md @@ -220,12 +220,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/ship/SKILL.md b/ship/SKILL.md index b64ddf867..7682d6c38 100644 --- a/ship/SKILL.md +++ b/ship/SKILL.md @@ -222,12 +222,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/skillify/SKILL.md b/skillify/SKILL.md index ea2107677..ce617501d 100644 --- a/skillify/SKILL.md +++ b/skillify/SKILL.md @@ -219,12 +219,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/spec/SKILL.md b/spec/SKILL.md index 54ab08e2d..2cc1bfe49 100644 --- a/spec/SKILL.md +++ b/spec/SKILL.md @@ -220,12 +220,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/sync-gbrain/SKILL.md b/sync-gbrain/SKILL.md index d4ed3bd82..347e67206 100644 --- a/sync-gbrain/SKILL.md +++ b/sync-gbrain/SKILL.md @@ -221,12 +221,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/test-audit/SKILL.md b/test-audit/SKILL.md index 6f3c6c210..32bad98fc 100644 --- a/test-audit/SKILL.md +++ b/test-audit/SKILL.md @@ -216,12 +216,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/test/fixtures/golden/claude-ship-SKILL.md b/test/fixtures/golden/claude-ship-SKILL.md index b64ddf867..7682d6c38 100644 --- a/test/fixtures/golden/claude-ship-SKILL.md +++ b/test/fixtures/golden/claude-ship-SKILL.md @@ -222,12 +222,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/test/fixtures/golden/codex-ship-SKILL.md b/test/fixtures/golden/codex-ship-SKILL.md index 5873804e7..aed4db7ba 100644 --- a/test/fixtures/golden/codex-ship-SKILL.md +++ b/test/fixtures/golden/codex-ship-SKILL.md @@ -225,12 +225,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/test/fixtures/golden/factory-ship-SKILL.md b/test/fixtures/golden/factory-ship-SKILL.md index dae060274..2ffa52e7d 100644 --- a/test/fixtures/golden/factory-ship-SKILL.md +++ b/test/fixtures/golden/factory-ship-SKILL.md @@ -206,12 +206,13 @@ GStack voice: Garry-shaped product and engineering judgment. - Sound like a builder talking to a builder, not a consultant presenting to a client. - Never corporate, academic, PR, or hype. Avoid filler, throat-clearing, generic optimism, and founder cosplay. - No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted, furthermore, moreover, additionally, pivotal, landscape, tapestry, underscore, foster, showcase, intricate, vibrant, fundamental, significant, load-bearing. +- Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers, quoted output and question markers (`D`, option letters, `(recommended)`) stay verbatim. - The user has context you do not: domain knowledge, timing, relationships, taste. Cross-model agreement is a recommendation, not a decision. The user decides. Good: "auth.ts:47 returns undefined when the session cookie expires. Users hit a white screen. Fix: add a null check and redirect to /login. Two lines." Bad: "I've identified a potential issue in the authentication flow that may cause problems under certain conditions." -**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: AskUserQuestion decision briefs, completion-status blocks, explanations the user asked for, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. +**Bounded closer.** After completing work, report in at most a few short lines: what changed, what was skipped, what to watch. No feature tours or unrequested design notes. Exempt: decision briefs, completion-status blocks, requested explanations, and a skill's mandated report (/qa-only, /plan-*-review, /retro, /document-generate). The rule limits prose around the deliverable, never the deliverable. Good closer: "Renamed the flag in 3 files, regenerated docs, tests green. Skipped the CLI alias (unused since v1.2); watch the Windows job." Bad closer: a tour of every edit, a restatement of the plan, and three paragraphs justifying choices nobody questioned. diff --git a/test/helpers/carve-guards.ts b/test/helpers/carve-guards.ts index 9ebc58807..3df038d55 100644 --- a/test/helpers/carve-guards.ts +++ b/test/helpers/carve-guards.ts @@ -484,7 +484,7 @@ do not launch the downstream skill or open a browser.`, gateAfterStop: undefined, // operational multi-STOP skill, like ship }, behavioral: 'plan', - maxSkeletonBytes: 74_881, // Shared-code identity/skip/action rules + critical-severity validation; measured 74,493 (2026-09-17). + v1.91.12.0 merge of #2999 (review clarity repairs: await reads, research alongside dispatch, /review deadline and setup authority, findings sources) with #3002 (guarded state-root lines, plan-check checkpoints); each fit alone; measured 74,881 (2026-10-01). + maxSkeletonBytes: 74_884, // Shared-code identity/skip/action rules + critical-severity validation; measured 74,493 (2026-09-17). + v1.91.12.0 merge of #2999 (review clarity repairs: await reads, research alongside dispatch, /review deadline and setup authority, findings sources) with #3002 (guarded state-root lines, plan-check checkpoints); each fit alone; measured 74,881 (2026-10-01). + Oct 8 wave: shared voice directive bans "load-bearing" and adds the reply-language rule, offset by tightening the bounded closer (net +17 bytes per tier-2+ skill); measured 74,884 (2026-10-08). minUnionBytes: 89_000, // Phase 4 wave 1; measured union 93,357 mustContain: ['confidence', 'P1', 'P2', 'Review Army', 'adversarial'], maxSizeRatio: 1.2345, // Shared-code feature + critical-severity validation: 128,042 union bytes / 108,523 baseline = 1.1799; preserves content floors. + v1.91.12.0 merge of #2999 (above, plus plan-completion fallback intent and specialist checklist-by-path) with #3002; measured 1.1843 (2026-10-01). + v1.91.19.0 wave: verdict-form Codex callers with sandbox preflight (INV-1/B1), P0/P1 structured gate (B1b), bound-plan discovery and data-not-instructions guard (F1/D3), visible LEARNINGS failures (B5); measured 129,941 / 108,523 = 1.1974 (2026-10-03). + v1.91.18.0 (#3023) merged into the v1.91.19.0 wave; measured 130,025 / 108,523 = 1.1981 (2026-10-04). + Oct 6 fix wave: quota_exhausted preflight branch (#3051); measured 130,359 / 108,523 = 1.2012 (2026-10-06). + Oct 6 fix wave A3/CEO-12: free text reaches commands only through agent-written mktemp files (mktemp block, write rule, path rebuild and refusal at each posting, prompt and brief site); measured 131,314 / 108,523 = 1.2100 (2026-10-06). Combined Oct 6 wave head (A and B): measured 131,966 / 108,523 = 1.2160 (2026-10-06). + Oct 7 wave B3: the Codex probe runs as a command (select-model capture lines, check-sandbox/probe-model/run-with-timeout subcommands) instead of being sourced; measured 132,199 / 108,523 = 1.2182 (2026-10-07). + Oct 7 wave CEO-28/DX-11: review prompts ask for a severity per finding and design proposals use the proposal gate; measured 132,258 / 108,523 = 1.2187 (2026-10-07). + Oct 7 wave guard (CEO-20): conditional `run_in_background` request plus the background-run recovery at each foreground dispatch site; measured 132,233 / 108,523 = 1.2185 (2026-10-07). Merged with the guard area: measured 132,522 / 108,523 = 1.2211 (2026-10-07). + Oct 8 wave: the defensive-security framing and fixture summary mode reach the security specialist and the Red Team (stated once in the dispatch, referenced by the Red Team); measured 133,902 / 108,523 = 1.2339 (2026-10-08). @@ -670,7 +670,7 @@ do not launch the downstream skill or open a browser.`, }, behavioral: 'prompt', maxSkeletonBytes: 63_500, // + v2.0 {{ASIDE_SETUP}}/{{BROWSE_FALLBACK}} (replaces the browse setup block); measured 61_253 - maxSizeRatio: 1.127, // + v1.81 Aside contract + gstack-browser fallback block (1.080 on v1.91.7.0) + the shared test value bar at 8a.5 ({{TEST_VALUE_BAR:qa}}); measured 1.094 + W1 guarded state-root resolution (`eval gstack-paths; : "${GSTACK_STATE_ROOT:?…}"`) in the Context Recovery preamble, the eureka log and each state-writing bash block; measured 1.101 (2026-09-30) + v1.91.12.0 merge of #2999 (await scope/method Reads, capture --after checkpoints, browser-only empty evidence list) with #3002; measured 1.1028 (2026-10-01). + both untrusted-content marker formats in the browser fallback (W7f); measured 1.1035 (2026-10-02). Re-measured 1.1038 after the W8 probe-loop renames (2026-10-03); the cap already matches. + the annotate-every-capture and superseded rule before materialize (a ship-exploratory-late-input run published evidence that omitted older-snapshot captures); measured 1.1064 (2026-10-03). + v1.91.18.0 (#3023) merged into the v1.91.19.0 wave; measured 93,282 / 84,049 = 1.1099 (2026-10-04). + reliability follow-ups C2 (judge-named gaps after trimming the added wording: feasible 180 s Browser Quick, PROBE_DIR's source line, stop goes to the §4 report, written JSON keeps full card values; lane S's {user}/timing fields); measured 93,311 / 84,049 = 1.11020 (2026-10-04). + Oct 6 fix wave A3/CEO-12: free text reaches commands only through agent-written mktemp files (mktemp block, write rule, path rebuild and refusal at each posting, prompt and brief site); measured 94,486 / 84,049 = 1.1242 (2026-10-06). + Oct 7 wave B6: Aside rules 1, 4, 6 and 7 (offer a target-origin tab before openTab, a second sign-in wall means a tab- or URL-bound session, no early-return hint, fast [ok without the sentinel is an abort); measured 94,681 / 84,049 = 1.1265 (2026-10-07). + maxSizeRatio: 1.1272, // + v1.81 Aside contract + gstack-browser fallback block (1.080 on v1.91.7.0) + the shared test value bar at 8a.5 ({{TEST_VALUE_BAR:qa}}); measured 1.094 + W1 guarded state-root resolution (`eval gstack-paths; : "${GSTACK_STATE_ROOT:?…}"`) in the Context Recovery preamble, the eureka log and each state-writing bash block; measured 1.101 (2026-09-30) + v1.91.12.0 merge of #2999 (await scope/method Reads, capture --after checkpoints, browser-only empty evidence list) with #3002; measured 1.1028 (2026-10-01). + both untrusted-content marker formats in the browser fallback (W7f); measured 1.1035 (2026-10-02). Re-measured 1.1038 after the W8 probe-loop renames (2026-10-03); the cap already matches. + the annotate-every-capture and superseded rule before materialize (a ship-exploratory-late-input run published evidence that omitted older-snapshot captures); measured 1.1064 (2026-10-03). + v1.91.18.0 (#3023) merged into the v1.91.19.0 wave; measured 93,282 / 84,049 = 1.1099 (2026-10-04). + reliability follow-ups C2 (judge-named gaps after trimming the added wording: feasible 180 s Browser Quick, PROBE_DIR's source line, stop goes to the §4 report, written JSON keeps full card values; lane S's {user}/timing fields); measured 93,311 / 84,049 = 1.11020 (2026-10-04). + Oct 6 fix wave A3/CEO-12: free text reaches commands only through agent-written mktemp files (mktemp block, write rule, path rebuild and refusal at each posting, prompt and brief site); measured 94,486 / 84,049 = 1.1242 (2026-10-06). + Oct 7 wave B6: Aside rules 1, 4, 6 and 7 (offer a target-origin tab before openTab, a second sign-in wall means a tab- or URL-bound session, no early-return hint, fast [ok without the sentinel is an abort); measured 94,681 / 84,049 = 1.1265 (2026-10-07). + Oct 8 wave: shared voice directive bans "load-bearing" and adds the reply-language rule, offset by tightening the bounded closer (net +17 bytes per tier-2+ skill); measured 94,736 / 84,049 = 1.12715 (2026-10-08). minUnionBytes: 69_500, // measured union 70,385 // 'aside repl' pins the Aside contract; '$B goto' pins the fallback block in the always-loaded skeleton. mustContain: ['bug', 'aside repl', '$B goto', 'fix', 'Health Score Rubric', 'regression'], @@ -707,7 +707,7 @@ do not launch the downstream skill or open a browser.`, gateAfterStop: undefined, }, behavioral: 'prompt', - maxSkeletonBytes: 34_100, // + v2.0 {{ASIDE_SETUP}}/{{BROWSE_FALLBACK}} skeleton + the STOP-Read pointer; measured 29_986 + Oct 6 fix wave A3/CEO-12: free text reaches commands only through agent-written mktemp files (mktemp block, write rule, path rebuild and refusal at each posting, prompt and brief site); skeleton measured 32,532 (2026-10-06). + Oct 7 wave B6: Aside rules 1, 4, 6 and 7 (offer a target-origin tab before openTab, a second sign-in wall means a tab- or URL-bound session, no early-return hint, fast [ok without the sentinel is an abort), and the cookbook's silent-failure list and signed-in-tab recipe (the rule details live here, not in every browsing skill); skeleton measured 34,047 (2026-10-07). + maxSkeletonBytes: 34_210, // + v2.0 {{ASIDE_SETUP}}/{{BROWSE_FALLBACK}} skeleton + the STOP-Read pointer; measured 29_986 + Oct 6 fix wave A3/CEO-12: free text reaches commands only through agent-written mktemp files (mktemp block, write rule, path rebuild and refusal at each posting, prompt and brief site); skeleton measured 32,532 (2026-10-06). + Oct 7 wave B6: Aside rules 1, 4, 6 and 7 (offer a target-origin tab before openTab, a second sign-in wall means a tab- or URL-bound session, no early-return hint, fast [ok without the sentinel is an abort), and the cookbook's silent-failure list and signed-in-tab recipe (the rule details live here, not in every browsing skill); skeleton measured 34,047 (2026-10-07). + Oct 8 wave: the tier-1 voice directive bans "load-bearing" and adds the reply-language rule (tier 1 has no closer to tighten: +158 bytes); skeleton measured 34,209 (2026-10-08). minUnionBytes: 36_000, // skeleton + command-list section (14,240); measured union ~38.5 KB // 'BEGIN/END UNTRUSTED EXTERNAL' pins the untrusted-content warning in the // command reference; 'aside repl' pins the Aside contract in the skeleton. diff --git a/test/helpers/manual-judge-review-fixture.ts b/test/helpers/manual-judge-review-fixture.ts index ff4d0bd4d..1962df387 100644 --- a/test/helpers/manual-judge-review-fixture.ts +++ b/test/helpers/manual-judge-review-fixture.ts @@ -33,6 +33,8 @@ const LATER_WAVE_EDITS: Array<[string, string]> = [ // Oct 7 wave: the artifacts-sync preamble block surfaces attention lines (one line longer). ["Skill-start already ran artifacts sync. GBrain hint text (if any) says\nwhen to prefer `gbrain` over Grep. `ARTIFACTS_SYNC:` reports sync health\n(`off`, `mode=... | queue=N`, `remote-mode`, or a `gstack-brain-restore`\nhint). On an `attention:` line, tell the user in one sentence what\nit says and the command it names, then continue.\n\nThe one-time privacy stop-gate arrives as a `GSTACK_INSTRUCTION` block\nfrom skill-start when consent is pending; fire it via AskUserQuestion\nexactly as instructed.", "The skill-start output above already ran artifacts sync. Act on its lines:\nGBrain hint text (if present) tells you when to prefer `gbrain` over Grep;\n`ARTIFACTS_SYNC:` reports sync health (`off`, `mode=... | queue=N`,\n`remote-mode`, or a restore hint naming `gstack-brain-restore`).\n\nThe one-time privacy stop-gate (artifacts-sync consent) arrives as a\n`GSTACK_INSTRUCTION` block from skill-start when consent is actually pending\n\u2014 fire it via AskUserQuestion exactly as the block instructs."], + // Oct 8 wave: the tier-1 voice directive gained the reply-language rule (two lines longer). + ["Reply in the language of the user's latest message unless asked otherwise. Code, commands, paths, identifiers and quoted output stay verbatim.\n\n", ''], ]; export function approvedCookieWorkflowSource(source: string): string { diff --git a/test/voice-directive.test.ts b/test/voice-directive.test.ts index 14bfae690..d0932ae8a 100644 --- a/test/voice-directive.test.ts +++ b/test/voice-directive.test.ts @@ -1,6 +1,10 @@ import { describe, expect, test } from 'bun:test'; +import { execFileSync } from 'node:child_process'; +import { readFileSync } from 'node:fs'; +import { join } from 'node:path'; import { generateVoiceDirective } from '../scripts/resolvers/preamble/generate-voice-directive'; import { HOST_PATHS, type TemplateContext } from '../scripts/resolvers/types'; +import { between, expectMentions } from './helpers/prompt-structure'; const ctx: TemplateContext = { skillName: 'review', tmplPath: 'review/SKILL.md.tmpl', host: 'claude', paths: HOST_PATHS.claude }; const tiers: number[] = [1, 3]; @@ -11,4 +15,25 @@ describe('shared voice directive', () => { expect(banLine).toBeDefined(); expect(banLine!).toContain('load-bearing'); }); + + test.each(tiers)('tier %i replies in the language of the latest message and keeps technical text verbatim', tier => { + const voice = generateVoiceDirective(ctx, tier); + expectMentions(voice, [ + ['reply', 'language', "user's latest message", 'unless'], + ['code', 'commands', 'paths', 'identifiers', 'quoted output', 'verbatim'], + ], `tier ${tier} voice`); + if (tier >= 2) expectMentions(voice, [['question markers', '`D`', 'option letters', '`(recommended)`', 'verbatim']], 'tier 3 voice'); + }); + + test('every generated skill with a Voice section carries the reply-language rule', () => { + const root = join(import.meta.dir, '..'); + const skills = execFileSync('git', ['ls-files', 'SKILL.md', '*/SKILL.md'], { cwd: root, encoding: 'utf8', timeout: 10_000 }).split('\n').filter(Boolean); + const voiced = skills.filter(file => readFileSync(join(root, file), 'utf8').includes('\n## Voice\n')); + expect(voiced.length).toBeGreaterThan(40); + const missing = voiced.filter(file => { + const voice = between(readFileSync(join(root, file), 'utf8'), '\n## Voice\n', /\n## /).toLowerCase(); + return !(voice.includes('language') && voice.includes('latest message') && voice.includes('verbatim')); + }); + expect(missing).toEqual([]); + }); });