Prompt library

336 prompts · last added

71 results for “Intended use packaging” · page 1 of 3

  • Root Cause Analysis from Stack Trace and Logs

    Turns an error report, stack trace, and logs into ranked root-cause hypotheses. Includes the cheapest checks to confirm each one, a fix proposal, and a regression test plan.

  • Cursor Agent Bug Triage: Reproduce, Root-Cause, Fix, and Regression Test

    Guides Cursor Agent through reproducing a bug, isolating the root cause with evidence, applying a minimal diff, and adding a regression test, ending with a verification checklist and risks.

  • Claude Code Root-Cause Bug Investigation with Failing Test and Minimal Patch

    Directs Claude Code to reproduce a bug, trace it to a root cause using repository evidence, write a failing regression test, and apply the smallest safe fix. Ends with a verified diff, risks, and next actions.

  • Release Notes From Git Log Skill for Users and Developers (SKILL.md)

    A SKILL.md that writes release notes from the commits between two tags, split into a plain-language section for users and a technical changelog for developers.

  • Agent Run Post-Mortem: Trace Root Cause and Prompt or Tool Fixes

    Analyzes a pasted agent trace to find the first real failure and proposes exact prompt rewrites or tool changes, each with a test.

  • Claude Code Hook Writer: Auto-Run Lint, Typecheck or Tests After Edits

    Produces a PostToolUse hook entry for settings.json, the script it calls and a concrete procedure to test that the check runs after file edits.

  • Codex Read-Only Repo Investigation for a Bug Report

    Runs a read-only Codex investigation that maps the relevant code paths, test commands, and likely root causes for a bug report. It ends with a ranked hypothesis table and a go/no-go recommendation before any edits.

  • Implement a Scoped Feature in Copilot Agent Mode with Repo Discovery and Tests

    Guides GitHub Copilot agent mode to inspect the repository, state assumptions, plan a minimal change, implement it, and add tests. It ends with a verification report you can use to decide whether to open a PR.

  • Failing Test First Bug Fix

    Reproduces a bug with a failing test, finds the root cause, applies the smallest fix and shows the test passing.

  • Agent Tool Names, Descriptions and JSON Schemas from API Docs

    Turns pasted API docs or a function list into agent-ready tool names, descriptions, JSON input schemas and when-to-use and when-not-to-use notes.

  • Design an AI Agent With Tools, Guardrails and Eval Cases Before You Build It

    Turns an agent idea into a build-ready design: the job, the tools with their inputs and permissions, guardrails, failure handling and a set of evaluation cases to test it.

  • Pre-PR Self-Review and Pull Request Description from a Git Diff

    Has GitHub Copilot review your branch diff against the base branch, flag defects and missing tests, and draft a PR description with evidence. Use it to decide whether to open the PR or fix issues first.

  • Debug an Error From the Message and the Code Around It

    Finds the most likely cause of an error from the message and the relevant code, ranks other possible causes, and gives the smallest fix plus a way to prove it worked.

  • Edge-Case Test Suite for One Function in Your Existing Test Framework

    Writes tests for a single function that cover normal inputs, boundaries, bad input and error paths, in the test framework your project already uses.

  • Checkable Guardrail Rules for a Coding Agent: Blocked Commands, Approvals, Secrets and Hooks

    Produces a set of testable guardrail rules for your coding agent, covering blocked commands, approval gates, secret handling and hook checks.

  • Tool Permission Matrix and Function Spec for a Tool-Using Agent

    Produces a least-privilege tool inventory, function definitions, and approval rules for an agent that calls APIs or internal systems.

  • Codex CI Failure Triage: Reproduce, Classify, Fix or Hand Off

    Guides Codex through reproducing a failing CI job locally, classifying the cause as code, test, environment, or flaky, applying a minimal fix when safe, and producing an evidence-based handoff for anything it cannot resolve.

  • Cursor Incremental Dependency Migration Plan and Codemod Execution

    Plans and executes a library or framework version migration in Cursor in small, verifiable batches, with an impact inventory, rollback points, and per-batch test gates instead of one risky bulk edit.

  • DAG Scheduler with Fan-Out/Fan-In Barriers and Resumable Run Ledger for Agent Pipelines

    Guides Claude Code to build or refactor a dependency-aware DAG scheduler for agent phases, with cycle validation, bounded parallelism, join policies, retries, and an append-only run ledger so interrupted runs resume without redoing finished nodes.

  • Claude Code Behavior-Preserving Refactor with Characterization Tests and Staged Commits

    Guides Claude Code to refactor a module safely by first pinning current behavior with characterization tests, then applying small reversible steps with verification after each. Delivers a diff, risk register, and rollback plan.

  • Subagent Fan-Out Plan for a Large Codebase Migration

    Plans a big migration so an orchestrating agent can split it into independent chunks for parallel subagents, each with a clear brief, a verification command and merge rules.

  • Recurring Workflow to SKILL.md with Trigger, Steps and Verification

    Claude Code interviews you briefly about a repeated workflow and writes a complete SKILL.md with a precise trigger description, steps, supporting files and a verification step.

  • Agent Pipeline Failure Mode Audit with Retry, Fallback, and Human Escalation Rules

    Audits an existing multi-agent pipeline for failure modes and produces retry limits, fallback paths, escalation triggers, and a test plan. Supports the decision on what to harden before wider rollout.

  • Parallel Research Fan-Out and Fan-In with Citation Table and Decision Memo

    Splits a research question across parallel research agents, defines source discovery and evidence review steps, merges findings into a citation table, and produces a decision memo without claiming live browsing.

Guide

Using the library

  1. Narrow the list by type, tool or topic, or search for the task you have.
  2. Copy a prompt from its card, or open it to read it in full and fill in the blanks first.
  3. Paste it into your AI tool and check the answer against the format the prompt asks for.

Nothing that fits? Write a prompt with AI.

What is in the prompt library?

336 copy-ready prompts for productivity, writing, business and coding and more. Each one sets the role, the steps and the output format, and marks the parts you fill in with curly brackets.

Which AI tools are the prompts written for?

Most are written for ChatGPT (285), Gemini (260), Claude (217) and Midjourney (42); the number is how many prompts list that tool. Each prompt page lists its tools, and most text prompts also work in any capable chat model.

What are the highlighted blanks?

Words in curly brackets, such as {audience}, are the parts you replace with your own details. Choose “Ready to use (no blanks)” in the filters to see prompts you can paste as they are.

How are the prompts sorted?

By how often they are copied, unless you choose another order. Newest shows the latest additions first. Trending ranks prompts by copies, opens and saves over the last two weeks.

Do I need an account?

No. Every prompt is free to copy or open in your AI tool. A free account lets you save prompts to your vault.

Can I write my own prompt?

Yes. Write with AI asks what you need, builds a short form for it, and writes the prompt as you fill it in.