TrebuchetDynamics

Resolve short approval against the latest checkpoint. Use for "lgtm", "looks good", "approved", or "go ahead"; not risky or review feedback.

Re-check a prior assistant claim. Use when user says "nack", "not convinced", or "check again"; not for review feedback.

UI/UX routing front door. Use as the front door for broad or ambiguous UI/UX work that needs the right build, redesign, audit, design-system, accessibility, or browser specialist. Do not use when the user already names a narrower UI skill.

Proposes UI Vault resource upgrades for a selected webpage. Use when the user asks for libraries, assets, effects, or inspiration for an existing page. Do not use for implementation or greenfield design.

Upload, list, or delete files with s3upload and return expiring Azure links. Use for configured temporary Azure storage; not for S3 or cloud setup.

Ship local Git changes by inspecting, polishing, validating, split-committing, and pushing. Use for commit, push, ship, delivery audit, or delivery blockers; not deploys or releases.

Remove proven unreachable code in small validated batches. Use when asked to find and delete dead, stale, orphaned, or unused code; not for dependency pruning, over-engineering reports, or speculative cleanup.

Redesigns a GitHub repository README or creates GitHub-safe README SVG assets from real project evidence. Use for README visual overhauls, heroes, section banners, diagrams, badges, or read-only README audits; not general website UI or ordinary documentation maintenance.

Implement one selected repo-scoped Gormes row with tests. Use when next-work says decision=build. Do not use for decision=plan, broad parity audits, or untracked feature ideas.

Shape source-backed Gormes progress rows. Use for decision=plan builder handoffs, row splitting, feature maps, or parity planning. Do not use when decision=build or for runtime code.

Route Gormes work to the smallest repo-local skill chain. Use before substantial planning/building/refactor work, when unsure which Gormes skill applies, or when creating/improving repo-local skills.

Build one selected Gormes behavior with red-green-refactor. Use when the row or reproduced bug defines a test target. Do not use after decision=plan or for broad planning.

Move one bounded cmd/gormes command domain out of root files toward root main.go only. Use when thinning cmd/gormes, burning down loose root files, preserving CLI behavior, or catching refactor regressions during cmd moves.

Use when an agent is unfamiliar with a Gormes code area, a change crosses package boundaries, or a refactor needs a source-backed module map before edits.

Plan or implement browser automation parity. Use for Browser Use, go-browser-harness, CDP, /browser connect, browser providers, tool descriptors, and browser interaction skills.

Use when the user invokes gormes-git to commit every current Gormes worktree change in coherent split commits, make development green, and push only the existing development branch.

Audit Gormes sessions under ~/.gormes. Use when inspecting agent sessions, gateway state, indexes, logs, locks, or fix plans.

Implement Goncho negative memory and anti-repeat behavior. Use when working on dead-end recall, drift anchors, repeated-failure warnings, feedback labels, or negative-memory supersession.

Implement Goncho graph and cognitive-map recall. Use when working on relation extraction, entity links, graph-expanded retrieval, topology, branch routing, or multi-hop recall provenance.

Stress-test Goncho-specific implementation plans before coding. Use when asked to grill a Goncho roadmap slice, validate readiness for TDD, challenge a memory-system design, or find gaps against Goncho docs/metaanalysis.

Implement Goncho lifecycle and trust behavior. Use when working on temporal validity, supersession, conflict review, audit trails, verification, stale-memory warnings, quarantine, or redaction.

Release Goncho next minor version safely. Use when asked to make release CI green, publish Goncho, create a GitHub release, tag a Goncho version, or update pkg.go.dev/go.dev package metadata.

Implement Goncho roadmap features with red-green-refactor. Use when changing Goncho behavior from TODO.md, README roadmap, docs/superpowers plans, or memory-system metaanalysis gaps.

Implement Goncho shared/team/server behavior. Use when working on server mode, team memory, PostgreSQL adapters, ACLs, roles, leases, receipts, team feeds, import/export, or multi-user governance.

Audits Go code for goroutine-to-widget access without fyne.Do(...) wrapping, the project's most common GUI freeze cause. Use when reviewing a PR that adds goroutines, async I/O, or simulation tickers in any pkg/gui/ or shell package.

Runs build flows for the canonical Fyne shell and module commands on this Go 1.25 monorepo. Use when building, packaging, or debugging build failures in cmd/fecim-lattice-tools or module GUI commands.

Relentlessly interviews the user about a proposed FeCIM physics, simulation, or GUI change before any code is written — covering source citation, educational-vs-validated framing, TDD-RED test, thread-safety, and honesty-audit alignment. Use when starting a non-trivial change to physics, ISPP, crossbar, or GUI logic.

Runs the FeCIM test matrix (full, race, module-scoped, coverage, golden regen) and interprets physics regression failures using the 5 known bug patterns. Use when running tests, debugging test failures, or regenerating physics golden files.

Verifies and formats FeCIM physics/measurement claims against the project's published-source list and docs/4-research/honesty-audit.md. Use when adding a numeric claim, accuracy figure, or device-parameter assertion to code, docs, PR descriptions, or commit messages.

Enforces docs/4-research/honesty-audit.md policy by scanning PR diffs, READMEs, and presentation material for removed/unverified claims (87% MNIST, 30-states-as-fact, energy multipliers vs NAND/GPUs). Use before committing docs, PRs, or release notes that include accuracy or efficiency numbers.

Surveys FeCIM domain knowledge by searching references/, citations/, docs/4-research/, and the local Cognee KG, then synthesizes a cited research note. Use when investigating a physics topic, evaluating a paper, or grounding a design decision in literature.