​
Welcome to the prompt library

This is your creative shortcut. Here, you’ll find a collection of tested, reusable prompts designed to help you move faster inside Rocket.

Think of these as templates. You can copy them as-is or adapt the details for your own project. Each one is purpose-built for a specific job - from starting a new project, to fixing tricky bugs.

We keep things simple and direct. The goal is always the same: get great results without overthinking the wording.

​
Starting a new project

Kick off a new app by describing what you’re building, what it should do, and where to begin.

When to use: At the beginning of your build when you want to describe the big picture and help Rocket lay the foundation.

How to use it: Describe what kind of app you’re making, what it should do, and where to begin. If you’re using any services like Supabase or Stripe, include those upfront.

Examples:

Create a task management app which includes project dashboards, due dates, and task assignment. Start with the dashboard layout.

​
Designing or restyling screens

Improve layout, spacing, and visual polish without changing how your app works.

When to use: When you want to improve the look of a screen without changing how it behaves.

How to use it: Be clear about what should stay the same. Focus on spacing, layout, color, or visual tone.

Examples:

Improve the visual design of this screen. Keep all logic the same. Focus on layout, spacing, and a more modern look.

If it’s a visual-only update, say so. Example: “Don’t change how it works - just improve the layout.”

​
Making things responsive

Make sure your UI adapts across mobile, tablet, and desktop without breaking layout or flow.

When to use: When your layout needs to work across all screen sizes - especially mobile.

How to use it: Say you want mobile-first design. Ask Rocket to resize, stack, or simplify layouts as needed.

Examples:

Make this layout responsive. Stack elements vertically on mobile, and add spacing so everything stays readable.

​
Workflows

Handle everything from user actions to publishing in a way that keeps your app flowing smoothly.

When to use:
Any time you’re defining how things flow - whether it’s inside your app (user actions), or around your app (team collaboration, testing, or deployment).

How to use it:
Be clear whether you’re describing user-facing logic (like a submit button) or project-level setup (like GitHub). Rocket can help automate both.

​
App logic workflows

Examples:

When a form is submitted, validate it, save the data, and show a confirmation message.

​
Project workflows

Examples:

Connect this project to GitHub and set up automatic preview deployments for pull requests.

If you’re working on logic that users will interact with, describe triggers and expected behavior.
If you’re working on project structure or processes, describe the outcome and tools involved.

​
Editing or refactoring

Clean up messy code, improve readability, and keep your logic intact.

When to use: When you want to clean up existing code or reorganize a screen.

How to use it: Tell Rocket what to keep the same and what to clean up.

Examples:

Refactor this layout. Keep the same output, but simplify the structure, reduce duplication, and add helpful comments.

​
React development

Use React-specific patterns and tools to build scalable, maintainable, modern components.

When to use: When you want Rocket to build or refactor something React-specific components, hooks, or patterns.

How to use it: Describe the structure, desired behavior, and any libraries or tools to use (e.g., react-hook-form, React Query, or Framer Motion).

Examples:

Create a reusable `<component_name>` component with props for `title`, `description`, and an optional icon. Use TypeScript and apply Tailwind styling.

Mention any tools or libraries you want used - like React Query, or Tailwind. Rocket adapts to them automatically.

​
Writing help, onboarding, or guides

Write simple, clear documentation or walkthroughs that guide your users through your product.

When to use: When building support content, onboarding experiences, or walkthroughs inside your app.

How to use it: Say who it’s for and what the guidance should cover - like a screen, flow, or feature.

Examples:

Create a help page for how to use `<page_name>`. Include a title, intro, and 3–5 steps.

​
Planning and scoping

Break big ideas into smaller steps so you can build confidently and stay aligned.

When to use: When a task feels big, unclear, or needs to be broken down first.

How to use it: Ask Rocket to outline the required steps: frontend, backend, logic before building anything.

Examples:

Plan the steps to add a notification system for overdue items. Don’t implement yet—just outline.

​
Locking or limiting scope

Make sure Rocket focuses on one area without touching anything else in your app.

When to use: When you want Rocket to only update one screen, component, or file and leave the rest untouched.

How to use it: Say exactly where Rocket should focus and what to skip.

Examples:

Only update `<screen_name>`. Do not change anything in the auth flow or settings screen.

Repeating what Rocket should avoid is helpful especially across multiple prompts in the same session.

​
Testing & error handling

Add smart, helpful feedback for users when things go wrong, or prevent issues before they happen.

When to use: When you want to add resilience, surface errors cleanly, or improve reliability in general.

How to use it: Ask Rocket to show fallback states, retry logic, or validation behavior for common failure points.

Examples:

Add loading and error states to `<page_name>`. Show a spinner while loading, and a message if data fetch fails.

​
Need something more specific?

This library grows as Rocket learns. If there’s a use case missing or something you’d love a prompt for, we’re listening.

We’re always expanding this library. Got an edge case or niche prompt that works well? Share it with us - we’d love to include it.

Email us at support@rocket.new.