developer-skill-pack

Developer Skill Pack

A complete development toolkit for AI-assisted coding — UX testing, multi-agent coordination, TDD workflow, GitHub templates, research spikes, and repo scaffolding.

Works with Claude Code and OpenAI Codex CLI.

---

What's Inside

UX Testing (from ux-toolkit)

Skill	Description
ux-paths	Generate exhaustive user journey stories by analyzing the codebase. Produces short, medium, and long stories with a swarm of parallel sub-agents.
ux-walker	Walk the UX story catalog through a real browser, testing each journey for correctness, visual quality, and UX excellence. Auto-fixes small issues, files GitHub issues for larger ones.
walk-the-issues	Groom all open GitHub issues, then loop through them — branching, researching, implementing with swarms, testing, and creating PRs until all issues are complete.
deploy-check	Instrument a frontend with version fingerprinting (meta tag + /__version endpoint) so LLM-based testing can verify the correct build is deployed before walking.

Coordination (from claude-coordinator)

Skill	Description
coordinator	Pure-delegation control plane with a 10-phase state machine. Plans, delegates, reviews, and learns. 14 specialized agents with JSON Schema output contracts.
issue-groomer	Autonomous backlog groomer. Claims open status-less issues, researches each deeply (codebase + product docs + external APIs), fills the target repo's issue template exhaustively, and applies status:ready (clear path) or status:blocked (exhaustively groomed, path-decision needed). Loops; WATCH mode re-checks every poll_interval. Sequential v1 — one instance per repo.
issue-implementer	Autonomous backlog agent. Claims status:ready issues, drives each to a tested PR (red → green → regression commits), then loops until the backlog is clear or a stop condition trips. Sequential v1 — one instance per repo.
mine-transcripts	Sweep sub-agent JSONL transcripts for novel learnings and promote the strongest to durable docs. Parallel mining with dedupe baseline.

Development Process (from partyline + synthetix)

Skill	Description
setup-repo	Scaffold a repo with GitHub issue templates, PR template, TDD hooks, process docs, and CI configuration.
debug	Deterministic 7-phase debugging workflow — symptom capture through regression test commit.
regression-guard	Post-fix test-coverage analysis — generates unit and regression tests, audits how the bug could have been caught earlier.
research-spike	Time-boxed research with Context7 integration — produces structured findings in docs/research/.

Hooks

Hook	Event	Description
tdd-reminder	PreToolUse (Edit/Write)	Warns when modifying src/ without a failing test first
session-start	SessionStart	Announces TDD-first requirement

---

Launcher shortcuts (claude-groom / claude-implement)

claude-groom and claude-implement are shell shortcuts that invoke cco (the Claude Code sandbox wrapper) with the correct Gamut proxy settings and agent names — no flags to remember, no token in any script.

How it works

Both names are symlinks to bin/claude-coord in this repo. The script reads your Gamut auth token at runtime from one of two secure locations (never hardcoded), maps its invocation name to the right agent, and execs cco.

Install the symlinks

mkdir -p ~/.local/bin ~/.config/cco-gamut
chmod 700 ~/.config/cco-gamut
ln -sf /path/to/developer-skill-pack/bin/claude-coord ~/.local/bin/claude-groom
ln -sf /path/to/developer-skill-pack/bin/claude-coord ~/.local/bin/claude-implement

Replace /path/to/developer-skill-pack with the absolute path where you cloned this repo (e.g. /Users/you/develop/developer-skill-pack).

Make sure ~/.local/bin is on your PATH. Add to ~/.zshrc if needed:

export PATH="$HOME/.local/bin:$PATH"

Provide your token securely (after rotating any old token)

Option 1 — environment variable (per-session or in your shell profile):

export GAMUT_AUTH_TOKEN='<your-rotated-token>'

Option 2 — token file (persists across sessions):

echo '<your-rotated-token>' > ~/.config/cco-gamut/token
chmod 600 ~/.config/cco-gamut/token

The token is read at runtime. It is never written into any script or committed to this repo. The test suite (test/launcher.test.sh) will fail if a token literal ever appears in bin/claude-coord.

Usage