Build your first web page
Create a one-page HTML introduction for {{PROJECT_NAME}} with a heading, a paragraph, and an accessible link. Use only the supplied facts.
Clear goals, sensible boundaries, and a way to check the result.
35 prompt library
Create a one-page HTML introduction for {{PROJECT_NAME}} with a heading, a paragraph, and an accessible link. Use only the supplied facts.
Inspect {{PROJECT_NAME}} before editing. Identify its framework, entry points, applicable AGENTS.md, and available checks. Cite file paths. Do not edit anything.
Investigate {{ERROR}} in {{FILE}}. Reproduce it using {{STEPS}}, identify the cause, then make the smallest fix. Preserve unrelated user changes.
Build a landing page for {{PROJECT_NAME}} serving {{AUDIENCE}}. Use {{CONTENT}} and one primary call to action. Do not invent testimonials or performance claims.
Implement {{COMPONENT}} in {{PROJECT_NAME}} using existing component conventions. Define props and loading, empty, error, and success states.
Inspect the installed Next.js version and router in {{PROJECT_NAME}}. Add {{ROUTE}} following the existing architecture, metadata, and data-fetching conventions.
Add {{ENDPOINT}} to {{PROJECT_NAME}}. Reuse authentication and authorization, validate inputs, and document response and error contracts.
Plan {{CHANGE}} for {{PROJECT_NAME}}. Inspect schema and callers, prefer additive changes, and define backup, compatibility, restore, and rollout steps. Produce a plan before execution.
Integrate {{API}} with {{PROJECT_NAME}} using current official documentation. Keep credentials server-side; handle timeouts, rate limits, and invalid responses.
Map {{REQUIREMENTS}} to tests for {{PROJECT_NAME}}. Reuse existing test tools, prioritize critical behavior, and distinguish automated from manual checks.
Review {{DIFF}} in {{PROJECT_NAME}} for authorization errors, injection, secret exposure, and unsafe data handling. Report concrete findings with paths and evidence. Do not modify files.
Measure {{PAGE}} in {{PROJECT_NAME}} before changing it. Identify the largest bottleneck, propose a bounded fix, and preserve visual and interaction behavior.
Audit {{SITE}} for titles, descriptions, canonical URLs, language alternates, sitemaps, robots rules, status codes, and internal links. Do not promise rankings.
Inspect the theme and plugins for {{SITE}}. Implement {{CHANGE}} in the appropriate child theme or extension point. Preserve content, URLs, and update compatibility.
Inspect {{CSV_FILE}}, identify encoding, columns, missing values, and duplicates. Write a cleaned copy and a transformation log; never overwrite the input.
Review {{FILE}} and implement server-side validation, output escaping, and the project’s CSRF protection. Preserve the current user flow.
Implement authorization for {{RESOURCE}} in {{PROJECT_NAME}} using existing Laravel policies and authentication conventions. Deny access unless explicitly allowed.
Inspect status and diff in {{PROJECT_NAME}}. Identify changes related to {{GOAL}}, check for secrets, and propose a commit message. Do not stage unrelated files or push.
Draft a pull request for {{DIFF}}. Lead with the problem and resulting behavior, then describe tests, limitations, and rollback. Do not publish the draft.
Create a CI plan for {{PROJECT_NAME}} based on its actual build and test commands. Limit workflow permissions and avoid exposing secrets to untrusted changes.
Update the README for {{PROJECT_NAME}} using verified files and commands. Include setup, running, checks, configuration names without values, and known limitations.
Refactor {{FILE}} to reduce {{DUPLICATION}} while preserving public interfaces and behavior. Establish characterization checks before modifying it.
Review {{DIFF}} for correctness and regressions. Trace affected callers. Report actionable findings with file locations, impact, and reproducible conditions. Do not edit.
Design a script that reads {{INPUT}} and writes {{OUTPUT}}. Preserve originals, support dry-run, bound retries, and log failures without sensitive data.
Build a product-page prototype using {{PRODUCT_DATA}}. Show condition, verified specifications, included accessories, and supplied return terms. Leave unknown facts explicit.
Create a dashboard from {{SAMPLE_DATA}} for {{AUDIENCE}}. Define each metric, date range, units, and missing-data behavior. Label sample data clearly.
Review {{PAGE}} for {{AUDIENCE}}. Identify unclear value, competing actions, accessibility barriers, and unsupported claims. Propose small changes as hypotheses.
Build a quiz on {{TOPIC}} from {{SOURCE}} with answer explanations, keyboard controls, retry, and honest completion feedback.
Reconcile {{LEDGER}} with {{STATEMENT}} using supplied matching rules. Preserve originals, identify unmatched rows, and avoid inferring missing amounts. This is data processing, not financial advice.
Organize {{SOURCES}} into an index with title, date, source link, supported claim, and uncertainty. Do not fabricate citations or imply access to unread sources.
Plan migration of {{CONTENT_SET}} to {{TARGET}}. Preserve source files, map old and new URLs, retain semantic headings and links, and list redirects for review.
Turn {{IDEA}} for {{AUDIENCE}} into a specification with user flows, boundaries, inputs, outputs, acceptance criteria, and unresolved decisions. Do not start implementation.
Inspect {{DEPENDENCY}} in {{PROJECT_NAME}}, read official release and migration notes for {{TARGET_VERSION}}, and propose the smallest compatible upgrade. Preserve the lockfile workflow.
Review {{PAGE}} for semantic headings, accessible names, focus visibility, keyboard access, error messages, and contrast. Preserve the intended design.
Summarize {{PROJECT_NAME}} with objective, current files, decisions, constraints, verified checks, unresolved issues, and one next action. Redact sensitive values.
No matches. Try a different keyword or clear the filters.