Best PromptsCode generation prompts
[Attach the screenshot or design image, then use this prompt:] Build this UI as [FRAMEWORK: React + TypeScript / Vue / Svelte / plain HTML] using [STYLING: Tailwind / CSS modules / styled-components / our design system, described below]. Our existing conventions and tokens: """ [PASTE A SIMILAR COMPONENT FROM OUR CODEBASE, PLUS OUR SPAC
Build UI From a Screenshot
Turn a design screenshot into accessible, responsive component code that matches your existing stack instead of inventing a new one.
I want to implement this feature: [DESCRIBE THE FEATURE: the user-visible outcome, not the implementation] Constraints: [e.g. "no new dependencies", "must work with our existing auth", "ship behind a feature flag"] Work in two phases. Do NOT write or edit any code in phase 1. **Phase 1: Explore and plan:** 1. Read the relevant parts of
Plan-First Feature Implementation
Make an AI coding agent explore and plan before touching code: file-level plan, risks, and edge cases; implementation gated on your approval.
Write SQL to answer my question. My schema (tables, columns, types, plus 2-3 sample rows per table if available; samples resolve ambiguity better than descriptions): """ [PASTE CREATE TABLE STATEMENTS OR SCHEMA DUMP] """ Dialect: [POSTGRES / MYSQL / SQLITE / BIGQUERY / SNOWFLAKE] The question, in plain English: [WHAT YOU WANT TO KNOW, e
Text to SQL
Turn a plain-English question into correct SQL: schema-grounded, dialect-aware, edge cases handled, and the query explained back.
Write a regex for me. What it should match: [DESCRIBE THE PATTERN + PASTE 3-5 REAL STRINGS THAT MUST MATCH] What it must NOT match: [PASTE 3-5 STRINGS THAT LOOK SIMILAR BUT MUST BE REJECTED: this is where most regexes fail] Where it runs: [JAVASCRIPT / PYTHON / GO(RE2) / PCRE / grep: flavors differ on lookbehind, named groups, unicode] T
Regex Builder
Get a regex with match/reject test cases, a piece-by-piece explanation, ReDoS check, and a straight answer when regex is the wrong tool.
Write a production-ready Dockerfile for my app. Stack: [LANGUAGE + VERSION + FRAMEWORK, e.g. "Node 22 / Next.js", "Python 3.12 / FastAPI", "Go 1.23"] How it builds and starts: [BUILD COMMAND + START COMMAND + PORT] Package manager + lockfile: [e.g. "pnpm with pnpm-lock.yaml", "uv with uv.lock"] Runtime needs: [NATIVE DEPS, ENV VARS EXPEC
Production Dockerfile
Write a production Dockerfile with multi-stage builds, layer-cache ordering, non-root user, health check, and no secrets in layers.
Write a GitHub Actions workflow for my project. What it should do: [e.g. "typecheck + test + lint on every PR, build and deploy on merge to main"] Stack: [LANGUAGE/RUNTIME + VERSION, PACKAGE MANAGER, TEST/BUILD COMMANDS] Deploy target, if any: [WHERE + AUTH METHOD: OIDC preferred over long-lived secrets] Repo facts: [MONOREPO? / TYPICAL
GitHub Actions Workflow
Generate a CI workflow with the practices AI usually skips: SHA-pinned actions, least-privilege permissions, caching, timeouts, and concurrency.
Give me a shell command for this task: [TASK, e.g. "find every file over 100MB modified in the last week, excluding node_modules"] My environment: [macOS / Linux / Windows (WSL or Git Bash)], shell: [zsh / bash / don't know] Format the answer as: 1. THE COMMAND: one pasteable line (or two clear commands if that's more readable than one
Plain English to Shell Command
Turn a plain-English task into a shell command with a flag-by-flag explanation, a blast-radius warning, and a dry-run first for anything destructive.
Turn my app idea into a spec for an AI app builder ([v0 / Lovable / Bolt / Replit]). Vague ideas produce demo-ware: plausible screens wrapped around a core loop that doesn't work. This spec's whole job is to prevent that. The idea: [2-3 SENTENCES] Who it's for: [THE USER, and the moment they'd reach for it] The one thing that must work:
PRD for AI App Builders
Turn an app idea into a build spec (pages, data model, edge states, scope cuts) then compress it into one paste-ready prompt for builders like v0, Lovable, and Bolt.