The Aura Pro Demo Prompt Generator Is 11 Templates, Not One Model. I Ran Every Category.

Every product page on the WorkflowAlpha.ai site has a working interactive demo — a tool you type into and get a real result back before you pay a cent. On the Aura Pro page, that demo is a prompt generator: type a topic, pick one of 11 intent categories, get a complete structured prompt.

I wanted to know what it actually is under the hood, so I did the thing I always do. I pulled the page source, found the script block, and ran the template object directly in Node with one identical topic across every category.

The topic I fed it: a booking system for a small restaurant.

What I found: it is a template engine, not a language model

The demo exposes a PROMPT_TEMPLATES object with 11 keys. Each value is a function that takes your topic string and returns a complete markdown prompt. There is no API call, no network request, no key. The topic is interpolated into a fixed skeleton that is hand-written per category.

That is not a criticism — it is the thing that makes the product work offline on a phone. It is exactly what the page claims: "No API key needed for core generation — runs entirely on-device." The claim holds up.

The measurement table

I ran all 11 categories with the same topic and counted characters, words, and structure. Every single one passed: no blank output, no crash, and the topic string is echoed back in the final instruction line of every category.

Result: 11 of 11 categories produced usable output. Character range 821–973. Every category carries exactly one ## Requirements block with 6 numbered requirements and one ## Output Format block with bulleted deliverables.

What the output actually looks like

Here is the Legal category verbatim, which is short enough to quote:

You are a legal advisor. Your task is to provide guidance on: a booking system for a small restaurant

Requirements

1. Explain the legal landscape and relevant laws/regulations
2. Identify key legal considerations and potential issues
3. Provide actionable steps for compliance or protection
4. Suggest when to consult a licensed attorney
5. Include relevant documentation or contract considerations
6. Address jurisdiction-specific factors

Output Format

• Disclaimer: This is informational, not legal advice
• Legal Overview: Relevant laws and regulations
• Key Issues: Main legal...

The pattern across all 11: role assignment → 6 requirements → output format spec → a closing line that names your topic. The role and the deliverables change per category; the spine does not.

Why this matters to a buyer

Two things, and they pull in opposite directions.

The good: the structure is genuinely professional. A 6-point requirement list with a fixed output contract is a real prompt-engineering pattern. Feed any of these 11 outputs into a frontier model and you get a structured, on-format answer on the first try instead of a generic one. That is the product's value, and the demo proves it without an API key.

The honest limitation: because the topic is interpolated into a fixed skeleton, the output depth is capped by the template, not by your input. Type a booking system for a small restaurant and type help me write a haiku into the same category and you get the same 6 requirements and the same deliverable list. The generator does not reason about your topic — it formats a request about it.

I would rather tell you that now than have you find out after paying. If you are buying Aura Pro expecting a model that adapts to each request, the demo will not show you that, because it does not do it. If you are buying it for a reliable, offline, structured prompt factory across 11 disciplines, the demo shows you exactly that.

The rest of what the package contains

The prompt engine is one part. The full Aura Pro package is a complete Android app takeover:

• app-release.apk — signed, 3.7 MB, package com.auraprompt.app, all premium features unlocked for testing
• play_takeover.py — one command that drives the Google Play Developer API: APK upload, auto-filled store listing, store images, in-app products, subscription products, track activation, publish
• upload_to_play.py — lighter APK-only path
• README-TAKOVER.md and README-PLAY-SETUP.md — buyer docs covering Google Cloud setup, service account creation, Play Console invite, and the manual steps the API cannot do
• Optional: the signing keystore and the full source tree

Google Play Billing is already wired via BillingClient 6.2.0, with the monthly and annual subscription product IDs defined. Only 6 manual Console steps remain after the script runs — Data Safety, content rating, category, pricing, review submission, push notifications. All of them are documented in the READMEs.

Test it before you pay

Download the demo APK, install it on any Android phone, and run all 11 categories yourself. Verify the UI, verify the offline generation, verify there are no blanks and no crashes. Then decide.

Price: $299.99 USD, one-time. Lifetime ownership.

Payment:

• PayPal — send to [email protected] and write a note stating it is for Aura Pro. You get a payment request and it is confirmed in the inbox.
• Crypto — ETH, USDC, or USDT on the Base network to 0x078fE079A9440631Bc6AD722D7143dC382b4ea4f
• Western Union / MoneyGram — details sent on request

To buy, email [email protected] stating you want Aura Pro. Payment details are confirmed and the full package is delivered as a zip after payment.

Bottom line

I ran all 11 categories and 11 of 11 worked, which is a better hit rate than most code generators I have tested. The architecture is a template engine — and it says so on the page. If you want to see the exact output shape before spending anything, the demo on the Aura Pro page will show it to you right now.

If you have a product page you want tested this way, email the address above — I run the same measurement pass on any interactive demo.