Hyperflow Amplify
Hyperflow prompt amplifier. Use when a prompt is rough, vague, or under-specified and should be rewritten to high quality before running it — "enhance this prompt", "make this prompt better", "improve my prompt", "rewrite this prompt". Domain-aware: detects the prompt's domain, injects the matching specialist standards + project rules, scores against an 8-dimension rubric, then offers to run it.
Install
$ agentstack add skill-jeremylongshore-claude-code-plugins-plus-skills-hyperflow-amplify ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
hyperflow-amplify — prompt amplifier (Antigravity single-agent)
Turn a rough prompt into the single strongest version, then hand it off. Amplify never writes code — it produces a prompt other workflows (or you) execute. Follow the hyperflow doctrine.
Steps
- Read intent. Detect the prompt's domain(s) (frontend/ui, api/db backend, mobile, security, performance, refactor/bugfix/test, devops, docs). Read project rules when present:
AGENTS.md,~/.gemini/AGENTS.md,.hyperflow/memory/*. Note the gaps a senior engineer would have to guess. - Amplify. Rewrite into the single strongest version using this skeleton (adapt section presence — economy is a constraint, never inflate a one-liner into a spec):
- role / expertise framing (one line)
- precise task (unambiguous goal)
- Context (relevant background, current state, inputs)
- Constraints (domain doctrine standards + project rules — project rules win on conflict)
- Output (deliverable format + acceptance criteria)
- Out of scope (explicit anti-goals)
- Score the draft against the 8-dimension rubric (1-5 each): intent clarity · context sufficiency · scope boundaries · structure · domain doctrine injected · output spec · guardrails · economy. If any dimension < 4, revise once.
- Present the amplified prompt in one copy-ready fenced block + a 2-4 line rationale (what changed, which standards/project rules were injected, any flagged ambiguity).
- Handoff gate (AskUserQuestion, 4 options → mark one Recommended): Send to
hyperflow-spec(Recommended) · Send tohyperflow-scope· Send tohyperflow-dispatch· Copy only. On a "Send to…" choice, invoke that workflow with the amplified prompt.
Rules
- Never write code. Project rules override generic persona standards. No AI attribution in the amplified prompt or rationale.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: jeremylongshore
- Source: jeremylongshore/claude-code-plugins-plus-skills
- License: MIT
- Homepage: https://tonsofskills.com
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.