Open Prompts
Submit a prompt
Coding

Database schema design assistant

Describe a feature in plain language along with your database engine, expected scale, and existing tables to get a second opinion before writing migrations that are painful to undo. Returns proposed tables, keys, and indexes with the reasoning behind each normalization or denormalization decision, flags which constraints belong at the database level instead of application code, and stress-tests the design against one likely future change.

Prompt
Design a database schema for the following feature.

Feature description:
{{description}}

Database engine:
{{db_engine}}

Expected scale:
{{row_counts}}

Existing related tables (if any):
{{schema}}

Provide:
1. Proposed tables with columns, types, and primary/foreign keys.
2. Normalization decisions, and any deliberate denormalization with the reason for it.
3. Indexes needed for the described query patterns, and why each one earns its cost.
4. Constraints (uniqueness, not-null, checks) that should be enforced at the database level rather than in application code.
5. One likely future change to the feature, and how well this schema would absorb it.
Download .md

Variables

Related prompts

Coding

Structured Feature Implementation Request

Fill in the feature you want built, the language, and up to three specific requirements, and get an implementation request structured enough that nothing important gets skipped. It explicitly asks for error handling, edge cases, performance, and framework best practices to be considered up front, and instructs the output to keep existing comments intact and explain its own logic inline.

Coding

Git commit message writer

Takes a pasted diff plus a short note on why the change was made, and returns a commit message ready to paste into git: an imperative summary line under 72 characters, followed by an optional body covering rationale and tradeoffs. It skips line-by-line narration in favor of describing intent and impact, and flags diffs that look like they're bundling unrelated changes that should be split into separate commits.

Coding

Regex generator and explainer

Describe a matching pattern in plain language, list a few strings it must reject, and name the language or regex engine, and get back a working regular expression. It comes with a token-by-token breakdown of what each part does, a callout of edge cases it might mishandle like unicode, empty strings, or catastrophic backtracking, and three example strings that should match plus three that shouldn't.