hyperflow-cache
Hyperflow memory manager. Use to view, search, add, edit, prune, or clear hyperflow project memory — "show memory", "search memory for X", "clear memory", "what does hyperflow remember about Y". CRUD over .hyperflow/memory/ only — never touches source code.
git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace /tmp/hyperflow-cache && cp -r /tmp/hyperflow-cache/plugins/ai-agency/hyperflow/templates/antigravity/skills/hyperflow-cache ~/.claude/skills/hyperflow-cacheSKILL.md
# hyperflow-cache — memory CRUD (Antigravity single-agent)
Manage `.hyperflow/memory/` entries. **Only memory files** — never source code. Follow the `hyperflow` doctrine.
## Operations
- **view / list** — print the entries in `.hyperflow/memory/{decisions,learnings,pitfalls,patterns}.md`.
- **search `<term>`** — grep the memory files; show matching entries with their file + heading.
- **add** — append a tagged entry to the right category file (decisions / learnings / pitfalls / patterns). Use the format: `## <topic>` then `- <fact> (recorded <YYYY-MM-DD>)`.
- **edit `<entry>`** — update an existing entry in place (don't duplicate).
- **prune / clear** — remove stale or wrong entries. Confirm via AskUserQuestion before a destructive clear (binary Yes/No).
## Rules
- Scope is `.hyperflow/memory/` only. Don't record what the repo/git already captures; record the non-obvious why.|
Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.
Plan and scope a project — discovery, challenge assumptions, present S/M/L options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.
Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.
Cross-cutting review of recent work — catches gaps between specialists. Use when asked to "review what we built", "check the work", "pre-launch review", or after completing a significant chunk of work.
CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.
System takeover — take ownership of an existing codebase or inherited system. Use when "we acquired this", "previous team left", "take over this system", "inherited this codebase".
Knowledge engineer — architecture docs, ADRs, diagrams, changelogs, onboarding, and reports.