Operator manual

Exactly how to get what you want out of SuperGrok Heavy

Prompt formulas, control surfaces, approval ladders, verification loops, and copy-paste templates that turn Heavy from chatty to precise.

HeavyThis is the meta-chapter — how to drive every other chapter in this manual.

Mental model: Heavy is a studio, not a vending machine

SuperGrok Heavy wins when you give it constraints, done criteria, and a control surface (CLI plan mode vs Web Build vs Imagine). Vague prompts produce average SaaS purple. Tight prompts produce product.

You provide	Heavy can deliver	If missing
Audience + job-to-be-done	Right tone and IA	Generic startup voice
Hard bans (anti-slop)	Tasteful UI	Purple gradients
Done criteria	Stops at shippable	Endless partial work
Freeze lists (video)	Same character	Face drift
Approve / plan gates	Safe multi-file edits	Surprise rewrites

The universal prompt formula

Copy this skeleton every time

GOAL: [one sentence — what exists when we're done]
CONTEXT: [product, audience, stack, hosting]
CONSTRAINTS:
- Keep: [routes, brand hex, form endpoints, data models…]
- Ban: [purple gradients, lorem, emoji icons, scope creep…]
- Quality: [mobile 390px, a11y, clean console…]
DELIVERABLES: [files/pages/assets + order]
DONE WHEN: [testable checklist]
MODE: [plan only | design only | implement | iterate only]

Filled example — website

GOAL: Ship a Hostinger-ready marketing site for a fintech API startup.
CONTEXT: Audience = CTOs; stack = React+Tailwind static export; host = Hostinger Cloud Startup (dedicated IP).
CONSTRAINTS:
- Keep: brand accent #5EEAD4, no blog yet
- Ban: purple gradients, lorem, stock photos of handshakes
- Quality: 390px no overflow, SEO meta, real FAQ
DELIVERABLES: tokens → home → pricing → contact form → deploy notes
DONE WHEN: clean console, form validates email, Lighthouse-friendly images
MODE: design only first, wait for approval, then implement

Pick the right surface (this is half the battle)

I want…	Use	How to drive it
Fast demo app / site	Web Build Mode	One rich brief; iterate in small product asks
Edits in my real repo	CLI / PowerShell	/plan → approve → diffs; off yolo
Taste first	/design skill	Tokens + hierarchy before code
Same face across clips	Imagine Video 1.5	Bible + multi-ref + freeze lists
Overnight fixes	grok -p / /loop	Narrow scope + stop conditions

Deep compare: CLI vs Web. Tiers: Heavy tier map.

The approval ladder (use it)

Recommended sequence

1) /design or design-only prompt  → approve tokens
2) /plan or implementation plan   → approve file list
3) Implement                      → review diffs
4) Iterate small                  → "keep X, change Y only"
5) Verify                         → console + mobile + forms
6) /skillify                      → lock the win for next project

Watch out

/yolo / always-approve skips the ladder. Fine for sandboxes; dangerous in production monorepos. It can persist — check session mode.

Templates that extract quality

A. Implement with freeze scope

Scope freeze

Implement the approved design for /pricing only.
FREEZE: routes, auth, database schema, global nav structure.
CHANGE ONLY: pricing page layout, tier copy, mobile spacing.
If you need a new dependency, stop and ask.

B. Iteration that doesn't thrash

Surgical iterate

Do not redesign.
1) Increase hero contrast
2) Move secondary CTA under primary on mobile
3) Fix FAQ keyboard focus rings
Leave everything else identical.

C. Force options then choose

Options mode

/plan Propose 3 approaches for multi-tenant billing:
A) simplest B) most scalable C) best DX
Table: tradeoffs, risks, time. Recommend one. Wait — do not code.

D. Video continuity

Freeze list

Refs: @face @outfit @location
FREEZE: face geometry, hair, scar, coat color, pendant, proportions.
CHANGE ONLY: she turns and walks to the window. 6s, one camera move.
1080p if available.

E. Headless CI agent

grok -p

grok -p "Run unit tests. Fix only failures and direct causes.
No refactors. No dependency upgrades. Stop when green.
Print files changed." --no-auto-update

F. Recurring monitor

/loop

/loop 15m Check production health endpoint and last deploy.
If failing, open a short plan to fix; do not auto-apply without approval.
Stop after 3 consecutive healthy checks.

When Heavy gives the wrong thing

Symptom	Fix prompt
Looks generic / AI-slop	Ban list + reference 2 taste words + force tokens first
Changed too much	FREEZE list + “diff summary first” + smaller surface
Blank / broken UI	“Reproduce console errors; fix only those; verify visible content”
Character face drifts	Fewer changes; more refs; freeze list; shorter 6s shot
Ignores skill / design rules	grok inspect; re-invoke /design; put rules in AGENTS.md
Long session lost context	/flush before compact; /remember hard constraints

Hard reset message

STOP. Re-read constraints.

You violated: [what]
Required freeze: [list]
Required deliverable now: [single next artifact]
Do not continue past that until I say proceed.

Always attach verification (Heavy will do it if asked)

Verification block — paste at end of every build prompt

VERIFY before done:
1) Visible content on main routes (not blank root)
2) Browser console: zero uncaught errors
3) Mobile ~390px: no horizontal overflow; primary CTA usable
4) Forms: validation + success path
5) Production build mindset: assets resolve; no broken imports
Report pass/fail for each.

Power sequences (copy whole blocks)

Sequence: startup site in one afternoon

# Web Build Mode
[paste startup brief from /startup-sites]
→ iterate hero + pricing only
→ add waitlist form
→ “mobile polish pass + clean console”
→ export / publish
# optional: Hostinger upload notes from /websites

Sequence: refresh legacy site

/design audit only (from /refresh)
→ approve token proposal
→ CSS layer OR homepage surgical rewrite
→ SEO redirect plan
→ staging verify
→ deploy + CDN purge

Sequence: multimedia brand

Imagine hero still → I2V 6s loop
→ brief from /multimedia with poster path
→ VideoHero + StoryChapter + ProjectGrid
→ prefers-reduced-motion check
→ compress media; Hostinger /media upload

Sequence: compound Heavy advantage

/design house system → /skillify as studio-design
Web Build product MVP with that taste
Imagine character bible + 3 progressive clips
Hostinger marketing site embeds reel
CLI -p keeps tests green overnight

The one rule

If you cannot write a DONE WHEN checklist, you are not ready to prompt. Write the checklist first — Heavy will chase it.

More: Prompt library · Cheat sheet · Easter eggs · Workflows