From Golden Hoop Spell
Initialize ghs project tracking by creating .ghs/features.json and .ghs/progress.md. Use when setting up a project for ghs for the first time, or when other ghs skills fail because .ghs/ doesn't exist.
How this skill is triggered — by the user, by Claude, or both
Slash command
/golden-hoop-spell:ghs-initThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Set up the project with `.ghs/features.json` and `.ghs/progress.md` so the ghs system can track sprints, features, and progress across sessions. These files live inside `.ghs/` (gitignored) so they stay local.
Set up the project with .ghs/features.json and .ghs/progress.md so the ghs system can track sprints, features, and progress across sessions. These files live inside .ghs/ (gitignored) so they stay local.
Run the init script from the project directory:
python3 ${CLAUDE_PLUGIN_ROOT}/shared/scripts/init_project.py "<PROJECT_NAME>" --description "<DESCRIPTION>" --project-dir "$(pwd)"
The script creates the .ghs/ directory with:
${CLAUDE_PLUGIN_ROOT}/shared/assets/features.json)${CLAUDE_PLUGIN_ROOT}/shared/assets/progress.md).ghsVerify files were created:
ls .ghs/features.json .ghs/progress.md
Tell the user to run /ghs:sprint to plan their first sprint.
All ghs commands operate on the current project directory. If the working directory might not be the project root, resolve it first:
python3 ${CLAUDE_PLUGIN_ROOT}/shared/scripts/resolve_project_dir.py
This walks up from the current directory to find where .ghs/features.json or .ghs/progress.md lives.
npx claudepluginhub wangdahoo/golden-hoop-spell --plugin golden-hoop-spellProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.