Hyperflow scaffold
Hyperflow project setup. Use when starting hyperflow in a new project or refreshing its cache — "init hyperflow", "set up hyperflow", "refresh hyperflow", "scaffold hyperflow". One-shot setup of the .hyperflow/ project cache + memory and the .agent/workflows/hyperflow* slash commands. Does not start the plan → dispatch chain.From its SKILL.md
npx -y skills add jeremylongshore/claude-code-plugins-plus-skills --skill hyperflow-scaffoldAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.7 KB, 355 tokens by cl100k_base, as published. Nobody here has run it
hyperflow-scaffold — project setup (Antigravity single-agent)
One-shot setup of hyperflow's project surfaces. Follow the hyperflow doctrine.
Steps
- Create the
.hyperflow/cache at the repo root if absent:.hyperflow/memory/withdecisions.md,learnings.md,pitfalls.md,patterns.md(empty stubs, each with a one-line header)..hyperflow/tasks/,.hyperflow/specs/,.hyperflow/audits/(empty dirs).
- Write context files (
.hyperflow/profile.md,architecture.md,conventions.md) by reading the repo: stack, top-level layout, test/lint conventions, commit conventions. Keep each short and factual. - Install project slash commands: copy the
hyperflow*workflow files into<repo>/.agent/workflows/(so/hyperflow,/hyperflow-plan,/hyperflow-design, … resolve in Antigravity's/menu). Source: thetemplates/antigravity/workflows/shipped with hyperflow. - Note that global hyperflow skills live in
~/.gemini/config/skills/(auto-trigger) and global rules in~/.gemini/AGENTS.md. - Print a one-line summary of what was created. Do NOT start the chain.
Rules
- Idempotent — never clobber existing
.hyperflow/content; only create what's missing. .hyperflow/tasksand.hyperflow/specsare runtime artefacts;.hyperflow/memoryis durable and worth committing.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.