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.
92%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
One-shot setup of hyperflow's project surfaces. Follow the hyperflow doctrine.
.hyperflow/ cache at the repo root if absent:
.hyperflow/memory/ with decisions.md, learnings.md, pitfalls.md, patterns.md (empty stubs, each with a one-line header)..hyperflow/tasks/, .hyperflow/specs/, .hyperflow/audits/ (empty dirs)..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.hyperflow* workflow files into <repo>/.agent/workflows/ (so /hyperflow, /hyperflow-plan, /hyperflow-design, … resolve in Antigravity's / menu). Source: the templates/antigravity/workflows/ shipped with hyperflow.~/.gemini/config/skills/ (auto-trigger) and global rules in ~/.gemini/AGENTS.md..hyperflow/ content; only create what's missing..hyperflow/tasks and .hyperflow/specs are runtime artefacts; .hyperflow/memory is durable and worth committing.ab85a06
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.