780 reviewed prompts.
A way of working for any code change: plan first, read before editing, change only what is needed, test, check security basics and summarise. Use when writing, fixing or refactoring code.
Writes readable, correct SQL for your schema and dialect, or diagnoses a slow query from its plan and proposes specific fixes. Use it for reports, data pulls and query performance problems.
Maps which regulations likely apply to a product in its target markets and turns them into a prioritised compliance roadmap with owners, evidence, and questions for counsel. Use before entering a regulated market or launching a regulated feature.
Turns a short scene idea into a six-panel storyboard plan with shot type, camera angle, action, emotion and transition for each panel. Use it before sketching, commissioning art or briefing an illustrator.
Reviews pasted bank or card transactions to find top payees, recurring charges, unusual items and ways to save. Use when checking your own or your small business statements monthly.
Ports code from one language to another using the target language's own idioms, and lists behavior differences to test. Use it when migrating or learning a new language.
Plans how to attract partners or backers for a small business idea when you cannot offer much security or ownership. Use when you need capital and want a clear, honest pitch and a fair deal structure to discuss.
Creates a slide-by-slide pitch deck outline with headline, content and speaker notes, and flags where your evidence is thin. Use before an investor meeting or when sharpening a funding story.
Turns a list of software dependencies and their licenses into a ranked list of licensing risks and fixes, based on how you ship. Use it before a release, customer questionnaire or due diligence review.
Turns a feature idea into a testable specification: requirements with MUST/SHOULD/MAY, Given/When/Then scenarios, explicit out-of-scope items, small delivery phases and a validation checklist. Use it before handing work to developers.
Defines user-focused reliability indicators, realistic targets, error budgets, burn-rate alerts and dashboards for a service. Use it when setting up on-call or when alerts are too noisy to trust.
Turns a technical description into a structured invention disclosure: problem, prior approaches, the new solution, embodiments and candidate inventive points. Use it to prepare a handover for a patent attorney or an internal IP review.
