Software prompts
Prompts about software. Start with an essential: it asks a few questions, then gets specific.
Essentials
Review a pull request
Reviews a pull request diff for correctness bugs, risky changes and missing tests, and returns ranked findings. Use before merging a PR, branch or diff.
review-pull-requestBuild a feature
Builds a feature from an idea rather than a full spec, asking the few questions that change the design, proposing a small plan, then implementing and testing it. Start here for new features.
build-a-featureFix a bug
Fixes a bug from a symptom or error, asking what happens, what should happen and how to trigger it if missing, then reproduces it, fixes the cause and proves it. Start here for any bug.
fix-a-bugDesign a relational database schema
Designs a relational schema from requirements and access patterns, with keys, constraints, types, indexes and DDL. Use when starting a new service or feature that stores data.
design-database-schemaImprove a prompt
Diagnoses why a prompt gives weak or inconsistent results and rewrites it with clear context, task, constraints and output format while keeping its intent. Use on any prompt for any AI assistant.
improve-promptWrite an implementation plan
Reads the codebase and writes an ordered implementation plan in small verifiable steps, with files to touch, tests, rollout and risks. Use before coding any change that spans several files.
write-implementation-planWrite user stories
Turns a feature description into small, independent user stories for specific users, each with acceptance criteria, and splits stories that are too big. Use when preparing a backlog.
write-user-storiesAssistant setup track
Sets up a personal or team AI assistant in gated steps - interview, custom instructions, knowledge files, tests and refinement - so it behaves well on real tasks before anyone relies on it.
assistant-setup-trackCheck an app for security problems
Runs a first security pass over an app, mapping what is exposed and checking the flaws that most often get apps breached, then ranks the fixes. Use to find out if your app is reasonably safe.
check-app-securityStart here 26
The general, start-from-zero entry for a need in this category: it works from a blank start, asks for what it needs and hands off to the specific entries. Example: Plan a trip.
- Design a system's architecture
Designs the architecture for a new system or a big new part of one, starting from the requirements that drive it, with components, a diagram, key decisions and risks. Use when starting to design.
- Explain a piece of code
Explains a piece of code step by step at the reader's level, starting with what it is for, then walking through how it works with a worked example and the parts that are easy to misread.
- Fix a git problem
Works out what state your repository is in and gives the safest commands to get where you want, with a backup first and a check after. Use when git confuses you or you are stuck mid-task.
- Learn prompting basics
Teaches prompting basics interactively on the learner's own tasks, one technique at a time, with before-and-after prompts, a short exercise and feedback. For beginners to AI assistants.
- Refactor messy code
Cleans up hard-to-work-with code in small behaviour-preserving steps, pinning behaviour with tests first and fixing what blocks your goal most. Use when code is messy and you want it easier to change.
- Set up deployment for an app
Plans how an app gets from the repository to production, choosing hosting that fits, a build-test-deploy pipeline, secrets, rollback and the production basics. Use when you need to ship an app.
- Write about a technical topic
Drafts a technical post, announcement, proposal or explainer for a named audience, leading with the main point and inventing no facts. Use when you need to write about engineering work.
- Write custom instructions
Writes personal custom instructions for an AI assistant from your role, preferences and pet peeves, turning them into specific behaviours, with test prompts to check the difference.
- Write a how-to guide for one task
Writes a how-to guide for a reader who knows the basics, with a goal-named title, prerequisites, numbered steps with expected results, a verification step and links instead of tangents.
- Write unit tests
Writes unit tests that pin a unit's behaviour, covering boundaries, errors and edge inputs in the project's own test style, and proves each test can fail. Use for new or untested code.
- Concise
Shortens answers by leading with the result and cutting preamble, recaps and filler, from light trimming to bare answers. Use when you want less reading and the same substance.
- Review custom instructions
Reviews existing custom or project instructions for an AI assistant, finds conflicts, vague rules, outdated facts and missing context, and returns a tighter version with test prompts.
- Triage a production alert
Turns a firing production alert into a severity call, the safest mitigation to try first, ranked hypotheses and the next checks. Use in the first minutes of an incident or page.
- Upgrade a major dependency
Upgrades a library or framework across major versions using the official migration notes, fixes what breaks, and proves the result with before-and-after checks. Use for any breaking upgrade.
- Write a test plan
Writes a risk-based test plan for a feature or release covering scope, risks, test levels, environments, data, manual checks automation misses and exit criteria. Use before testing a release.
- Code reviewer
Reviews changes like a senior engineer who blocks only on real defects, backs every finding with a triggering input, and keeps style opinions out. Use as a reviewer persona or subagent.
- Debugger
Debugs by reproducing first, testing one hypothesis at a time and fixing root causes, never symptoms. Use as a persona or subagent for bugs, crashes and failing builds.
- Open-source maintainer
Acts as an experienced open-source maintainer who protects project scope, writes welcoming but firm replies, reviews contributions and keeps releases sustainable.
- Profile and speed up a hot path
Measures a slow operation, profiles where the time goes, and makes it faster one verified change at a time, with before-and-after numbers. Use when an endpoint, command or function is too slow.
- Investigate a suspected hack
Guides the first hours after a suspected attack, covering what to do now, preserving evidence, finding what happened, containing it and who to tell. Use when you think a system or account was hacked.
- App localisation track
Takes an English-only app to its first extra language in gated steps, from readiness scan and string extraction to formatting fixes, pseudo-localisation, translation hand-off and linguistic QA.
- Audit web accessibility against WCAG 2.2
Audits markup or components against WCAG 2.2 and reports each issue by success criterion with user impact, severity and a concrete code fix. Use before a release or a compliance review.
- Set up an open-source project
Gets a project ready to open-source, checking you may publish it, picking a licence, adding the files contributors expect and setting promises you can keep. Use when publishing a project.
- Add an AI feature to an app
Turns an AI feature idea into a buildable design, choosing the simplest approach that works and planning evals, guardrails, cost and build steps. Use when you want to add AI or an LLM to your product.
Specific 1,823
One situation, audience, tool or format inside the category. Example: Plan a road trip with children.
- Actionable
Makes any answer end in action, from one concrete next step to a prioritised checklist with owners, time estimates and a first five-minute task. Use when you need to act, not just understand.
- AI literacy coach
AI literacy coach who teaches people to use assistants well and critically - what they are good at, how they fail, how to verify outputs and protect privacy. Use for learning to work with AI.
- Analogy-led
Explains through analogies, from one everyday analogy for the hardest idea to an extended analogy carried through the answer, with explicit notes on where it breaks down.
- Beginner friendly
Adapts answers for newcomers by defining jargon, explaining why each step matters and avoiding assumed knowledge, from light glossing to full guidance. Use when the reader is new to the topic.
- Bottom line first
Puts the answer or decision first, from a one-line summary on top to a strict BLUF memo with only supporting facts below. Use for busy readers, decisions and status updates.
- British English rules
Standing rules to write in British English - UK spelling, vocabulary, date and number formats, punctuation conventions and units - while leaving names, quotes and code untouched.
- Casual
Makes any answer more conversational, from relaxed everyday wording to a chatty, friend-over-coffee voice, while keeping every fact, number and warning accurate.
- Decisive
Makes answers commit, from marking a recommended option to a single clear recommendation with the deciding reason and the condition that would change it. Still states uncertainty.
- Dyslexia-friendly
Shapes answers for dyslexic readers, from short sentences and plain words to a summary first, chunked layout, one idea per line and bolded keywords. Use when dense text is hard to read.
- Example-led
Leads with concrete examples, from one illustrative case after the explanation to an example before every rule, so readers see the idea in action before the abstraction.
- Global English
Writes for non-native readers and machine translation, from dropping idioms to controlled English with short literal sentences, one term per concept and no cultural references.
- Metric units rules
Standing rules to use metric and SI units by default, convert only when asked or when a source used other units, keep sensible precision and format numbers and unit symbols correctly.
Advanced 399
Expert or deep work that assumes the user can judge expert output. Example: Plan croissant lamination.
- Technical
Raises the technical depth of any answer, from precise terminology to expert density that assumes domain knowledge, skips basics and states mechanisms, units and limits exactly.
- Data engineer
Acts as a data engineer who designs for idempotency, backfills and observability, treats schemas as contracts with their consumers, and asks who depends on each table before changing it.
- Machine-learning engineer
Acts as a machine-learning engineer who starts from the data and a baseline, insists on evals and reproducibility, and distrusts any gain a simpler model explains.
- Software architect
Acts as a pragmatic software architect who designs from requirements and constraints, names trade-offs and failure modes, and keeps designs as simple as the problem allows.
- Design a data pipeline
Designs a batch or streaming data pipeline sized to stated volumes, covering sources, schedule, idempotency, late data, backfills and monitoring. Use before building or replacing a pipeline.
- Design a star schema
Designs a dimensional model from the questions analysts need answered: business processes, grain, facts, dimensions, slowly changing dimension types and DDL. Use when building a warehouse layer.
- Plan an incremental migration
Plans a framework, platform or system migration as small reversible phases using the strangler fig pattern, with data strategy, verification and rollback per phase. Use instead of a big-bang rewrite.
- Review a system design
Reviews a design document or proposal for failure modes, scaling limits, data and consistency risks and operability gaps, and returns ranked findings. Use before a design review or before building.
- Triage a vulnerability report
Triages an external vulnerability or bug bounty report by checking the claim, rating severity with CVSS, deciding valid, duplicate or out of scope, and drafting the reply. Use for security inboxes.
- Performance engineer
Acts as a performance engineer who profiles before optimising, changes one thing at a time and reports gains with numbers and variance. Use for latency, throughput or memory work.
- Staff engineer
Acts as a staff engineer who scopes ambiguous cross-team problems, writes the doc that unblocks a decision, weighs organisational cost with technical cost and grows other engineers.
- Untangle circular dependencies
Finds circular dependencies between modules and plans breaking each cycle with interfaces, inversion or extraction in safe steps. Use when import cycles cause build errors or tangled code.