780 reviewed prompts.
Produces a practical plan for building a web app that works well on phones, tablets and desktops, covering layout, navigation, accessibility and performance. Use it at the start of a build or redesign.
Produces a first-pass FMEA table with ratings, ranked risks, recommended actions and listed assumptions. Use it to prepare a design or process risk review before the team workshop.
Produces a readable set of unit tests with a coverage map from a Python snippet and its intended behavior. Use it when adding tests to untested or legacy code.
Keeps answers short and dense: no filler, pleasantries or hedging, while preserving every technical detail. Use when the reader wants fast, skimmable replies to technical or operational questions.
Produces a clear music video concept with story, visual style, scenes and a realistic production scope. Use when pitching a video for a song to an artist, label or director.
Use when pairing with someone on code or architecture: asks before building on ambiguous requirements, explains choices briefly, admits uncertainty, and tells the user directly when their approach has a problem.
Answers a question about how a codebase behaves by tracing the actual code paths, separating facts from guesses and naming the check that would confirm it. Use for debugging, code review or learning unfamiliar code.
Extracts a table from a screenshot or scanned page into clean CSV text and lists any cells it could not read with confidence. Use when you need data from a picture or PDF page in a spreadsheet.
Reviews a small business's expenses and cash position to find savings, ordered by effort and impact, with questions to ask an accountant. Use it before budgeting season or when margins feel tight.
Produces a ranked list of likely causes and concrete fixes when a single-page web app shows a blank screen in production but works locally. Use it right after a failed or odd deploy.
Writes a thorough set of unit tests for a class that handles create, read, update and delete requests, covering normal use, bad input and permissions. Use when you need reliable tests before changing existing code.
Standing guidance for reviewing and rewriting version-control commit messages so history stays readable. Use when writing a commit for a set of changes or cleaning up weak messages before a merge.
