From groundwork
Brief usage guide for the groundwork plugin — what it is, how to use it, available commands
npx claudepluginhub vohaha/groundwork --plugin groundworkThis skill uses the workspace's default tool permissions.
Print the following groundwork usage guide:
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Designs, implements, and audits WCAG 2.2 AA accessible UIs for Web (ARIA/HTML5), iOS (SwiftUI traits), and Android (Compose semantics). Audits code for compliance gaps.
Print the following groundwork usage guide:
Groundwork gives Claude stable context and a two-way working agreement. It was designed by asking Claude what it needs — Claude is the primary beneficiary. Your role is to run the right commands and keep the working agreement current.
/groundwork:setup
Installs git hooks, creates WORKING_AGREEMENT.md and CLAUDE.md.
Signal your intent before giving Claude a task:
| Command | When to use |
|---|---|
/groundwork:do <task> | You want it done, no discussion |
/groundwork:think <topic> | You want options explored, nothing changed |
/groundwork:plan <task> | You want a design to approve before execution |
/groundwork:check-in
Updates WORKING_AGREEMENT.md and creates a checkpoint commit. Run this before closing.
| Command | What it does |
|---|---|
/groundwork:commit | Create a structured commit manually |
/groundwork:validate | Check that groundwork is set up correctly |
/groundwork:help | Show this guide |
WORKING_AGREEMENT.md is a two-way contract. Add to it when:
Claude reads it every session. Keep it current.
For path-scoped rules ("only style changes in auth/"): use .claude/rules/ files with paths: frontmatter — these load only when relevant.
For hard blocks: use settings.json permissions.deny.
$ARGUMENTS