Tag
A lot of repetitive work can be handed off with the right prompt. This set covers breaking tasks into steps, documenting processes, and keeping projects moving without extra manual effort.
19 prompts · page 1 of 3
Describe a feature in plain language along with your database engine, expected scale, and existing tables to get a second opinion before writing migrations that are painful to undo. Returns proposed tables, keys, and indexes with the reasoning behind each normalization or denormalization decision, flags which constraints belong at the database level instead of application code, and stress-tests the design against one likely future change.
Takes a pasted diff plus a short note on why the change was made, and returns a commit message ready to paste into git: an imperative summary line under 72 characters, followed by an optional body covering rationale and tradeoffs. It skips line-by-line narration in favor of describing intent and impact, and flags diffs that look like they're bundling unrelated changes that should be split into separate commits.
Describe a matching pattern in plain language, list a few strings it must reject, and name the language or regex engine, and get back a working regular expression. It comes with a token-by-token breakdown of what each part does, a callout of edge cases it might mishandle like unicode, empty strings, or catastrophic backtracking, and three example strings that should match plus three that shouldn't.
Enter your niche and receive a complete 5-email welcome sequence for new subscribers, moving step by step from a quick win to a story or insight, social proof, a resource share, and finally an offer invitation. Each email comes with its own subject line and full body copy, written to stay warm and valuable so the pitch in email five never feels rushed.
Paste in a published blog post and get a week of repurposed content mapped out around its core idea. - Assigns a post format for each of the 7 days (tweet, carousel, short video, email) - Recommends which platform each day's post should go on - Defines the single key message to focus on that day - Avoids repeating the same format on consecutive days
Describe your current content workflow — from idea to published post — and this prompt pinpoints the three specific bottlenecks slowing it down, then suggests a concrete fix for each one using Claude, automation tools, or a process adjustment. It deliberately avoids proposing a full workflow overhaul, focusing only on fixes you could realistically try this week.
List out your current content creation workflow step by step, and this prompt reviews each stage the way a content operations consultant would, flagging where you could automate it, cut it entirely, or delegate it to someone else. It returns concrete tool or prompt suggestions per step and narrows the list down to the two or three changes likely to save the most time, rather than a wish-list of theoretical fixes.
Paste a diff or code block and get a senior-engineer-style first pass before it reaches a human reviewer. - Flags bugs, security risks, performance issues, and maintainability problems - Rates each finding Critical, High, Medium, or Low with line references and a fix - Add project conventions (e.g. "no nested ifs") for sharper, more relevant results - Run it on every PR so reviewers only spend time on what's left after the obvious stuff is caught
Paste a module or function to get documentation a new hire could actually use, not filler that just repeats function names back to you. Returns an overview, a 3-step quick start, a full API reference with examples, the most common usage patterns, and a dedicated Gotchas section covering edge cases and limitations that usually only live in one developer's head.