fh:help

Output ONLY the reference content below. Do NOT add project-specific analysis, git status, next-step suggestions, or any commentary.

# fhhs-skills Command Reference

Getting Started

First time? Follow these steps:

1. /fh:setup — Install tools, configure LSP, set up hooks (~2 min, once)
2. /fh:new-project — Define your project vision, tech stack, and roadmap
3. /fh:plan — Plan your first feature or phase
4. /fh:build — Execute the plan with tests, quality checks, and verification

Returning? Run /fh:progress to see where you left off and what's next.

Need help? You're reading it. See command tables below, or ask any question about a specific command.

---

Build Pipeline

Command	What it does
/fh:new-project	Set up a project with vision, tech stack, design language, and roadmap
/fh:plan	Brainstorm, research, and produce an execution-ready plan. Handles phase creation and placement automatically
/fh:build	Execute a plan with parallel subagents, TDD, design gates, and verification. Handles milestone completion automatically
/fh:verify	Goal-backward verification with truth tables and fresh evidence
/fh:verify-ui	Visual verification with browser screenshots

Engineering

Command	What it does
/fh:fix	Auto-triage and fix bugs with systematic debugging
/fh:refactor	Restructure code safely, tests green at every step
/fh:research	Investigate a topic before planning

Navigation

Command	What it does
/fh:resume	Restore context and route to the right next action
/fh:progress	See where you are and what's next

Design Quality

Command	What it does
/fh:critique	Evaluate visual hierarchy, information architecture, and design quality
/fh:ui-animate	Purposeful motion and micro-interactions
/fh:ui-branding	One-time setup for your project's design language

Design agents (dispatched automatically by /fh:review, /fh:refactor, /fh:fix, and /fh:build):

Agent	What it does
fh:design-polish	Fix alignment, spacing, consistency, and detail issues
fh:design-normalize	Match your design system and ensure consistency
fh:design-harden	Error handling, i18n, text overflow, edge cases
fh:design-audit	Full accessibility, performance, theming, and responsive audit
fh:design-adapt	Make designs work across screen sizes and platforms
fh:design-bolder	Amplify safe designs to be more visually interesting
fh:design-quieter	Tone down overly aggressive designs
fh:design-distill	Strip away unnecessary complexity
fh:design-clarify	Improve confusing labels, errors, and microcopy
fh:design-colorize	Add strategic color to monochromatic interfaces
fh:design-delight	Add personality and moments of joy
fh:design-extract	Pull reusable components into your design system
fh:design-onboard	Design first-time user experiences and empty states
fh:design-optimize	Improve loading speed, rendering, and bundle size
fh:design-secure	Security scanning of changed files
fh:design-simplify	Review code for reuse, quality, and efficiency

Task Management

Command	What it does
/fh:todos	Track things to do — add or review pending todos

Phase management, milestone lifecycle, and test generation are handled automatically by /fh:plan, /fh:build, and /fh:verify.

Setup & Maintenance

Command	What it does
/fh:setup	One-time setup after installing
/fh:settings	Configure workflow preferences
/fh:health	Check if your project files are in good shape
/fh:map-codebase	Analyze your codebase structure
/fh:learnings	Capture and apply session learnings, optionally update CLAUDE.md
/fh:update	Check for updates and install the latest version

Common Workflows

First time:   See "Getting Started" above
Feature:      /fh:plan → /fh:build → /fh:verify → /fh:verify-ui
Bug fix:      /fh:fix
Refactoring:  /fh:refactor (dispatches fh:design-simplify agent automatically)
Resuming:     /fh:resume → (routes to next action)
CLAUDE.md:    /fh:learnings (after sessions to capture and apply learnings)

Files & Structure

.planning/
├── PROJECT.md            # Project vision
├── ROADMAP.md            # Current phase breakdown
├── STATE.md              # Project memory & context
├── DESIGN.md             # Design language (from /fh:ui-branding)
├── config.json           # Workflow mode & gates
├── todos/                # Captured ideas and tasks
├── debug/                # Active debug sessions
├── milestones/           # Archived milestone data
├── codebase/             # Codebase analysis (from /fh:map-codebase)
└── phases/               # Phase plans, summaries, and verifications

Architecture

GSD is the state machine. It owns project structure: phases, milestones, requirements, roadmaps, STATE.md. Always required — run /fh:new-project first.

Composites are the interface. They wire engineering disciplines, design quality tools, and GSD together so you never think about which skill to invoke. Subagents do the heavy work — composites stay under 15% context.

Self-contained. All engineering disciplines, design quality tools, GSD project tracking, and TypeScript LSP integration are built into this plugin.

Non-Negotiable Disciplines

Every composite that executes code enforces these via built-in skills:

1. TDD — no production code without a failing test first
2. Post-build code review — code quality and architecture review via /fh:review --quick
3. Quality review — code quality and architecture review
4. Simplify — code reuse, efficiency, and hygiene
5. Tests/build/lint verification — no claims without fresh evidence
6. Fresh subagents — structured prompts with self-review and analysis paralysis guard
7. YAGNI — no features, abstractions, or error handling beyond what's specified

Code Intelligence

TypeScript LSP (installed via /fh:setup) provides precise code navigation used across composites: workspaceSymbol and documentSymbol for architecture analysis, findReferences for blast radius mapping, goToDefinition and call hierarchy for data flow tracing, hover for type information.