Stats
Actions
Tags
From frontend-skills
Auto-guides frontend/React/TypeScript UI work through a full development lifecycle: understand, plan, grill, implement (TDD), and ship with automated PR creation and review.
How this skill is triggered — by the user, by Claude, or both
Slash command
/frontend-skills:development-lifecycleThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Auto-detect phase, guide process.
Auto-detect phase, guide process.
Feature branch? Skip. On main/master/develop? Spawn worktree before code. [ETHOS: Worktree Isolation]
scripts/mux-worktree.sh <type>/<branch-name>
Claude invoke silent when phase 1 start on default branch. User never run.
/prototype for 2-3 runnable UI variations, review with user, pick best. See REFERENCE.md./ultraplan/codex:rescue available -> auto-dispatch second opinionGATE: no impl until plan survive grilling.
/grill-with-docs | grill until every branch resolved | update CONTEXT.md + ADRs inlinesetTimeout hacks | run --detectAsyncLeaks/goImpl done -> run /go to ship. Handle all:
/simplify -> /commit-push-pr -> code-reviewer agent/resolve-pr-feedback -> AI self-review: up to 3 rounds, early-exit on clean; human review: address ALL (hook-enforced).claude/rules/See /go skill full details. See REFERENCE.md phase-specific checklists.
Full flowchart REFERENCE.md#phase-flowchart.
| User says | Phases |
|---|---|
| "Build a new feature" | 1->2->2b->3->/go |
| "Fix this bug" | 1(reproduce)->3(TDD)->/go |
| "Refactor this module" | 1->2->2b->3->/go |
| "Write tests for X" | 3 only |
| "Ship it" / "Create a PR" | /go only |
| "Quick question" | Just answer |
| "Batch these 5 issues" | Sandcastle -- parallel agents |
| "Work on this overnight" | Sandcastle -- AFK delegation |
See REFERENCE.md detailed checklists + Sandcastle integration.
npx claudepluginhub redpanda-data/ui-harness --plugin frontend-skillsFull frontend workflow: understand, plan, grill, TDD implementation, verify, and ship. Use for React/TypeScript/UI development tasks.
Orchestrates full dev cycle in isolated git worktree: task understanding, TDD implementation, quality review, draft PR, CI/CD monitoring to merge-ready PR. Explicit invoke via /developer-workflow:implement-task.
Initiates tasks by interviewing user for requirements, setting up git-wt worktrees or branches, checking tools like direnv/dotenvx, and creating plans for review.