Use Cases & Blueprints

Use cases are ready-made task blueprints that let you launch proven outcomes in one click. Instead of writing a prompt from scratch, browse the library, pick a blueprint, and hit "Use this" — the platform auto-configures the right agent, model, and services for you.

Finding Use Cases

Navigate to the Use Cases library from the Home page, the sidebar nav, or directly at /use-cases.

The library is organized by category:

• Landing Pages — waitlists, portfolios, event pages
• Dashboards — admin panels, analytics UIs
• Integrations — payment flows, auth systems, email services
• Pipelines — CI/CD, data processing, content generation
• Automations — cron jobs, bots, scheduled workflows
• And more

Use the search bar to find blueprints by keyword, or click a category to filter.

Free vs. Pro Blueprints

Some blueprints are available to everyone, while others are marked with a Pro badge. Pro blueprints typically involve more complex multi-service integrations and detailed prompts.

• Free: Available on all plans — great starting points for common outcomes.
• Pro: Require an active Pro subscription — designed for production-grade, multi-service architectures.

Using a Blueprint

1. Browse & Select

Open the Use Cases library and click on any card to see the full details — the prompt, recommended agent, and any required services.

2. Click "Use this"

The "Use this" button takes you to the Task Form with everything pre-configured:

• Prompt — filled with the blueprint's proven prompt text.
• Agent — automatically set to the recommended AI agent (e.g., Claude).
• Model — automatically set to the recommended model (e.g., Sonnet).
• Services — if the blueprint requires external services (Supabase, Stripe, etc.), those are highlighted so you know which API keys to add.

3. Configure API Keys (if needed)

Some blueprints require external services. The detail page lists any required environment variables (e.g., SUPABASE_URL, STRIPE_SECRET_KEY). Make sure you've added those keys in your User Settings → API Keys section before running the task.

4. Submit & Watch

Click the submit button and the agent takes over — executing the blueprint in a sandboxed environment, generating code, and opening a PR when done.

Bookmarking

Save blueprints you want to revisit later:

1. Click the bookmark icon (🔖) on any use case card or detail page.
2. Your bookmarks are saved to your account and sync across devices.
3. Toggle the "Bookmarks" filter in the library sidebar to quickly find your saved blueprints.

Bookmarking requires a signed-in account.

Sharing

Every use case has a shareable URL. Click the share button on any card or detail page to:

• Copy the link to your clipboard.
• Use the native share dialog on mobile (iOS/Android).

Share links include rich previews (title, description, image) when pasted into Slack, Discord, Twitter, etc.

Service-Powered Blueprints

Some blueprints come pre-wired with external service recommendations. These are displayed on the detail page under "Required Services" and "Required Environment Variables".

Examples:

Blueprint	Services	Key Env Vars
Stripe Checkout Flow	Stripe	STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET
Supabase Auth Dashboard	Supabase	SUPABASE_URL, SUPABASE_ANON_KEY
AI Content Pipeline	OpenAI, Pinecone	OPENAI_API_KEY, PINECONE_API_KEY

When you click "Use this" on a service-powered blueprint, the required services are passed to the task form so you can see exactly what needs to be configured.

How It Works Under the Hood

Each use case is defined as a static blueprint in the platform. When you click "Use this":

1. The blueprint's prompt, agent, model, and services are encoded as URL parameters.
2. The Home page reads those parameters and pre-fills the Task Form.
3. You review, add any missing API keys, and submit.
4. The agent executes the prompt in a sandboxed environment with full access to your selected repository.

Bookmarks are stored in our database tied to your user account, so they persist across sessions and devices.

Tips

• Start with a Free blueprint to see how the flow works before diving into Pro.
• Customize the prompt — blueprints are starting points, not rigid scripts. Add your own requirements.
• Check "Required Environment Variables" on the detail page before launching a service-heavy blueprint.
• Bookmark frequently — build a personal library of your go-to outcomes.