AI Prompt Library

A curated index of prompts and prompting techniques circulating in the AI community. Each entry credits its source where we have one, notes when we have adapted or rewritten it, and explains what it is for, when to use it, and what output to expect. Search and filtering run entirely in your browser.

What is in the library

48 prompts across 19 categories. Each entry gives the prompt itself plus what it is for, when to use it, and the output to expect. Search and category filtering happen in your browser — nothing is sent to a server.

Attribution: 38 of 48 entries name the source they were curated from; 10 have no creator recorded in our archive and say so. Sources are credited in plain text — we hold no verified public profile URLs, so we link none.

Coding Agents

  • Senior Engineer Codebase Audit — Have the model join an unfamiliar codebase like a senior engineer, reverse-engineer it, and surface architecture/quality problems without changing behavior. Curated from STICS
  • Production Debugging Engineer — Get root-cause debugging discipline: trace the real cause of a failure, enumerate edge cases, and propose the most robust fix rather than a guess. Curated from STICS
  • AI Technical Lead Mode — Make the model behave like a tech lead — ask clarifying questions and challenge decisions before writing code — instead of a code generator. Curated from STICS
  • Performance Optimization Engineer — Turn a vague "it feels slow" complaint into a measured diagnosis and a ranked list of fixes, instead of speculative micro-optimisation. Adapted from material by STICS
  • Clean Architecture Refactor — Restructure code that works but has become hard to change, without altering its behaviour. Adapted from material by STICS
  • Senior Frontend Engineer Review — Get a frontend review that covers accessibility, state and rendering behaviour rather than only styling. Adapted from material by STICS
  • Deployment Readiness Engineer — Find what will break on deploy — configuration, secrets, migrations and rollback — before it breaks in production. Adapted from material by STICS
  • End-to-End Test Generator — Generate browser tests that cover the paths a user actually takes, including the ones that fail. Adapted from material by @coding_dev_

Claude Code

  • "A Reviewer Will Check Your Output" (CLAUDE.md line) — Add a single line to CLAUDE.md telling the agent its work will be reviewed, so it self-scrutinizes for correctness, edge cases, and completeness before finishing. Adapted from material by @abhijitwt
  • Plan Before Coding — Stop the agent from jumping straight into a large implementation — make it brainstorm/plan and get approval first (no special mode needed). Adapted from material by Boris Cherny
  • Git-History Explainer — Use the model's git access to explain why code is shaped the way it is — when/why/by whom something was introduced and which issues it links to. Adapted from material by Boris Cherny
  • Write the Spec Before the Code — Force a coding agent to agree on what it is building before it writes a line, so you review a plan instead of a thousand wrong lines. Adapted from material by @coding_dev_
  • Project Context Files for a Coding Agent — Set up the small set of project files that stop an agent re-deciding your architecture every session. Source attribution not captured in our archive.
  • Split Work Into Reviewable Commits — Turn one sprawling working-tree change into a sequence of commits a reviewer can actually follow. Adapted from material by @coding_dev_

Research Validation

  • Pressure-Test a Startup Idea Before You Build — Find every fatal flaw in a startup idea before building — core assumption, ranked failure modes, real-vs-nice-to-have, founder-market fit, and a blunt verdict. Rewritten from material curated from @evolving.ai
  • Validate the Real Problem (Must-Fix or Nice-to-Have) — Test whether an idea solves a real, paid-for problem or an invented one — with a specific early-adopter profile and non-leading discovery questions. Rewritten from material curated from @evolving.ai
  • Build Your MVP in 2 Weeks — Design the smallest product that tests the single riskiest assumption, cut everything else, and produce a day-by-day 2-week launch plan. Rewritten from material curated from @evolving.ai
  • Map Your Real Competition — Identify who you actually lose to — including the spreadsheet and the do-nothing option — rather than the companies in your category. Adapted from material by @evolving.ai
  • Find Your First Ten Customers — Produce a concrete, reachable list of first users instead of a market-size slide. Adapted from material by @evolving.ai

Business Building

  • Validate a Digital Product Line Before You Build It — Test whether a low-content or print-on-demand product idea has real demand and workable economics before producing anything. Adapted from material by Drew Huibregtse (@drewskidigital)
  • Check the Licence Before You Sell Open Source — Work out what you may actually charge for when the product is someone else's open-source project, and what you must disclose. Adapted from material by @thesocialalpha_
  • Scope and Price a Deployment Project — Turn "deploy this open-source system for a client" into a scoped statement of work with a defensible price and a clear finish line. Adapted from material by @thesocialalpha_
  • Design a Recurring Report Clients Keep Paying For — Turn a repeatable analysis into a productized retainer that stays valuable after the first month. Adapted from material by @thesocialalpha_
  • Build and Price an AI Service Catalogue — Decide which AI-enabled services you can actually deliver, and price them from delivery cost and risk rather than from someone's screenshot. Adapted from material by @researchingai

Security Review

  • Red-Team Security Audit (All Layers) — Turn the model into an adversarial security auditor that sweeps every layer of a codebase and reports findings, attack chains, and fixes in a strict format. Adapted from material by The Wize AI (@thewizeai)
  • Pre-Launch Readiness Audit (Vibe Coders) — Check a fast-built app against the four launch basics — privacy policy, OWASP, secrets hygiene, and rate limits — with evidence and the smallest fix per failure. Source attribution not captured in our archive.
  • Plan an Authorized Security Assessment — Turn a vague "can you security-test this?" into a scoped, authorized, evidence-producing engagement plan. Source attribution not captured in our archive.
  • Structure a Red-Team Engagement by Attack Surface — Organise an authorized offensive-security engagement into surfaces, objectives and evidence, so coverage is deliberate rather than ad hoc. Source attribution not captured in our archive.

Workflow Automation

  • Self-Checking Loop (Any LLM) — Make any model iterate on its own work against strict success criteria until every criterion scores 8+/10, instead of a one-shot answer. Source attribution not captured in our archive.
  • Coding Loop Spec (Test-Gated) — Give a coding agent a strict loop with a real verifier — run tests, fix the highest-impact failure, re-check — and a hard stop condition. Source attribution not captured in our archive.
  • Marketing Pipeline With Specialist Agents — Run a campaign as a staged pipeline of specialist agents instead of one long, drifting conversation. Adapted from material by @shannholmberg

Context Management

  • Wrap-Up Skill (Session → NotebookLM / Second Brain) — End a Claude session by producing a NotebookLM-import-friendly summary so the next session can pick up without re-reading the chat. Source attribution not captured in our archive.
  • Compact Conversation Skill — Summarize a long chat into a paste-ready handoff so you can continue in a fresh session without losing context (and without paying to reload the whole history). Curated from @evolving.ai

Explanation

  • Fake Constraint (Force Creative Connections) — Break out of standard framing by forcing analogies from an unrelated domain. Curated from u/naculalex
  • Pretend Auditorium (Higher-Structure Explanations) — Get better structure, emphasis, anticipated Q&A, and pacing than 'explain clearly'. Curated from u/naculalex

Seo Geo

  • SEO + GEO Auditor — Audit a site for both Google ranking and AI-search (GEO) visibility, prioritize quick wins, and output schema + llms.txt + content changes. Adapted from material by @vibha.in.progress
  • Search Console Content-Gap Analysis — Find the questions a page already ranks for but never actually answers, and turn them into sections. Source attribution not captured in our archive.

Writing Voice

  • Clone a Writing Voice From Samples — Analyse how someone actually writes, then produce new text in that voice — without the model's defaults leaking through. Source attribution not captured in our archive.
  • Strip the AI Tells From a Draft — Remove the patterns that make a draft read as machine-written, without flattening its meaning. Adapted from material by @ARTIFICIALZONE

Advisor Mode

  • Critical Advisor Mode (Anti-Sycophancy Contract) — Reframe an LLM from polite assistant into smarter-than-you advisor. Rewritten from material curated from STICS

Iteration

  • Version 2.0 (Not Improve This) — Force the model to treat the input as v1 that needs a sequel, not incremental polish. Curated from u/naculalex

Token Savings

  • Caveman / Concise Mode — Cut conversational-reply output tokens by ~30–50% without changing answer quality. Curated from @evolving.ai

Preprocessing

  • Document Condenser — Compress an image-heavy PDF into ~20–30% of its length before uploading to the main LLM. Curated from @evolving.ai

Continuity

  • Assumed Shared Context (Continuity Bootstrap) — Bootstrap continuity on a fresh chat without paying full history reload. Curated from u/naculalex

Stress Test

  • Fake Audience Disagreement — Force the model to defend or concede rather than re-explain. Curated from u/naculalex

Privacy

  • Personal Data Deletion Audit — Find where your personal data is exposed online and produce the actual deletion requests, in priority order. Adapted from material by @vibeeval

Personal Finance

  • Audit Your Own Mutual Fund Portfolio — Read your own fund statement properly: what you hold, what overlaps, what it really costs, and what the returns actually say. Adapted from material by @stockizen_research

Social Content

  • Build a Short-Form Content System, Then Test the Claim — Design a repeatable short-form content process and, in the same pass, work out what evidence would show it is actually working. Source attribution not captured in our archive.

← All free tools

From Ambimat

Ambimat AI Tools is a free tools project from Ambimat.