> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rocket.new/llms.txt
> Use this file to discover all available pages before exploring further.
# Prompts for developers
> Rapid prototypes, API integrations, and custom code patterns with Rocket.new.
export const LlmsDirective = () =>
For the complete documentation index, see llms.txt.
For a lightweight markdown version of this page, append .md to the URL.
;
Copy-paste prompts for developers - from spinning up prototypes and integrating APIs to writing custom logic and debugging. Each prompt tells you which task type to use and what to expect.
Replace the placeholder details (in brackets) with your own endpoints, data schemas, and technical requirements.
## Rapid prototyping (Build)
### Full-stack CRUD app
**Task type:** Build
```plaintext wrap theme={null}
Build a full-stack CRUD app for managing [resource - e.g., invoices, projects, inventory items]. Include: a data table with sorting, filtering, and pagination. A form for creating and editing records. A detail view for each record. Delete with confirmation dialog. Connect to Supabase for the database. Add authentication so each user only sees their own records.
```
**What to expect:** A complete data management app with auth, CRUD operations, and a polished UI.
***
### API dashboard
**Task type:** Build
```plaintext wrap theme={null}
Build an API dashboard that displays data from [your API endpoint]. Show key metrics as cards at the top (total count, active count, revenue, growth rate). Below, add a data table with the full dataset - include columns for [list your columns]. Add a search bar and filters for [filterable fields]. Include a chart showing [metric] over time. Refresh data every 60 seconds.
```
**What to expect:** A real-time dashboard connected to your API with metrics, charts, and a data table.
***
### CLI tool web interface
**Task type:** Build
```plaintext wrap theme={null}
Build a web interface for a command-line tool. Users input parameters through a form: [list parameters with types]. When they click "Run," the app calls a server-side API route that executes the logic and returns the result. Display output in a terminal-style panel. Include a history of previous runs in a sidebar.
```
**What to expect:** A web wrapper around command-line functionality with a clean input form and terminal-style output.
## API integrations (Build)
### REST API integration
**Task type:** Build (iterate on existing task)
```plaintext wrap theme={null}
Integrate the [Service Name] API into my app. The base URL is [api endpoint]. I need to: fetch [data type] from GET /[endpoint], create new records via POST /[endpoint], and update records via PUT /[endpoint]/[id]. Use the API key from environment variables. Add error handling for rate limits (429), unauthorized (401), and server errors (500). Display the data in [describe the UI - table, cards, list].
```
**What to expect:** A working API integration with proper error handling and data display.
***
### Webhook handler
**Task type:** Build (iterate on existing task)
```plaintext wrap theme={null}
Create a webhook endpoint at /api/webhooks/[service] that receives POST requests from [service name]. Verify the webhook signature using the secret from environment variables. Handle these event types: [event 1] - [action to take], [event 2] - [action to take], [event 3] - [action to take]. Log each event and return a 200 response. If verification fails, return 401.
```
**What to expect:** A secure webhook handler with signature verification and event routing.
***
### OAuth integration
**Task type:** Build (iterate on existing task)
```plaintext wrap theme={null}
Add [Provider - e.g., Google, GitHub, Slack] OAuth login to my app. When a user clicks "Sign in with [Provider]," redirect them through the OAuth flow. On callback, create or update the user in Supabase and start a session. Display the user's name and avatar in the header after login. Add a sign-out button.
```
**What to expect:** A complete OAuth sign-in flow with session management and user display.
## Custom code and logic (Build)
### Custom server-side logic
**Task type:** Build (iterate on existing task)
```plaintext wrap theme={null}
Add a server-side API route at /api/[route-name] that: accepts a POST request with [describe the payload], validates the input (return 400 for invalid data), processes the data by [describe the business logic], stores the result in Supabase, and returns the processed result as JSON. Add rate limiting of [N] requests per minute per IP.
```
**What to expect:** A production-ready API route with validation, business logic, storage, and rate limiting.
***
### Scheduled job / cron
**Task type:** Build (iterate on existing task)
```plaintext wrap theme={null}
Add a scheduled job that runs every [interval - e.g., hour, day, week]. The job should: query [data source] for [condition], process the results by [describe logic], send a notification (email or webhook) if [threshold or condition] is met, and log the job execution with timestamp and result count.
```
**What to expect:** An automated background job with logging and notification triggers.
## Technical research (Solve)
### Architecture decision
**Task type:** Solve
```plaintext wrap theme={null}
I'm building a [describe your app] and need to decide between [Option A] and [Option B] for [specific technical decision - e.g., real-time updates, state management, database design]. Compare both options on: performance, complexity, scalability, cost, and developer experience. Which would you recommend for a team of [size] building a [type of product]?
```
**What to expect:** A structured comparison with a clear recommendation based on your constraints.
***
### API evaluation
**Task type:** Solve
```plaintext wrap theme={null}
Evaluate [API/Service A] vs [API/Service B] for [use case]. Compare on: pricing (include free tier limits), rate limits, SDK quality, documentation, reliability, and feature coverage for [specific features you need]. Which is better for a [describe your scale and use case]?
```
**What to expect:** A detailed technical comparison with pricing breakdowns and a recommendation.
## Monitor with Intelligence
Intelligence can monitor technical dependencies and competitor products after a one-time setup. Select **Intelligence** from the bottom of the home screen input area.
### Dependency and tech monitoring
Configure the wizard to watch your technical ecosystem:
* **Your context:** Describe your tech stack and what kinds of changes (breaking APIs, major version bumps, security patches) you need to know about
* **Competitors to track:** Add companies whose APIs, SDKs, or developer tools you depend on, using their main website URLs
* **Signal categories:** Select Product updates and Blogs to catch changelog and documentation updates
* **Frequency:** Weekly
**What to expect:** Signals about major releases, deprecations, and security patches from the platforms you depend on, surfaced in your Intelligence dashboard.
## What's next?
Market research, landing pages, and competitive intel.
Describe apps and features more effectively.
Edit generated source code directly.
Full guide to connecting APIs in Rocket.