Augmenters
Augmenters are special skills that modify your generated app's file tree. They read what you have, generate JSON patches via LLM, write them back, and hot-reload the preview. Re-running an augmenter is safe — they're idempotent.
#How augmenters work
A typical run cycle looks like this:
- You invoke
/seo(either inline in chat or queued via the chip row). - The augmenter reads your full workspace file tree.
- It generates a strict JSON patch: list of files to create or modify, with full new contents.
- The patch is parsed, validated, and applied to the workspace.
- The WebContainer hot-reloads — usually within 200ms.
Each augmenter writes a small idempotency marker into the files it touches (e.g. {/* @seo:applied */}) so a second run can detect what's already done and only update the parts that changed.
#The eight augmenters
/seo
Adds production-grade SEO scaffolding: full meta tag set, Open Graph, Twitter cards, JSON-LD structured data, robots.txt,sitemap.xml, canonical URLs.
/seo
/seo brand: Acme, audience: small biz owners/geo
Drops i18n scaffolding: a lightweight locale store, language switcher, content-negotiation hints, and example translations for the visible strings.
/marketing
Wires analytics and lead capture: Google Analytics, PostHog placeholders, a CRM-friendly lead form component, UTM-aware link helpers.
/a11y
Pass-through accessibility audit + fixes: semantic landmark elements, ARIA labels, focus visibility, keyboard nav, contrast corrections, prefers-reduced-motion guards.
/pwa
Adds a web app manifest, service worker (offline-first cache), install prompt UI, and home-screen icons.
/perf
Performance pass: route-level code-splitting, lazy-loaded images with placeholders, preloads for critical assets, font-display tweaks.
/auth
Scaffolds Supabase auth: signin / signup pages, OAuth buttons, protected route helper, session context.
/payments
Drops Razorpay subscription scaffolding: pricing page, checkout client, webhook handler stub, current-plan banner.
#Two ways to run
Inline — single run
Type /seo in chat. Same flow as any critique skill, except the result panel shows a "files modified" list with new/edited badges. The preview hot-reloads automatically.
Queue — pre-build
Above the prompt input is a row of augmenter chips. Click to select, click again to deselect. Selected augmenters queue up and run sequentially after the next build pipeline finishes.
#Preview before applying (dry-run)
Click the Preview button above the chip row to open the Augmenter Preview modal. It runs the augmenter in dry-run mode — generates the patch but doesn't apply it. You see exactly which files would change, what's new vs modified, and you can choose to apply or cancel.
Useful for previewing destructive augmenters or for understanding what an augmenter does before committing.
#Conflicts between augmenters
Some augmenters touch overlapping files — for example, /seo and /marketing both want to inject script tags into the document head. PromptFloe detects these overlaps and warns you in the chip row before you queue them together.
When a conflict is detected, the chips show a yellow alert icon and a tooltip listing the affected files. You can still queue them — augmenters run sequentially and each reads the up-to-date file tree — but the warning is there so you can audit the result.
#Cancelling a run
A running augmenter shows a spinner in the result card with a Skip button. Skip aborts only the current augmenter — if more are queued, they continue. To cancel everything, press Esc twice or click Stop in the run header.
#Tier requirements
Augmenters require Basic or higher. Free accounts see the chips disabled with an upgrade prompt. Daily limits:
| Field | Type | Description |
|---|---|---|
| Free | 0 / day | Locked. |
| Basic | 6 / day | Modest volume — enough for one app per day. |
| Pro | 40 / day | Power-user volume. |
| Max | 200 / day | Heavy use. |
| Enterprise | unlimited | No caps. |