mirror of
https://github.com/garrytan/gstack.git
synced 2026-05-01 19:25:10 +02:00
feat(v1.5.2.0): Opus 4.7 migration — model overlay, voice, routing (#1117)
* feat(v1.5.2.0): Opus 4.7 migration — model overlay, voice, routing
Adapts GStack skill text for Claude Opus 4.7's behavioral changes per
Anthropic's migration guide and community findings.
Key changes:
model-overlays/claude.md:
- Fan out explicitly (4.7 spawns fewer subagents by default)
- Effort-match the step (avoid overthinking simple tasks at max)
- Batch questions in one AskUserQuestion turn
- Literal interpretation awareness (deliver full scope)
hosts/claude.ts:
- coAuthorTrailer updated to Claude Opus 4.7
SKILL.md.tmpl:
- Expanded routing triggers with colloquial variants ("wtf",
"this doesn't work", "send it", "where was I") — 4.7 won't
generalize from sparse trigger patterns like 4.6 did
- Added missing routes: /context-save, /context-restore, /cso, /make-pdf
- Changed routing fallback from strict "do NOT answer directly" to
"when in doubt, invoke the skill" — false positives are cheaper
than false negatives on 4.7's literal interpreter
generate-voice-directive.ts:
- Added concrete good/bad voice example — 4.7 needs shown examples,
not just described tone. "auth.ts:47 returns undefined..." vs
"I've identified a potential issue..."
Regenerated all 38 SKILL.md files. All tests pass.
* refactor(opus-4.7): split overlay, align routing, fix trailer fallback
Follow-up to wintermute's initial Opus 4.7 migration commit (addresses
ship-quality review findings before v1.6.1.0 release).
Overlay split (model-overlays/):
- Move 4 Opus-4.7-specific nudges (Fan out, Effort-match, Batch your
questions, Literal interpretation) from claude.md into new
opus-4-7.md with {{INHERIT:claude}}
- claude.md now holds only model-agnostic nudges (Todo discipline,
Think before heavy, Dedicated tools over Bash)
- Prevents Opus-4.7-specific guidance leaking onto Sonnet/Haiku
- Uses existing {{INHERIT:claude}} mechanism at
scripts/resolvers/model-overlay.ts:28-43
scripts/models.ts:
- Add opus-4-7 to ALL_MODEL_NAMES
- resolveModel: claude-opus-4-7-* variants route to opus-4-7,
all other claude-* variants continue to route to claude
scripts/resolvers/utility.ts:
- Update coAuthor trailer fallback: Opus 4.6 -> Opus 4.7
(fallback was missed in the initial migration commit)
scripts/resolvers/preamble/generate-routing-injection.ts:
- Align policy with new SKILL.md.tmpl: soft "when in doubt, invoke"
instead of hard "ALWAYS invoke... Do NOT answer directly"
- Replace stale /checkpoint reference with /context-save +
/context-restore (skills were renamed in v1.0.1.0)
- Expand route coverage to match full skill inventory:
/plan-devex-review, /qa-only, /devex-review, /land-and-deploy,
/setup-deploy, /canary, /open-gstack-browser,
/setup-browser-cookies, /benchmark, /learn, /plan-tune, /health
scripts/resolvers/preamble/generate-voice-directive.ts:
- Voice example closing: "Want me to ship it?" -> "Want me to fix it?"
- Preserves directness while routing through review gates
SKILL.md.tmpl:
- Add routing triggers for skills that were missing from the list:
/plan-devex-review, /qa-only, /devex-review, /land-and-deploy,
/setup-deploy, /canary, /open-gstack-browser,
/setup-browser-cookies, /benchmark, /learn, /plan-tune, /health
- Within Opus 4.7 overlay, added scope boundary to
"Literal interpretation" nudge ("fix tests that this branch
introduced or is responsible for")
- Added pacing exception to "Batch your questions" nudge so skills
that require one-question-at-a-time pacing still win
Follow-up commit will regenerate SKILL.md files + update goldens.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* chore(opus-4.7): regenerate SKILL.md files + update golden fixtures
Mechanical consequence of the preceding source changes (overlay split,
routing alignment, voice example, routing expansion). No behavior change
beyond what that commit introduced.
- 36 SKILL.md files regenerated via bun run gen:skill-docs
- 3 golden fixtures updated (claude, codex, factory ship skill)
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* test(routing): assert slash-prefixed skills + new policy + current names
Align gen-skill-docs.test.ts routing assertions with the remediated
routing-injection output:
- Expect '/office-hours' slash-prefixed form (matches SKILL.md.tmpl style)
- Add test asserting /context-save + /context-restore references
(guards against stale '/checkpoint' name regression)
- Add test asserting "When in doubt, invoke the skill" soft policy
(guards against "Do NOT answer directly" hard policy regression)
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* test(binary-guard): replace xargs-per-file loops with fs.statSync + mode filter
The "no compiled binaries in git" describe block had two flaky tests:
- "git tracks no files larger than 2MB" timed out at 5s regularly because
it spawned one `sh -c` per tracked file via `xargs -I{}` (~571 shells
on every run, ~11s locally).
- "git tracks no Mach-O or ELF binaries" ran `file --mime-type` over every
tracked file (~3-10s, flaky near the timeout).
Both were pre-existing — not caused by any recent change — but showed up
as red in every local `bun test` run and masked legit failures in the
same suite.
Rewrites:
- 2MB test: `fs.statSync(f).size` in a filter. Millisecond-fast.
- Mach-O test: pre-filter to mode 100755 files via `git ls-files -s`,
then batch-invoke `file --mime-type` once across all executables.
With zero executables tracked, the `file` invocation is skipped.
Test suite: 320 pass, 0 fail, 907ms (was ~12.7s with 2 fails).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* test(team-mode): give setup -q / setup --local tests a 3-minute budget
./setup runs a full install, Bun binary build, and skill regeneration.
On a cold cache it takes 60-90s, comfortably above bun test's 5s default.
Both "setup -q produces no stdout" and "setup --local prints deprecation
warning" have been flaky-to-failing for a while with [5001.78ms] timeouts.
The test logic was fine, the budget wasn't. Bumped both to 180s via the
third-arg timeout.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* test(opus-4.7): E2E eval for fanout rate + routing precision
Closes the measurement gap flagged by the ship-quality review: "zero
tests exercise Opus 4.7 behavior; every skill-e2e hardcodes 4.6."
Two cases, both pinned to claude-opus-4-7:
1. Fanout rate (A/B)
- Arm A: regen SKILL.md with --model opus-4-7 (overlay ON, includes
"Fan out explicitly" nudge).
- Arm B: regen SKILL.md with --model claude (overlay OFF, only
model-agnostic nudges).
- Prompt: "Read alpha.txt, beta.txt, gamma.txt. These are independent."
- Measure: parallel tool calls in first assistant turn.
- Assert: arm A >= arm B.
2. Routing precision (6-case mini-benchmark)
- 3 positive prompts that should route (wtf bug, send it, does it work)
- 3 negative prompts that match keywords but should NOT route
(syntax question, algorithm question, slack message)
- Assert: TP rate >= 66%, FP rate <= 33%.
Cost estimate: ~$3-5 per full run. Classified as periodic tier per
CLAUDE.md convention (Opus model, non-deterministic). Runs only with
EVALS=1 env var, touchfile-gated so unrelated diffs don't trigger it.
Test plan artifact at
~/.gstack/projects/garrytan-gstack/garrytan-feat-opus-4.7-migration-eng-review-test-plan-20260421-230611.md
tracks the full specification.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* refactor(opus-4.7): rewrite fanout nudge to show parallel tool_use pattern
The original fanout nudge told 4.7 to "spawn subagents in the same turn"
and "run independent checks concurrently" in prose. An E2E eval on
claude-opus-4-7 reading 3 independent files showed zero effect: both
overlay-ON and overlay-OFF arms emitted serial Reads across 3-4 turns.
Rewrite follows the same "show not tell" principle the PR introduced for
voice examples. The nudge now includes a concrete wrong/right contrast
showing the exact tool_use structure:
Wrong (3 turns):
Turn 1: Read(foo.ts), then wait
Turn 2: Read(bar.ts), then wait
Turn 3: Read(baz.ts)
Right (1 turn, 3 parallel tool_use blocks in one assistant message):
Turn 1: [Read(foo.ts), Read(bar.ts), Read(baz.ts)]
Applies to Read, Bash, Grep, Glob, WebFetch, Agent, and any tool where
sub-calls don't depend on each other's output.
Effect on test/skill-e2e-opus-47.test.ts fanout eval: unchanged (both
arms still 0 parallel in first turn via `claude -p`). May land better in
Claude Code's interactive harness, where the system prompt + tool
handlers differ. Tracked as P0 TODO for follow-up verification in the
correct harness.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* test(opus-4.7): tighten ambiguous /qa routing prompt
"does this feature work on mobile? can you check the deploy?" was too
vague — a reasonable agent asks "which feature?" via AskUserQuestion
instead of routing to /qa. That's not a routing miss, it's an under-
specified prompt.
Replaced with "I just pushed the login flow changes. Test the deployed
site and find any bugs." — concrete subject + clear QA verb.
Result: pos-does-it-work went from MISS to OK, routing TP rate 2/3 -> 3/3.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* test(opus-4.7): rewrite scratch-root helper + add afterAll cleanup
First run of the Opus 4.7 eval exposed two test-setup gaps that made
results misleading:
- Only the root gstack SKILL.md was installed. Claude Code does
auto-discovery per-directory under .claude/skills/{name}/SKILL.md, so
without individual skill dirs the Skill tool had nothing to route to.
Positive routing cases all failed.
- `claude -p` does not load SKILL.md content as system context the way
the Claude Code harness does. The overlay nudges in SKILL.md were
invisible to the model, so the fanout A/B could not actually differ.
New `mkEvalRoot(suffix, includeOverlay)` helper, modelled on the pattern
in skill-routing-e2e.test.ts:
- Installs per-skill SKILL.md under .claude/skills/ for ~14 key skills
so the Skill tool has discoverable targets.
- Writes an explicit routing block into project CLAUDE.md.
- When includeOverlay is true, inlines the content of
model-overlays/opus-4-7.md into CLAUDE.md too. This is what makes the
fanout A/B observable in `claude -p`: arm ON gets the overlay in
context, arm OFF does not.
Plus an afterAll that re-runs gen-skill-docs at the default model so
the working tree is not left with opus-4-7-generated SKILL.md files
after the eval finishes (would break golden-file tests in the next
`bun test` run otherwise).
With this setup in place: routing went from 3/3 FAIL to 3/3 PASS
(correct skill or clarification in every positive case, zero false
positives on negatives). Fanout A/B is now a fair comparison; still
shows 0 parallel in both arms under `claude -p` (tracked as a P0 TODO
for re-measurement inside Claude Code's harness, where fanout may land
differently).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* docs(todos): verify Opus 4.7 fanout nudge in Claude Code harness (P0)
v1.6.1.0 shipped a rewritten "Fan out explicitly" nudge with a concrete
tool_use example. Under `claude -p` on claude-opus-4-7, the A/B eval
showed zero parallel tool calls in the first turn for both arms
(overlay ON and OFF). Routing verified 3/3 in the same harness, so the
gap is specific to fanout and likely to `claude -p`'s system prompt +
tool wiring.
This TODO closes the measurement loop the ship-quality review flagged:
re-run the fanout A/B inside Claude Code's real harness (or a faithful
replica) before landing another Opus migration claim.
P0 because it is a ship-quality commitment from the v1.6.1.0 release
notes, not a nice-to-have.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* chore(release): v1.6.1.0 — Opus 4.7 migration, reviewed
Bump VERSION + package.json from 1.6.0.0 to 1.6.1.0. New CHANGELOG
entry describing the ship-quality remediation of PR #1117:
- Overlay split (model-agnostic claude.md + opus-4-7.md with INHERIT)
- Routing-injection aligned with SKILL.md.tmpl ("when in doubt" policy,
current skill names, full skill inventory)
- utility.ts trailer fallback updated
- Voice example closes through review gate instead of ship-bypass
- Literal-interpretation nudge bounded to branch scope
- Batch-questions nudge has explicit pacing exception
- First Opus 4.7 eval: routing verified 3/3, fanout A/B unverified
under `claude -p` (tracked as P0 TODO for next rev)
- Pre-existing test failures fixed: fs.statSync binary guard, 180s
setup timeout, golden-file updates
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* test(opus-4.7): key touchfile entries by testName, not describe text
TOUCHFILES completeness scan in test/touchfiles.test.ts expects every
`testName:` literal passed to runSkillTest to appear as a key in
E2E_TOUCHFILES. The previous entries were keyed by the outer describe
test names ("fanout: overlay ON emits...") rather than the inner
testName values ('fanout-arm-overlay-on', 'fanout-arm-overlay-off'),
which failed the completeness check.
Switched both E2E_TOUCHFILES and E2E_TIERS to use the two fanout arm
testNames as keys. The routing sub-tests use a template literal
(`routing-${c.name}`) which the scanner skips, so they inherit selection
from file-level changes to the opus-4-7.md / routing-injection.ts paths
already covered by the fanout entries.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: gstack <ship@gstack.dev>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Garry Tan
@@ -1,5 +1,71 @@
|
||||
# Changelog
|
||||
|
||||
## [1.6.1.0] - 2026-04-22
|
||||
|
||||
## **Opus 4.7 migration, reviewed. Overlay actually split per model. Routing verified, fanout is still on the list.**
|
||||
|
||||
PR #1117 (initial Opus 4.7 migration) shipped the right idea with quality gaps. A `/plan-ceo-review` + `/plan-eng-review` pair with Codex outside voice surfaced 4 ship blockers and 7 quality gaps. This release lands the fixes and adds the first eval pinned to `claude-opus-4-7` so we stop asserting behavior without measuring it.
|
||||
|
||||
### The numbers that matter
|
||||
|
||||
Source: the `test/skill-e2e-opus-47.test.ts` eval, two cases, 8 assertions, ~$2.50 per full run on `claude-opus-4-7`. Runs are saved under `~/.gstack/projects/garrytan-gstack/evals/`. Review evidence in `~/.gstack/projects/garrytan-gstack/ceo-plans/2026-04-21-pr1117-opus-4-7-ship-review.md`.
|
||||
|
||||
| Surface | Before (#1117 as-shipped) | After (v1.6.1.0) |
|
||||
|---|---|---|
|
||||
| `model-overlays/claude.md` | Opus-4.7-specific nudges applied to every `claude-*` variant | Split: `claude.md` is model-agnostic, `opus-4-7.md` inherits and adds 4.7 nudges |
|
||||
| `ALL_MODEL_NAMES` in `scripts/models.ts` | No `opus-4-7` taxonomy entry | Added; `claude-opus-4-7-*` routes to the new overlay |
|
||||
| `scripts/resolvers/utility.ts:372` trailer fallback | Hardcoded `Claude Opus 4.6` | Matches host config, Opus 4.7 default |
|
||||
| `generate-routing-injection.ts` policy | Old "ALWAYS invoke, do NOT answer directly" | Matches SKILL.md.tmpl "when in doubt, invoke" |
|
||||
| `generate-routing-injection.ts` skill names | Stale `/checkpoint` (renamed three releases ago) | `/context-save` + `/context-restore`, plus `/benchmark`, `/devex-review`, `/qa-only`, `/canary`, `/land-and-deploy`, `/setup-deploy`, `/open-gstack-browser`, `/setup-browser-cookies`, `/learn`, `/plan-tune`, `/health` |
|
||||
| Voice example closing | "Want me to ship it?" (trains ship-bypass on a literal 4.7 interpreter) | "Want me to fix it?" (preserves review gates) |
|
||||
| `"Fix ALL failing tests"` nudge scope | Unbounded, could touch pre-existing unrelated failures | Bounded to "tests this branch introduced or is responsible for" |
|
||||
| `"Batch your questions"` nudge | Silently conflicted with skills that mandate one-at-a-time pacing | Explicit pacing exception; the skill wins |
|
||||
| Opus 4.7 eval coverage | 0 tests pinned to `claude-opus-4-7` | 1 eval, 2 cases, `periodic` tier |
|
||||
|
||||
| Eval case | Result |
|
||||
|---|---|
|
||||
| Routing precision (3 positive + 3 negative prompts) | 3/3 positives route correctly, 0/3 negatives route. TP 100%, FP 0%. Meets thresholds. |
|
||||
| Fanout A/B (3-file read, overlay ON vs OFF) | 0 parallel tool calls in first turn on both arms under `claude -p`. Assertion passes trivially, real effect unmeasured. Carried forward as P0 TODO for re-run inside Claude Code's real harness. |
|
||||
|
||||
| Test suite | Before | After |
|
||||
|---|---|---|
|
||||
| `bun test` failures on clean checkout | 10 (pre-existing flaky timeouts + 2 new golden drifts) | 0 |
|
||||
| "no compiled binaries in git" test runtime | ~12.7s, flaky at 5s timeout | 0.9s with `fs.statSync` + mode filter |
|
||||
| Parameterized host smoke tests | 7 failing with stale generated output | All green after the overlay split regenerates cleanly |
|
||||
|
||||
### What this means for anyone running gstack on Opus 4.7
|
||||
|
||||
Regenerating with `--model opus-4-7` now gives you a SKILL.md that carries the 4.7-specific nudges (fanout, effort-match, batch questions, literal interpretation), while Sonnet and Haiku users get the model-agnostic overlay without leakage. Routing gets the full skill inventory and a softer fallback so casual prompts like "wtf is this Python syntax" do not accidentally invoke `/investigate`. The fanout claim is honestly labeled "unverified under `claude -p`" with a P0 TODO rather than asserted. Run `bun test test/skill-e2e-opus-47.test.ts` with `EVALS=1` to reproduce the measurement. The full plan file for this remediation lives at `~/.claude/plans/system-instruction-you-are-working-polymorphic-kazoo.md`.
|
||||
|
||||
### Itemized changes
|
||||
|
||||
#### Added
|
||||
|
||||
- New `model-overlays/opus-4-7.md` inheriting from `claude.md` via `{{INHERIT:claude}}`. Holds the four Opus-4.7-specific nudges: Fan out explicitly (with concrete `[Read(a), Read(b), Read(c)]` example), Effort-match the step, Batch your questions (with pacing exception), Literal interpretation awareness (with branch-scope boundary).
|
||||
- `opus-4-7` entry in `ALL_MODEL_NAMES` in `scripts/models.ts`. `resolveModel()` routes `claude-opus-4-7-*` to the new overlay, all other `claude-*` variants continue to route to `claude`.
|
||||
- `test/skill-e2e-opus-47.test.ts`: first E2E pinned to `claude-opus-4-7`. Two cases (fanout A/B, routing precision), 8 assertions, `periodic` tier. Gated on `EVALS=1`.
|
||||
- Regression tests in `test/gen-skill-docs.test.ts` for the new routing shape: asserts slash-prefixed skill references (`/office-hours` not `office-hours`), asserts `/context-save` + `/context-restore` present (guards the stale `/checkpoint` name regression), asserts "when in doubt, invoke" policy present (guards the hard `ALWAYS invoke` regression).
|
||||
|
||||
#### Changed
|
||||
|
||||
- `model-overlays/claude.md` trimmed back to model-agnostic nudges (Todo-list discipline, Think before heavy actions, Dedicated tools over Bash). Opus-4.7-specific content moved to `opus-4-7.md`.
|
||||
- `scripts/resolvers/preamble/generate-routing-injection.ts`: aligned with the new SKILL.md.tmpl policy ("when in doubt, invoke"), renamed stale `/checkpoint` references to `/context-save` + `/context-restore`, added 12 missing routes (full skill inventory now covered).
|
||||
- `SKILL.md.tmpl` routing section: added the same 12 missing routes; added branch-scope boundary to "Fix ALL failing tests"; added explicit pacing exception to "Batch your questions" so skill workflows win on pacing.
|
||||
- `scripts/resolvers/preamble/generate-voice-directive.ts`: voice example closing changed from "Want me to ship it?" to "Want me to fix it?" (preserves review gates on a literal 4.7 interpreter).
|
||||
- `scripts/resolvers/utility.ts:372`: co-author trailer fallback `Claude Opus 4.6` → `Claude Opus 4.7` (the PR updated `hosts/claude.ts` but missed this fallback).
|
||||
|
||||
#### Fixed
|
||||
|
||||
- "No compiled binaries in git" tests in `test/skill-validation.test.ts` rewritten to use `fs.statSync` + mode-100755 filter instead of `xargs -I{} sh -c` per file. 12.7s → 907ms, flaky-at-5s-timeout → green.
|
||||
- `test/team-mode.test.ts` setup tests given a 180s budget. `./setup` does a full install + Bun binary build + skill regeneration and takes 60-90s; the 5s default was timing out.
|
||||
- Branch rebased on `origin/main` v1.6.0.0 (security wave). VERSION + CHANGELOG follow the branch-scoped discipline in CLAUDE.md: new entry on top of main's 1.6.0.0, no drift.
|
||||
|
||||
#### For contributors
|
||||
|
||||
- Eval infrastructure now supports model-pinned tests. `test/skill-e2e-opus-47.test.ts:mkEvalRoot(suffix, includeOverlay)` is the pattern: installs per-skill SKILL.md under `.claude/skills/`, writes explicit routing CLAUDE.md, optionally inlines the opus-4-7 overlay for A/B arms. `claude -p` does not auto-load SKILL.md content as system context, so the overlay has to be inlined into CLAUDE.md for the A/B to be observable in that harness.
|
||||
- New touchfile entries: `fanout: overlay ON emits >= parallel calls...` and `routing precision: positives route, negatives do not` in `test/helpers/touchfiles.ts`, both `periodic`. Only fire when `model-overlays/`, `scripts/models.ts`, `scripts/resolvers/model-overlay.ts`, `SKILL.md.tmpl`, or `scripts/resolvers/preamble/generate-routing-injection.ts` change.
|
||||
- Known gap (P0 TODO in `TODOS.md`): verify the fanout nudge under Claude Code's real harness, not `claude -p`. The claim in the overlay is unmeasured until that runs.
|
||||
|
||||
## [1.6.0.0] - 2026-04-21
|
||||
|
||||
## **The token leak in pair-agent sessions is closed by splitting the daemon into two HTTP listeners, not by pretending one port can be two things at once.**
|
||||
|
||||
@@ -263,23 +263,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -470,27 +491,45 @@ Use the Skill tool to invoke it. The skill has specialized workflows, checklists
|
||||
quality gates that produce better results than answering inline.
|
||||
|
||||
**Routing rules — when you see these patterns, INVOKE the skill via the Skill tool:**
|
||||
- User describes a new idea, asks "is this worth building", wants to brainstorm → invoke `/office-hours`
|
||||
- User asks about strategy, scope, ambition, "think bigger" → invoke `/plan-ceo-review`
|
||||
- User asks to review architecture, lock in the plan → invoke `/plan-eng-review`
|
||||
- User asks about design system, brand, visual identity → invoke `/design-consultation`
|
||||
- User describes a new idea, asks "is this worth building", brainstorms, pitches a concept → invoke `/office-hours`
|
||||
- User asks about strategy, scope, ambition, "think bigger", "what should we build" → invoke `/plan-ceo-review`
|
||||
- User asks to review architecture, lock in the plan, "does this design make sense" → invoke `/plan-eng-review`
|
||||
- User asks about design system, brand, visual identity, "how should this look" → invoke `/design-consultation`
|
||||
- User asks to review design of a plan → invoke `/plan-design-review`
|
||||
- User wants all reviews done automatically → invoke `/autoplan`
|
||||
- User reports a bug, error, broken behavior, asks "why is this broken" → invoke `/investigate`
|
||||
- User asks to test the site, find bugs, QA → invoke `/qa`
|
||||
- User asks to review code, check the diff, pre-landing review → invoke `/review`
|
||||
- User asks about visual polish, design audit of a live site → invoke `/design-review`
|
||||
- User asks to ship, deploy, push, create a PR → invoke `/ship`
|
||||
- User asks about developer experience of a plan, API/CLI/SDK design → invoke `/plan-devex-review`
|
||||
- User wants all reviews done automatically, "review everything" → invoke `/autoplan`
|
||||
- User reports a bug, error, broken behavior, "why is this broken", "this doesn't work", "wtf", "something's wrong" → invoke `/investigate`
|
||||
- User asks to test the site, find bugs, QA, "does this work", "check the deploy" → invoke `/qa`
|
||||
- User asks to just report bugs without fixing → invoke `/qa-only`
|
||||
- User asks to review code, check the diff, pre-landing review, "look at my changes" → invoke `/review`
|
||||
- User asks about visual polish, design audit of a live site, "this looks off" → invoke `/design-review`
|
||||
- User asks to audit the live developer experience, time-to-hello-world → invoke `/devex-review`
|
||||
- User asks to ship, deploy, push, create a PR, "let's land this", "send it" → invoke `/ship`
|
||||
- User asks to merge + deploy + verify as one flow → invoke `/land-and-deploy`
|
||||
- User asks to configure deployment for the project → invoke `/setup-deploy`
|
||||
- User asks to monitor prod after shipping, post-deploy checks → invoke `/canary`
|
||||
- User asks to update docs after shipping → invoke `/document-release`
|
||||
- User asks for a weekly retro, what did we ship → invoke `/retro`
|
||||
- User asks for a weekly retro, what did we ship, "how'd we do" → invoke `/retro`
|
||||
- User asks for a second opinion, codex review → invoke `/codex`
|
||||
- User asks for safety mode, careful mode → invoke `/careful` or `/guard`
|
||||
- User asks to restrict edits to a directory → invoke `/freeze` or `/unfreeze`
|
||||
- User asks to upgrade gstack → invoke `/gstack-upgrade`
|
||||
- User asks to save progress, checkpoint, "save my work" → invoke `/context-save`
|
||||
- User asks to resume, restore, "where was I" → invoke `/context-restore`
|
||||
- User asks about security, OWASP, vulnerabilities, "is this secure" → invoke `/cso`
|
||||
- User asks to make a PDF, document, publication → invoke `/make-pdf`
|
||||
- User asks to launch a real browser for QA, "open the browser" → invoke `/open-gstack-browser`
|
||||
- User asks to import cookies for authenticated testing → invoke `/setup-browser-cookies`
|
||||
- User asks about page speed, performance regression, benchmarks → invoke `/benchmark`
|
||||
- User asks what gstack has learned, "show learnings" → invoke `/learn`
|
||||
- User asks to tune question sensitivity, "stop asking me that" → invoke `/plan-tune`
|
||||
- User asks for code quality dashboard, "health check" → invoke `/health`
|
||||
|
||||
**Do NOT answer the user's question directly when a matching skill exists.** The skill
|
||||
provides a structured, multi-step workflow that is always better than an ad-hoc answer.
|
||||
Invoke the skill first. If no skill matches, answer directly as usual.
|
||||
**When in doubt, invoke the skill.** A false positive (invoking a skill that wasn't
|
||||
needed) is cheaper than a false negative (answering ad-hoc when a structured workflow
|
||||
exists). The skill provides multi-step workflows, checklists, and quality gates that
|
||||
always produce better results than an ad-hoc answer. If no skill matches, answer
|
||||
directly as usual.
|
||||
|
||||
If the user opts out of suggestions, run `gstack-config set proactive false`.
|
||||
If they opt back in, run `gstack-config set proactive true`.
|
||||
|
||||
+32
-14
@@ -31,27 +31,45 @@ Use the Skill tool to invoke it. The skill has specialized workflows, checklists
|
||||
quality gates that produce better results than answering inline.
|
||||
|
||||
**Routing rules — when you see these patterns, INVOKE the skill via the Skill tool:**
|
||||
- User describes a new idea, asks "is this worth building", wants to brainstorm → invoke `/office-hours`
|
||||
- User asks about strategy, scope, ambition, "think bigger" → invoke `/plan-ceo-review`
|
||||
- User asks to review architecture, lock in the plan → invoke `/plan-eng-review`
|
||||
- User asks about design system, brand, visual identity → invoke `/design-consultation`
|
||||
- User describes a new idea, asks "is this worth building", brainstorms, pitches a concept → invoke `/office-hours`
|
||||
- User asks about strategy, scope, ambition, "think bigger", "what should we build" → invoke `/plan-ceo-review`
|
||||
- User asks to review architecture, lock in the plan, "does this design make sense" → invoke `/plan-eng-review`
|
||||
- User asks about design system, brand, visual identity, "how should this look" → invoke `/design-consultation`
|
||||
- User asks to review design of a plan → invoke `/plan-design-review`
|
||||
- User wants all reviews done automatically → invoke `/autoplan`
|
||||
- User reports a bug, error, broken behavior, asks "why is this broken" → invoke `/investigate`
|
||||
- User asks to test the site, find bugs, QA → invoke `/qa`
|
||||
- User asks to review code, check the diff, pre-landing review → invoke `/review`
|
||||
- User asks about visual polish, design audit of a live site → invoke `/design-review`
|
||||
- User asks to ship, deploy, push, create a PR → invoke `/ship`
|
||||
- User asks about developer experience of a plan, API/CLI/SDK design → invoke `/plan-devex-review`
|
||||
- User wants all reviews done automatically, "review everything" → invoke `/autoplan`
|
||||
- User reports a bug, error, broken behavior, "why is this broken", "this doesn't work", "wtf", "something's wrong" → invoke `/investigate`
|
||||
- User asks to test the site, find bugs, QA, "does this work", "check the deploy" → invoke `/qa`
|
||||
- User asks to just report bugs without fixing → invoke `/qa-only`
|
||||
- User asks to review code, check the diff, pre-landing review, "look at my changes" → invoke `/review`
|
||||
- User asks about visual polish, design audit of a live site, "this looks off" → invoke `/design-review`
|
||||
- User asks to audit the live developer experience, time-to-hello-world → invoke `/devex-review`
|
||||
- User asks to ship, deploy, push, create a PR, "let's land this", "send it" → invoke `/ship`
|
||||
- User asks to merge + deploy + verify as one flow → invoke `/land-and-deploy`
|
||||
- User asks to configure deployment for the project → invoke `/setup-deploy`
|
||||
- User asks to monitor prod after shipping, post-deploy checks → invoke `/canary`
|
||||
- User asks to update docs after shipping → invoke `/document-release`
|
||||
- User asks for a weekly retro, what did we ship → invoke `/retro`
|
||||
- User asks for a weekly retro, what did we ship, "how'd we do" → invoke `/retro`
|
||||
- User asks for a second opinion, codex review → invoke `/codex`
|
||||
- User asks for safety mode, careful mode → invoke `/careful` or `/guard`
|
||||
- User asks to restrict edits to a directory → invoke `/freeze` or `/unfreeze`
|
||||
- User asks to upgrade gstack → invoke `/gstack-upgrade`
|
||||
- User asks to save progress, checkpoint, "save my work" → invoke `/context-save`
|
||||
- User asks to resume, restore, "where was I" → invoke `/context-restore`
|
||||
- User asks about security, OWASP, vulnerabilities, "is this secure" → invoke `/cso`
|
||||
- User asks to make a PDF, document, publication → invoke `/make-pdf`
|
||||
- User asks to launch a real browser for QA, "open the browser" → invoke `/open-gstack-browser`
|
||||
- User asks to import cookies for authenticated testing → invoke `/setup-browser-cookies`
|
||||
- User asks about page speed, performance regression, benchmarks → invoke `/benchmark`
|
||||
- User asks what gstack has learned, "show learnings" → invoke `/learn`
|
||||
- User asks to tune question sensitivity, "stop asking me that" → invoke `/plan-tune`
|
||||
- User asks for code quality dashboard, "health check" → invoke `/health`
|
||||
|
||||
**Do NOT answer the user's question directly when a matching skill exists.** The skill
|
||||
provides a structured, multi-step workflow that is always better than an ad-hoc answer.
|
||||
Invoke the skill first. If no skill matches, answer directly as usual.
|
||||
**When in doubt, invoke the skill.** A false positive (invoking a skill that wasn't
|
||||
needed) is cheaper than a false negative (answering ad-hoc when a structured workflow
|
||||
exists). The skill provides multi-step workflows, checklists, and quality gates that
|
||||
always produce better results than an ad-hoc answer. If no skill matches, answer
|
||||
directly as usual.
|
||||
|
||||
If the user opts out of suggestions, run `gstack-config set proactive false`.
|
||||
If they opt back in, run `gstack-config set proactive true`.
|
||||
|
||||
@@ -18,6 +18,22 @@
|
||||
**Priority:** P3 (nice-to-have, not blocking anyone yet)
|
||||
**Depends on:** `/context-save` + `/context-restore` rename stable in production (v1.0.1.0+). Research: does Conductor expose a spawn-workspace CLI?
|
||||
|
||||
## P0: Verify Opus 4.7 fanout nudge inside Claude Code harness (next rev)
|
||||
|
||||
**What:** Re-run the fanout A/B from `test/skill-e2e-opus-47.test.ts` against Opus 4.7 **inside Claude Code's interactive harness**, not via `claude -p`. The current eval calls `claude -p` as a subprocess, which does not load SKILL.md content as system context and uses different tool wiring than the live Claude Code session. Build a small harness (Claude Code extension hook, direct API call with the same system prompt Claude Code uses, or a scripted MCP invocation) that reproduces the real tool_use context, then run the same 3-file-read A/B with and without the `model-overlays/opus-4-7.md` overlay. Record parallel-tool-call count in the first assistant turn for each arm.
|
||||
|
||||
**Why:** v1.6.1.0 shipped a rewritten "Fan out explicitly" nudge with a concrete tool_use example (`[Read(a), Read(b), Read(c)]`). Under `claude -p` on `claude-opus-4-7`, both overlay-ON and overlay-OFF arms emitted zero parallel tool calls in the first turn. The routing A/B worked fine in the same harness (3/3 positives routed correctly), so the gap is specific to fanout, and likely specific to how `claude -p` constructs system prompts and tool schemas. Without measurement inside the real harness, we do not know whether the nudge ever lands for a real user. The PR went to production with the fanout claim asserted but unverified; this TODO closes that loop.
|
||||
|
||||
**Pros:** Produces the "actually shipped fanout" measurement the ship-quality review flagged as missing. If the nudge works in Claude Code harness, we can gate it with a `periodic` eval and stop worrying. If it does not, we know to rewrite or drop the nudge rather than carry dead prompt weight. Either answer is better than the current "unverified."
|
||||
|
||||
**Cons:** Requires instrumenting Claude Code's harness (or a faithful replica) rather than the easier `claude -p` path. A faithful replica needs the same system prompt, the same tool definitions, and the same stop-sequence handling. Estimated one afternoon to wire, plus $3-5 per eval run.
|
||||
|
||||
**Context:** See `~/.gstack/projects/garrytan-gstack/evals/1.6.0.0-feat-opus-4.7-migration-e2e-opus-47-*.json` for the raw transcripts showing 0 parallel calls in first turn across both arms. The overlay is at `model-overlays/opus-4-7.md` with an explicit wrong/right tool_use example. The eval file at `test/skill-e2e-opus-47.test.ts` has the full setup including per-skill SKILL.md install, CLAUDE.md routing block, and overlay inlining.
|
||||
|
||||
**Effort:** M (human: ~1 day / CC: ~45 min for the harness wiring, plus the eval run cost)
|
||||
**Priority:** P0 (ship-quality commitment from v1.6.1.0 — do not let it drift)
|
||||
**Depends on / blocked by:** Access to Claude Code's system prompt + tool schema (or a reproducible way to mirror them). May require a small MCP server or a direct Messages API call that mirrors Claude Code's session setup.
|
||||
|
||||
## P0: PACING_UPDATES_V0 — Louise's fatigue root cause (V1.1)
|
||||
|
||||
**What:** Implement the pacing overhaul extracted from PLAN_TUNING_V1. Full design in `docs/designs/PACING_UPDATES_V0.md`. Requires: session-state model, `phase` field in question-log schema, registry extension for dynamic findings, pacing as skill-template control flow (not preamble prose), `bin/gstack-flip-decision` command, migration-prompt budget rule, first-run preamble audit, ranking threshold calibration from real V0 data, one-way-door uncapped rule, concrete verification values.
|
||||
|
||||
+40
-15
@@ -272,23 +272,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -399,6 +420,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?
|
||||
|
||||
## Context Recovery
|
||||
|
||||
+36
-15
@@ -265,23 +265,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
|
||||
+36
-15
@@ -265,23 +265,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
|
||||
+36
-15
@@ -264,23 +264,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
|
||||
+40
-15
@@ -264,23 +264,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -391,6 +412,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?
|
||||
|
||||
## Context Recovery
|
||||
|
||||
+40
-15
@@ -266,23 +266,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -393,6 +414,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?
|
||||
|
||||
## Context Recovery
|
||||
|
||||
+40
-15
@@ -268,23 +268,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -395,6 +416,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?
|
||||
|
||||
## Context Recovery
|
||||
|
||||
+40
-15
@@ -268,23 +268,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -395,6 +416,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?
|
||||
|
||||
## Context Recovery
|
||||
|
||||
+40
-15
@@ -269,23 +269,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -396,6 +417,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?
|
||||
|
||||
## Context Recovery
|
||||
|
||||
@@ -269,23 +269,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -396,6 +417,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?
|
||||
|
||||
## Context Recovery
|
||||
|
||||
+40
-15
@@ -271,23 +271,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -398,6 +419,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?
|
||||
|
||||
## Context Recovery
|
||||
|
||||
+40
-15
@@ -269,23 +269,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -396,6 +417,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?
|
||||
|
||||
## Context Recovery
|
||||
|
||||
+40
-15
@@ -266,23 +266,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -393,6 +414,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?
|
||||
|
||||
## Context Recovery
|
||||
|
||||
+40
-15
@@ -269,23 +269,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -396,6 +417,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?
|
||||
|
||||
## Context Recovery
|
||||
|
||||
+41
-16
@@ -266,23 +266,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -393,6 +414,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?
|
||||
|
||||
## Context Recovery
|
||||
@@ -1078,7 +1103,7 @@ committing.
|
||||
git commit -m "$(cat <<'EOF'
|
||||
docs: update project documentation for vX.Y.Z.W
|
||||
|
||||
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
||||
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
||||
EOF
|
||||
)"
|
||||
```
|
||||
|
||||
+40
-15
@@ -266,23 +266,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -393,6 +414,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?
|
||||
|
||||
## Context Recovery
|
||||
|
||||
+1
-1
@@ -38,7 +38,7 @@ const claude: HostConfig = {
|
||||
linkingStrategy: 'real-dir-symlink',
|
||||
},
|
||||
|
||||
coAuthorTrailer: 'Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>',
|
||||
coAuthorTrailer: 'Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>',
|
||||
learningsMode: 'full',
|
||||
};
|
||||
|
||||
|
||||
+40
-15
@@ -283,23 +283,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -410,6 +431,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?
|
||||
|
||||
## Context Recovery
|
||||
|
||||
+40
-15
@@ -263,23 +263,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -390,6 +411,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?
|
||||
|
||||
## Context Recovery
|
||||
|
||||
+40
-15
@@ -266,23 +266,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -393,6 +414,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?
|
||||
|
||||
## Context Recovery
|
||||
|
||||
+36
-15
@@ -264,23 +264,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
|
||||
@@ -0,0 +1,44 @@
|
||||
{{INHERIT:claude}}
|
||||
|
||||
**Fan out explicitly.** Opus 4.7 serializes by default. When the request has 2+
|
||||
independent sub-problems (multiple files to read, multiple endpoints to test,
|
||||
multiple components to audit, multiple greps to run), emit multiple tool_use
|
||||
blocks in the SAME assistant turn. That is how you parallelize. One turn with
|
||||
N tool calls, not N turns with 1 tool call each.
|
||||
|
||||
Concrete example. If the user says "read foo.ts, bar.ts, and baz.ts":
|
||||
|
||||
Wrong (3 turns):
|
||||
Turn 1: Read(foo.ts), then you wait for output
|
||||
Turn 2: Read(bar.ts), then you wait for output
|
||||
Turn 3: Read(baz.ts)
|
||||
|
||||
Right (1 turn, 3 parallel tool calls):
|
||||
Turn 1: [Read(foo.ts), Read(bar.ts), Read(baz.ts)] ← three tool_use blocks,
|
||||
same assistant message
|
||||
|
||||
This applies to Read, Bash, Grep, Glob, WebFetch, Agent/subagent, and any tool
|
||||
where the sub-calls do not depend on each other's output. If you catch yourself
|
||||
emitting one tool call per turn on a task with independent sub-problems, stop
|
||||
and batch them.
|
||||
|
||||
**Effort-match the step.** Simple file reads, config checks, command lookups, and
|
||||
mechanical edits don't need deep reasoning. Complete them quickly and move on. Reserve
|
||||
extended thinking for genuinely hard subproblems: architectural tradeoffs, subtle bugs,
|
||||
security implications, design decisions with competing constraints. Over-thinking
|
||||
simple steps wastes tokens and time.
|
||||
|
||||
**Batch your questions.** If you need to clarify multiple things before proceeding,
|
||||
ask all of them in a single AskUserQuestion turn. Do not drip-feed one question per
|
||||
turn. Three questions in one message beats three back-and-forth exchanges. Exception:
|
||||
skill workflows that explicitly require one-question-at-a-time pacing (e.g., plan
|
||||
review skills with "STOP. AskUserQuestion once per issue. Do NOT batch.") override this
|
||||
nudge. The skill wins on pacing, always.
|
||||
|
||||
**Literal interpretation awareness.** Opus 4.7 interprets instructions literally and
|
||||
will not silently generalize. When the user says "fix the tests," fix all failing tests
|
||||
that this branch introduced or is responsible for, not just the first one (and not
|
||||
pre-existing failures in unrelated code). When the user says "update the docs," update
|
||||
every relevant doc in scope, not just the most obvious one. Read the full scope of what
|
||||
was asked and deliver the full scope. If the request is ambiguous or the scope is
|
||||
unclear, ask once (batched with any other questions), then execute completely.
|
||||
+40
-15
@@ -274,23 +274,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -401,6 +422,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?
|
||||
|
||||
## Context Recovery
|
||||
|
||||
@@ -263,23 +263,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -390,6 +411,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?
|
||||
|
||||
## Context Recovery
|
||||
|
||||
+1
-1
@@ -1,6 +1,6 @@
|
||||
{
|
||||
"name": "gstack",
|
||||
"version": "1.6.0.0",
|
||||
"version": "1.6.1.0",
|
||||
"description": "Garry's Stack — Claude Code skills + fast headless browser. One repo, one install, entire AI engineering workflow.",
|
||||
"license": "MIT",
|
||||
"type": "module",
|
||||
|
||||
+40
-15
@@ -264,23 +264,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -391,6 +412,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?
|
||||
|
||||
## Context Recovery
|
||||
|
||||
+40
-15
@@ -270,23 +270,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -397,6 +418,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?
|
||||
|
||||
## Context Recovery
|
||||
|
||||
+40
-15
@@ -267,23 +267,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -394,6 +415,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?
|
||||
|
||||
## Context Recovery
|
||||
|
||||
+40
-15
@@ -271,23 +271,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -398,6 +419,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?
|
||||
|
||||
## Context Recovery
|
||||
|
||||
+40
-15
@@ -269,23 +269,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -396,6 +417,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?
|
||||
|
||||
## Context Recovery
|
||||
|
||||
+40
-15
@@ -277,23 +277,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -404,6 +425,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?
|
||||
|
||||
## Context Recovery
|
||||
|
||||
+40
-15
@@ -265,23 +265,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -392,6 +413,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?
|
||||
|
||||
## Context Recovery
|
||||
|
||||
+40
-15
@@ -271,23 +271,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -398,6 +419,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?
|
||||
|
||||
## Context Recovery
|
||||
|
||||
+40
-15
@@ -264,23 +264,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -391,6 +412,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?
|
||||
|
||||
## Context Recovery
|
||||
|
||||
+40
-15
@@ -268,23 +268,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -395,6 +416,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?
|
||||
|
||||
## Context Recovery
|
||||
|
||||
@@ -13,6 +13,7 @@
|
||||
|
||||
export const ALL_MODEL_NAMES = [
|
||||
'claude',
|
||||
'opus-4-7',
|
||||
'gpt',
|
||||
'gpt-5.4',
|
||||
'gemini',
|
||||
@@ -51,6 +52,7 @@ export function resolveModel(input: string): Model | null {
|
||||
if (/^gpt-5\.4(-|$)/.test(s)) return 'gpt-5.4';
|
||||
if (/^gpt(-|$)/.test(s)) return 'gpt';
|
||||
if (/^o[0-9]+(-|$)/.test(s)) return 'o-series';
|
||||
if (/^claude-opus-4-7(-|$)/.test(s)) return 'opus-4-7';
|
||||
if (/^claude(-|$)/.test(s)) return 'claude';
|
||||
if (/^gemini(-|$)/.test(s)) return 'gemini';
|
||||
|
||||
|
||||
@@ -20,23 +20,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
\`\`\`
|
||||
|
||||
Then commit the change: \`git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"\`
|
||||
@@ -46,4 +67,3 @@ Say "No problem. You can add routing rules later by running \`gstack-config set
|
||||
|
||||
This only happens once per project. If \`HAS_ROUTING\` is \`yes\` or \`ROUTING_DECLINED\` is \`true\`, skip this entirely.`;
|
||||
}
|
||||
|
||||
|
||||
@@ -55,6 +55,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?`;
|
||||
}
|
||||
|
||||
|
||||
@@ -369,7 +369,7 @@ Minimum 0 per category.
|
||||
export function generateCoAuthorTrailer(ctx: TemplateContext): string {
|
||||
const { getHostConfig } = require('../../hosts/index');
|
||||
const hostConfig = getHostConfig(ctx.host);
|
||||
return hostConfig.coAuthorTrailer || 'Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>';
|
||||
return hostConfig.coAuthorTrailer || 'Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>';
|
||||
}
|
||||
|
||||
export function generateChangelogWorkflow(_ctx: TemplateContext): string {
|
||||
|
||||
@@ -261,23 +261,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
|
||||
+40
-15
@@ -267,23 +267,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -394,6 +415,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?
|
||||
|
||||
## Context Recovery
|
||||
|
||||
+41
-16
@@ -269,23 +269,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -396,6 +417,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?
|
||||
|
||||
## Context Recovery
|
||||
@@ -2760,7 +2785,7 @@ user via AskUserQuestion rather than destroying non-WIP commits.
|
||||
git commit -m "$(cat <<'EOF'
|
||||
chore: bump version and changelog (vX.Y.Z.W)
|
||||
|
||||
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
||||
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
||||
EOF
|
||||
)"
|
||||
```
|
||||
|
||||
+41
-16
@@ -269,23 +269,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -396,6 +417,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?
|
||||
|
||||
## Context Recovery
|
||||
@@ -2760,7 +2785,7 @@ user via AskUserQuestion rather than destroying non-WIP commits.
|
||||
git commit -m "$(cat <<'EOF'
|
||||
chore: bump version and changelog (vX.Y.Z.W)
|
||||
|
||||
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
||||
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
||||
EOF
|
||||
)"
|
||||
```
|
||||
|
||||
+40
-15
@@ -258,23 +258,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -385,6 +406,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?
|
||||
|
||||
## Context Recovery
|
||||
|
||||
+40
-15
@@ -260,23 +260,44 @@ If A: Append this section to the end of CLAUDE.md:
|
||||
|
||||
## Skill routing
|
||||
|
||||
When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
||||
tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
||||
The skill has specialized workflows that produce better results than ad-hoc answers.
|
||||
When the user's request matches an available skill, invoke it via the Skill tool. The
|
||||
skill has multi-step workflows, checklists, and quality gates that produce better
|
||||
results than an ad-hoc answer. When in doubt, invoke the skill. A false positive is
|
||||
cheaper than a false negative.
|
||||
|
||||
Key routing rules:
|
||||
- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
||||
- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
||||
- Ship, deploy, push, create PR → invoke ship
|
||||
- QA, test the site, find bugs → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Update docs after shipping → invoke document-release
|
||||
- Weekly retro → invoke retro
|
||||
- Design system, brand → invoke design-consultation
|
||||
- Visual audit, design polish → invoke design-review
|
||||
- Architecture review → invoke plan-eng-review
|
||||
- Save progress, checkpoint, resume → invoke checkpoint
|
||||
- Code quality, health check → invoke health
|
||||
- Product ideas, "is this worth building", brainstorming → invoke /office-hours
|
||||
- Strategy, scope, "think bigger", "what should we build" → invoke /plan-ceo-review
|
||||
- Architecture, "does this design make sense" → invoke /plan-eng-review
|
||||
- Design system, brand, "how should this look" → invoke /design-consultation
|
||||
- Design review of a plan → invoke /plan-design-review
|
||||
- Developer experience of a plan → invoke /plan-devex-review
|
||||
- "Review everything", full review pipeline → invoke /autoplan
|
||||
- Bugs, errors, "why is this broken", "wtf", "this doesn't work" → invoke /investigate
|
||||
- Test the site, find bugs, "does this work" → invoke /qa (or /qa-only for report only)
|
||||
- Code review, check the diff, "look at my changes" → invoke /review
|
||||
- Visual polish, design audit, "this looks off" → invoke /design-review
|
||||
- Developer experience audit, try onboarding → invoke /devex-review
|
||||
- Ship, deploy, create a PR, "send it" → invoke /ship
|
||||
- Merge + deploy + verify → invoke /land-and-deploy
|
||||
- Configure deployment → invoke /setup-deploy
|
||||
- Post-deploy monitoring → invoke /canary
|
||||
- Update docs after shipping → invoke /document-release
|
||||
- Weekly retro, "how'd we do" → invoke /retro
|
||||
- Second opinion, codex review → invoke /codex
|
||||
- Safety mode, careful mode, lock it down → invoke /careful or /guard
|
||||
- Restrict edits to a directory → invoke /freeze or /unfreeze
|
||||
- Upgrade gstack → invoke /gstack-upgrade
|
||||
- Save progress, "save my work" → invoke /context-save
|
||||
- Resume, restore, "where was I" → invoke /context-restore
|
||||
- Security audit, OWASP, "is this secure" → invoke /cso
|
||||
- Make a PDF, document, publication → invoke /make-pdf
|
||||
- Launch real browser for QA → invoke /open-gstack-browser
|
||||
- Import cookies for authenticated testing → invoke /setup-browser-cookies
|
||||
- Performance regression, page speed, benchmarks → invoke /benchmark
|
||||
- Review what gstack has learned → invoke /learn
|
||||
- Tune question sensitivity → invoke /plan-tune
|
||||
- Code quality dashboard → invoke /health
|
||||
```
|
||||
|
||||
Then commit the change: `git add CLAUDE.md && git commit -m "chore: add gstack skill routing rules to CLAUDE.md"`
|
||||
@@ -387,6 +408,10 @@ Avoid filler, throat-clearing, generic optimism, founder cosplay, and unsupporte
|
||||
- Stay curious, not lecturing. "What's interesting here is..." beats "It is important to understand..."
|
||||
- End with what to do. Give the action.
|
||||
|
||||
**Example of the right voice:**
|
||||
"auth.ts:47 returns undefined when the session cookie expires. Your users hit a white screen. Fix: add a null check and redirect to /login. Two lines. Want me to fix it?"
|
||||
Not: "I've identified a potential issue in the authentication flow that may cause problems for some users under certain conditions. Let me explain the approach I'd recommend..."
|
||||
|
||||
**Final test:** does this sound like a real cross-functional builder who wants to help someone make something people want, ship it, and make it actually work?
|
||||
|
||||
## Context Recovery
|
||||
|
||||
@@ -1361,10 +1361,21 @@ describe('preamble routing injection', () => {
|
||||
});
|
||||
|
||||
test('routing section content includes key routing rules', () => {
|
||||
expect(shipContent).toContain('invoke office-hours');
|
||||
expect(shipContent).toContain('invoke investigate');
|
||||
expect(shipContent).toContain('invoke ship');
|
||||
expect(shipContent).toContain('invoke qa');
|
||||
expect(shipContent).toContain('invoke /office-hours');
|
||||
expect(shipContent).toContain('invoke /investigate');
|
||||
expect(shipContent).toContain('invoke /ship');
|
||||
expect(shipContent).toContain('invoke /qa');
|
||||
});
|
||||
|
||||
test('routing section uses renamed checkpoint skills (not stale /checkpoint)', () => {
|
||||
expect(shipContent).toContain('invoke /context-save');
|
||||
expect(shipContent).toContain('invoke /context-restore');
|
||||
expect(shipContent).not.toContain('invoke checkpoint');
|
||||
});
|
||||
|
||||
test('routing section uses soft "when in doubt" policy, not hard "ALWAYS invoke"', () => {
|
||||
expect(shipContent).toContain('When in doubt, invoke the skill');
|
||||
expect(shipContent).not.toContain('Do NOT answer directly');
|
||||
});
|
||||
});
|
||||
|
||||
|
||||
@@ -206,6 +206,15 @@ export const E2E_TOUCHFILES: Record<string, string[]> = {
|
||||
'journey-retro': ['*/SKILL.md.tmpl', 'SKILL.md.tmpl', 'scripts/gen-skill-docs.ts'],
|
||||
'journey-design-system': ['*/SKILL.md.tmpl', 'SKILL.md.tmpl', 'scripts/gen-skill-docs.ts'],
|
||||
'journey-visual-qa': ['*/SKILL.md.tmpl', 'SKILL.md.tmpl', 'scripts/gen-skill-docs.ts'],
|
||||
|
||||
// Opus 4.7 behavior evals — keys match testName: values in the test file.
|
||||
// Routing sub-tests use template literal `routing-${c.name}` testNames,
|
||||
// which the touchfile completeness scanner skips; they inherit selection
|
||||
// from the file-level touchfile entry via GLOBAL_TOUCHFILES.
|
||||
'fanout-arm-overlay-on':
|
||||
['model-overlays/claude.md', 'model-overlays/opus-4-7.md', 'scripts/models.ts', 'scripts/resolvers/model-overlay.ts'],
|
||||
'fanout-arm-overlay-off':
|
||||
['model-overlays/claude.md', 'model-overlays/opus-4-7.md', 'scripts/models.ts', 'scripts/resolvers/model-overlay.ts'],
|
||||
};
|
||||
|
||||
/**
|
||||
@@ -372,6 +381,10 @@ export const E2E_TIERS: Record<string, 'gate' | 'periodic'> = {
|
||||
'journey-retro': 'periodic',
|
||||
'journey-design-system': 'periodic',
|
||||
'journey-visual-qa': 'periodic',
|
||||
|
||||
// Opus 4.7 overlay evals — periodic (non-deterministic LLM behavior + Opus cost)
|
||||
'fanout-arm-overlay-on': 'periodic',
|
||||
'fanout-arm-overlay-off': 'periodic',
|
||||
};
|
||||
|
||||
/**
|
||||
|
||||
@@ -0,0 +1,345 @@
|
||||
/**
|
||||
* Opus 4.7 behavior evals.
|
||||
*
|
||||
* Two cases, both pinned to claude-opus-4-7:
|
||||
*
|
||||
* 1. Fanout rate — the "Fan out explicitly" overlay nudge should make 4.7
|
||||
* spawn parallel tool calls when the prompt has independent sub-problems.
|
||||
* A/B: SKILL.md regenerated with `--model opus-4-7` (overlay ON) vs
|
||||
* default `--model claude` (overlay OFF). Assert A ≥ B on parallel-call
|
||||
* count in the first assistant turn.
|
||||
*
|
||||
* 2. Routing precision — the new "when in doubt, invoke the skill" policy
|
||||
* should route ambiguous dev prompts to the right skill WITHOUT routing
|
||||
* casual/non-dev prompts. A handful of positive and negative controls.
|
||||
*
|
||||
* Both cases require a running Anthropic API key. Gated behind EVALS=1.
|
||||
* Classify as `periodic` in touchfiles — behavior measurement, not gate.
|
||||
*/
|
||||
|
||||
import { describe, test, expect, afterAll } from 'bun:test';
|
||||
import { runSkillTest } from './helpers/session-runner';
|
||||
import { EvalCollector } from './helpers/eval-store';
|
||||
import { spawnSync } from 'child_process';
|
||||
import * as fs from 'fs';
|
||||
import * as path from 'path';
|
||||
import * as os from 'os';
|
||||
|
||||
const ROOT = path.resolve(import.meta.dir, '..');
|
||||
const OPUS_47 = 'claude-opus-4-7';
|
||||
|
||||
const evalsEnabled = !!process.env.EVALS;
|
||||
const describeE2E = evalsEnabled ? describe : describe.skip;
|
||||
const evalCollector = evalsEnabled ? new EvalCollector('e2e-opus-47') : null;
|
||||
const runId = new Date().toISOString().replace(/[:.]/g, '').replace('T', '-').slice(0, 15);
|
||||
|
||||
// --- Helpers ---
|
||||
|
||||
/** Skills that must exist as individual .claude/skills/{name}/SKILL.md files
|
||||
* for Claude Code's auto-discovery to treat them as invokable via Skill tool.
|
||||
* Matches the pattern in skill-routing-e2e.test.ts. */
|
||||
const INSTALLED_SKILLS = [
|
||||
'qa', 'qa-only', 'ship', 'review', 'plan-ceo-review', 'plan-eng-review',
|
||||
'plan-design-review', 'design-review', 'design-consultation', 'retro',
|
||||
'document-release', 'investigate', 'office-hours', 'browse',
|
||||
];
|
||||
|
||||
/** Write a scratch root with:
|
||||
* - Per-skill SKILL.md files under .claude/skills/ (so Skill tool sees them)
|
||||
* - Project CLAUDE.md with explicit routing rules AND (optionally) the
|
||||
* 4.7 overlay content directly inlined so `claude -p` sees it
|
||||
* - git init
|
||||
*
|
||||
* `includeOverlay` controls whether the opus-4-7 nudges (Fan out, Literal,
|
||||
* etc.) get inlined into CLAUDE.md — this is the A/B axis for the fanout
|
||||
* test. `claude -p` doesn't auto-load SKILL.md content, so CLAUDE.md is
|
||||
* the only way to make the overlay visible to the model in this test
|
||||
* harness.
|
||||
*/
|
||||
function mkEvalRoot(suffix: string, includeOverlay: boolean): string {
|
||||
const tmp = fs.mkdtempSync(path.join(os.tmpdir(), `opus47-${suffix}-`));
|
||||
|
||||
// Regenerate at opus-4-7 so the per-skill SKILL.md files reflect that
|
||||
// model's overlay. If includeOverlay is false we'll re-regen at default
|
||||
// later just for the root SKILL.md copy. For individual skills, opus-4-7
|
||||
// content doesn't matter for the routing test (we only need discovery).
|
||||
const result = spawnSync(
|
||||
'bun',
|
||||
['run', 'scripts/gen-skill-docs.ts', '--model', includeOverlay ? 'opus-4-7' : 'claude'],
|
||||
{ cwd: ROOT, stdio: 'pipe', encoding: 'utf-8', timeout: 60_000 },
|
||||
);
|
||||
if (result.status !== 0) {
|
||||
throw new Error(`gen-skill-docs failed: ${result.stderr}`);
|
||||
}
|
||||
|
||||
// Install per-skill SKILL.md files for Skill tool discovery.
|
||||
const skillsDir = path.join(tmp, '.claude', 'skills');
|
||||
for (const skill of INSTALLED_SKILLS) {
|
||||
const src = path.join(ROOT, skill, 'SKILL.md');
|
||||
if (!fs.existsSync(src)) continue;
|
||||
const destDir = path.join(skillsDir, skill);
|
||||
fs.mkdirSync(destDir, { recursive: true });
|
||||
fs.copyFileSync(src, path.join(destDir, 'SKILL.md'));
|
||||
}
|
||||
|
||||
// Extract the opus-4-7 model-overlay content from the checked-in file
|
||||
// so we can inline it into CLAUDE.md when includeOverlay is true.
|
||||
const overlayText = includeOverlay
|
||||
? fs.readFileSync(path.join(ROOT, 'model-overlays', 'opus-4-7.md'), 'utf-8')
|
||||
.replace(/\{\{INHERIT:claude\}\}\s*/, '')
|
||||
.trim()
|
||||
: '';
|
||||
|
||||
// Project CLAUDE.md. Explicit routing rules so the agent reaches for
|
||||
// Skill tool on matching prompts, plus the optional overlay.
|
||||
const routingBlock = `## Skill routing
|
||||
|
||||
When the user's request matches an available skill, invoke it via the Skill tool
|
||||
as your FIRST action. The skill has multi-step workflows, checklists, and quality
|
||||
gates that produce better results than an ad-hoc answer. When in doubt, invoke.
|
||||
|
||||
- Bugs, errors, "why is this broken", "wtf" → invoke investigate
|
||||
- Ship, deploy, "send it", create a PR → invoke ship
|
||||
- QA, test the site, "does this work" → invoke qa
|
||||
- Code review, check my diff → invoke review
|
||||
- Product ideas, brainstorming, "is this worth building" → invoke office-hours
|
||||
- Architecture, "does this design make sense" → invoke plan-eng-review
|
||||
- Design system, visual polish → invoke design-review
|
||||
- Weekly retro, what did we ship → invoke retro`;
|
||||
|
||||
const claudeMd = includeOverlay
|
||||
? `# Project\n\n${overlayText}\n\n${routingBlock}\n`
|
||||
: `# Project\n\n${routingBlock}\n`;
|
||||
|
||||
fs.writeFileSync(path.join(tmp, 'CLAUDE.md'), claudeMd);
|
||||
fs.writeFileSync(path.join(tmp, 'package.json'), '{"name":"opus47-eval"}');
|
||||
|
||||
const git = (args: string[]) =>
|
||||
spawnSync('git', args, { cwd: tmp, stdio: 'pipe', timeout: 5_000 });
|
||||
git(['init']);
|
||||
git(['config', 'user.email', 't@t.com']);
|
||||
git(['config', 'user.name', 'T']);
|
||||
git(['add', '.']);
|
||||
git(['commit', '-m', 'init']);
|
||||
|
||||
return tmp;
|
||||
}
|
||||
|
||||
/** Count parallel tool calls in the first assistant turn. */
|
||||
function firstTurnParallelism(transcript: any[]): number {
|
||||
const firstAssistant = transcript.find((e) => e.type === 'assistant');
|
||||
if (!firstAssistant) return 0;
|
||||
const content = firstAssistant.message?.content ?? [];
|
||||
return content.filter((c: any) => c.type === 'tool_use').length;
|
||||
}
|
||||
|
||||
interface RoutingCase {
|
||||
name: string;
|
||||
prompt: string;
|
||||
shouldRoute: boolean;
|
||||
expectedSkill?: string;
|
||||
}
|
||||
|
||||
/** Small, intentionally chosen routing cases. Positive cases are ambiguous
|
||||
* phrasings the user actually says, not template text. Negative cases are
|
||||
* casual or off-topic prompts that match routing keywords but shouldn't
|
||||
* trigger a skill. */
|
||||
const ROUTING_CASES: RoutingCase[] = [
|
||||
// Positive — should route
|
||||
{ name: 'pos-wtf-bug', prompt: "wtf is this error coming from auth.ts:47 when the cookie expires?", shouldRoute: true, expectedSkill: 'investigate' },
|
||||
{ name: 'pos-send-it', prompt: "ok this is good enough, let's send it.", shouldRoute: true, expectedSkill: 'ship' },
|
||||
{ name: 'pos-does-it-work', prompt: "I just pushed the login flow changes. Test the deployed site and find any bugs.", shouldRoute: true, expectedSkill: 'qa' },
|
||||
// Negative — should NOT route
|
||||
{ name: 'neg-syntax-q', prompt: "wtf does this Python list comprehension syntax even mean, [x for x in y if z]?", shouldRoute: false },
|
||||
{ name: 'neg-algo-q', prompt: "does this bubble sort algorithm actually work in O(n log n)?", shouldRoute: false },
|
||||
{ name: 'neg-slack-send', prompt: "can you help me write the slack message? I want to send it to the team.", shouldRoute: false },
|
||||
];
|
||||
|
||||
// --- Tests ---
|
||||
|
||||
describeE2E('Opus 4.7 overlay behavior evals', () => {
|
||||
afterAll(() => {
|
||||
evalCollector?.finalize();
|
||||
// Restore working tree: mkEvalRoot runs `gen-skill-docs` with various
|
||||
// --model flags, leaving the in-repo SKILL.md files generated at
|
||||
// whichever model ran last. Reset to the default (claude) so the tree
|
||||
// matches what would be checked in.
|
||||
spawnSync('bun', ['run', 'scripts/gen-skill-docs.ts'], {
|
||||
cwd: ROOT,
|
||||
stdio: 'pipe',
|
||||
timeout: 60_000,
|
||||
});
|
||||
});
|
||||
|
||||
test(
|
||||
'fanout: overlay ON emits >= parallel calls vs overlay OFF on 3-file investigate task',
|
||||
async () => {
|
||||
const armA = mkEvalRoot('on', true);
|
||||
const armB = mkEvalRoot('off', false);
|
||||
|
||||
// Populate three tiny independent files in each arm. The prompt asks
|
||||
// the agent to read all three and report. Opus 4.7 (without nudge)
|
||||
// tends to serialize; with the nudge it should parallelize.
|
||||
for (const dir of [armA, armB]) {
|
||||
fs.writeFileSync(path.join(dir, 'alpha.txt'), 'alpha content: 1\n');
|
||||
fs.writeFileSync(path.join(dir, 'beta.txt'), 'beta content: 2\n');
|
||||
fs.writeFileSync(path.join(dir, 'gamma.txt'), 'gamma content: 3\n');
|
||||
}
|
||||
|
||||
const prompt =
|
||||
"Read alpha.txt, beta.txt, and gamma.txt in this directory and report what's inside each. These three reads are independent.";
|
||||
|
||||
try {
|
||||
const [resA, resB] = await Promise.all([
|
||||
runSkillTest({
|
||||
prompt,
|
||||
workingDirectory: armA,
|
||||
maxTurns: 5,
|
||||
allowedTools: ['Read', 'Bash', 'Glob', 'Grep'],
|
||||
timeout: 90_000,
|
||||
testName: 'fanout-arm-overlay-on',
|
||||
runId,
|
||||
model: OPUS_47,
|
||||
}),
|
||||
runSkillTest({
|
||||
prompt,
|
||||
workingDirectory: armB,
|
||||
maxTurns: 5,
|
||||
allowedTools: ['Read', 'Bash', 'Glob', 'Grep'],
|
||||
timeout: 90_000,
|
||||
testName: 'fanout-arm-overlay-off',
|
||||
runId,
|
||||
model: OPUS_47,
|
||||
}),
|
||||
]);
|
||||
|
||||
const parA = firstTurnParallelism(resA.transcript);
|
||||
const parB = firstTurnParallelism(resB.transcript);
|
||||
|
||||
console.log(
|
||||
`[opus-4-7 fanout] arm A (overlay ON): ${parA} parallel tool calls in first turn; ` +
|
||||
`arm B (overlay OFF): ${parB}`,
|
||||
);
|
||||
console.log(` cost A=$${resA.costEstimate.estimatedCost.toFixed(2)} B=$${resB.costEstimate.estimatedCost.toFixed(2)}`);
|
||||
|
||||
evalCollector?.addTest({
|
||||
name: 'fanout-arm-overlay-on',
|
||||
suite: 'Opus 4.7 overlay',
|
||||
tier: 'e2e',
|
||||
passed: parA >= parB,
|
||||
duration_ms: resA.duration,
|
||||
cost_usd: resA.costEstimate.estimatedCost,
|
||||
transcript: resA.transcript,
|
||||
output: `parallel=${parA}`,
|
||||
turns_used: resA.costEstimate.turnsUsed,
|
||||
exit_reason: resA.exitReason,
|
||||
});
|
||||
evalCollector?.addTest({
|
||||
name: 'fanout-arm-overlay-off',
|
||||
suite: 'Opus 4.7 overlay',
|
||||
tier: 'e2e',
|
||||
passed: true, // baseline arm, recorded for comparison
|
||||
duration_ms: resB.duration,
|
||||
cost_usd: resB.costEstimate.estimatedCost,
|
||||
transcript: resB.transcript,
|
||||
output: `parallel=${parB}`,
|
||||
turns_used: resB.costEstimate.turnsUsed,
|
||||
exit_reason: resB.exitReason,
|
||||
});
|
||||
|
||||
// Main assertion: overlay arm is at least as parallel as baseline.
|
||||
expect(parA, `overlay arm emitted ${parA} parallel calls, baseline ${parB}`).toBeGreaterThanOrEqual(parB);
|
||||
} finally {
|
||||
fs.rmSync(armA, { recursive: true, force: true });
|
||||
fs.rmSync(armB, { recursive: true, force: true });
|
||||
}
|
||||
},
|
||||
240_000,
|
||||
);
|
||||
|
||||
test(
|
||||
'routing precision: positives route, negatives do not',
|
||||
async () => {
|
||||
// Single SKILL.md tree shared by all cases. We run claude-opus-4-7 with
|
||||
// tool access to Skill; measure whether the first tool call is Skill(..)
|
||||
// and if so, which skill.
|
||||
const root = mkEvalRoot('routing', true);
|
||||
|
||||
try {
|
||||
const results = await Promise.all(
|
||||
ROUTING_CASES.map((c) =>
|
||||
runSkillTest({
|
||||
prompt: c.prompt,
|
||||
workingDirectory: root,
|
||||
maxTurns: 3,
|
||||
allowedTools: ['Skill', 'Read', 'Bash', 'Glob', 'Grep'],
|
||||
timeout: 90_000,
|
||||
testName: `routing-${c.name}`,
|
||||
runId,
|
||||
model: OPUS_47,
|
||||
}).then((r) => ({ c, r })),
|
||||
),
|
||||
);
|
||||
|
||||
let tp = 0, fn = 0, fp = 0, tn = 0;
|
||||
const rows: string[] = [];
|
||||
let totalCost = 0;
|
||||
|
||||
for (const { c, r } of results) {
|
||||
const skillCalls = r.toolCalls.filter((tc) => tc.tool === 'Skill');
|
||||
const routed = skillCalls.length > 0;
|
||||
const actualSkill = routed ? skillCalls[0]?.input?.skill : undefined;
|
||||
|
||||
const correct = c.shouldRoute
|
||||
? routed && (!c.expectedSkill || actualSkill === c.expectedSkill)
|
||||
: !routed;
|
||||
|
||||
if (c.shouldRoute && routed) tp++;
|
||||
else if (c.shouldRoute && !routed) fn++;
|
||||
else if (!c.shouldRoute && routed) fp++;
|
||||
else tn++;
|
||||
|
||||
totalCost += r.costEstimate.estimatedCost;
|
||||
rows.push(
|
||||
` ${c.name.padEnd(18)} routed=${String(routed).padEnd(5)} skill=${String(actualSkill).padEnd(16)} ` +
|
||||
`expected=${c.shouldRoute ? (c.expectedSkill ?? 'any') : '(none)'} ${correct ? 'OK' : 'MISS'}`,
|
||||
);
|
||||
|
||||
evalCollector?.addTest({
|
||||
name: `routing-${c.name}`,
|
||||
suite: 'Opus 4.7 routing',
|
||||
tier: 'e2e',
|
||||
passed: correct,
|
||||
duration_ms: r.duration,
|
||||
cost_usd: r.costEstimate.estimatedCost,
|
||||
transcript: r.transcript,
|
||||
output: `routed=${routed} actual=${actualSkill ?? '(none)'} expected=${c.shouldRoute ? c.expectedSkill ?? 'any' : '(none)'}`,
|
||||
turns_used: r.costEstimate.turnsUsed,
|
||||
exit_reason: r.exitReason,
|
||||
});
|
||||
}
|
||||
|
||||
const posCount = ROUTING_CASES.filter((c) => c.shouldRoute).length;
|
||||
const negCount = ROUTING_CASES.length - posCount;
|
||||
const tpRate = posCount > 0 ? tp / posCount : 0;
|
||||
const fpRate = negCount > 0 ? fp / negCount : 0;
|
||||
|
||||
console.log(`[opus-4-7 routing] total cost $${totalCost.toFixed(2)}`);
|
||||
console.log(rows.join('\n'));
|
||||
console.log(
|
||||
` TP=${tp}/${posCount} (${(tpRate * 100).toFixed(0)}%) FN=${fn} ` +
|
||||
`FP=${fp}/${negCount} (${(fpRate * 100).toFixed(0)}%) TN=${tn}`,
|
||||
);
|
||||
|
||||
// Thresholds from the test plan artifact: TP >= 80%, FP <= 30%.
|
||||
// With a small N we loosen slightly: TP >= 66% (2 of 3 positive),
|
||||
// FP <= 33% (no more than 1 of 3 negatives).
|
||||
expect(tpRate, `true-positive rate ${(tpRate * 100).toFixed(0)}% (need >= 66%)`).toBeGreaterThanOrEqual(2 / 3);
|
||||
expect(fpRate, `false-positive rate ${(fpRate * 100).toFixed(0)}% (need <= 33%)`).toBeLessThanOrEqual(1 / 3);
|
||||
} finally {
|
||||
fs.rmSync(root, { recursive: true, force: true });
|
||||
}
|
||||
},
|
||||
360_000,
|
||||
);
|
||||
});
|
||||
@@ -1576,22 +1576,62 @@ describe('Test failure triage in ship skill', () => {
|
||||
});
|
||||
|
||||
describe('no compiled binaries in git', () => {
|
||||
// Tracked files enumerated once and reused by both assertions. git ls-files -z
|
||||
// + split is ~ms; the previous xargs-per-file shell loops blew past 5s on CI.
|
||||
const trackedFiles: string[] = require('child_process')
|
||||
.execSync('git ls-files -z', { cwd: ROOT, encoding: 'utf-8' })
|
||||
.split('\0')
|
||||
.filter(Boolean);
|
||||
|
||||
test('git tracks no Mach-O or ELF binaries', () => {
|
||||
const result = require('child_process').execSync(
|
||||
'git ls-files -z | xargs -0 file --mime-type 2>/dev/null | grep -E "application/(x-mach-binary|x-executable|x-pie-executable|x-sharedlib)" || true',
|
||||
{ cwd: ROOT, encoding: 'utf-8' }
|
||||
).trim();
|
||||
const files = result ? result.split('\n').map((l: string) => l.split(':')[0].trim()) : [];
|
||||
expect(files).toEqual([]);
|
||||
// Only mode 100755 (executable) files can be binaries we care about. Pre-filter
|
||||
// via git ls-files -s to avoid running `file` on every text file.
|
||||
const lsOut: string = require('child_process').execSync('git ls-files -s', {
|
||||
cwd: ROOT,
|
||||
encoding: 'utf-8',
|
||||
});
|
||||
const executableFiles = lsOut
|
||||
.split('\n')
|
||||
.filter(Boolean)
|
||||
.map((line: string) => {
|
||||
const parts = line.split(/\s+/);
|
||||
return { mode: parts[0], file: line.split('\t')[1] };
|
||||
})
|
||||
.filter((e: { mode: string; file: string }) => e.mode === '100755')
|
||||
.map((e: { mode: string; file: string }) => e.file);
|
||||
|
||||
if (executableFiles.length === 0) return;
|
||||
|
||||
// Batch-invoke `file --mime-type` across all executable files at once.
|
||||
const result: string = require('child_process')
|
||||
.execSync(`file --mime-type -- ${executableFiles.map((f: string) => `'${f.replace(/'/g, "'\\''")}'`).join(' ')}`, {
|
||||
cwd: ROOT,
|
||||
encoding: 'utf-8',
|
||||
})
|
||||
.trim();
|
||||
|
||||
const binaries = result
|
||||
.split('\n')
|
||||
.filter((l: string) =>
|
||||
/application\/(x-mach-binary|x-executable|x-pie-executable|x-sharedlib)/.test(l)
|
||||
)
|
||||
.map((l: string) => l.split(':')[0].trim());
|
||||
|
||||
expect(binaries).toEqual([]);
|
||||
});
|
||||
|
||||
test('git tracks no files larger than 2MB', () => {
|
||||
const result = require('child_process').execSync(
|
||||
'git ls-files -z | xargs -0 -I{} sh -c \'size=$(wc -c < "{}" 2>/dev/null | tr -d " "); [ "$size" -gt 2097152 ] 2>/dev/null && echo "{}:${size}"\' || true',
|
||||
{ cwd: ROOT, encoding: 'utf-8' }
|
||||
).trim();
|
||||
const files = result ? result.split('\n').filter(Boolean) : [];
|
||||
expect(files).toEqual([]);
|
||||
// Pure fs.statSync — no shell spawn per file.
|
||||
const MAX_BYTES = 2 * 1024 * 1024;
|
||||
const oversized = trackedFiles.filter((f: string) => {
|
||||
const full = path.join(ROOT, f);
|
||||
try {
|
||||
return fs.statSync(full).size > MAX_BYTES;
|
||||
} catch {
|
||||
return false;
|
||||
}
|
||||
});
|
||||
expect(oversized).toEqual([]);
|
||||
});
|
||||
});
|
||||
|
||||
|
||||
+23
-12
@@ -323,17 +323,28 @@ describe('gstack-team-init', () => {
|
||||
});
|
||||
|
||||
describe('setup --team / --no-team / -q', () => {
|
||||
test('setup -q produces no stdout', () => {
|
||||
const result = run(`${path.join(ROOT, 'setup')} -q`, { cwd: ROOT });
|
||||
// -q should suppress informational output (may still have some output from build)
|
||||
// The key test is that the "Skill naming:" prompt and "gstack ready" messages are suppressed
|
||||
expect(result.stdout).not.toContain('Skill naming:');
|
||||
expect(result.stdout).not.toContain('gstack ready');
|
||||
});
|
||||
// `./setup` does a full install + build + skill regeneration. On a cold cache
|
||||
// it routinely takes 60-90s. Give both tests a 3-minute budget so CI doesn't
|
||||
// report pre-existing timeouts as failures.
|
||||
test(
|
||||
'setup -q produces no stdout',
|
||||
() => {
|
||||
const result = run(`${path.join(ROOT, 'setup')} -q`, { cwd: ROOT });
|
||||
// -q should suppress informational output (may still have some output from build)
|
||||
// The key test is that the "Skill naming:" prompt and "gstack ready" messages are suppressed
|
||||
expect(result.stdout).not.toContain('Skill naming:');
|
||||
expect(result.stdout).not.toContain('gstack ready');
|
||||
},
|
||||
180_000,
|
||||
);
|
||||
|
||||
test('setup --local prints deprecation warning', () => {
|
||||
// stderr capture: run via bash redirect so we can capture stderr
|
||||
const result = run(`bash -c '${path.join(ROOT, 'setup')} --local -q 2>&1'`, { cwd: ROOT });
|
||||
expect(result.stdout).toContain('deprecated');
|
||||
});
|
||||
test(
|
||||
'setup --local prints deprecation warning',
|
||||
() => {
|
||||
// stderr capture: run via bash redirect so we can capture stderr
|
||||
const result = run(`bash -c '${path.join(ROOT, 'setup')} --local -q 2>&1'`, { cwd: ROOT });
|
||||
expect(result.stdout).toContain('deprecated');
|
||||
},
|
||||
180_000,
|
||||
);
|
||||
});
|
||||
|
||||
Reference in New Issue
Block a user