730 reviewed prompts.
Audits subtitle or caption text for timing errors, reading speed and line-length problems, then returns a fixed version of the problem cues. Use before publishing a video with captions.
Turns an article, notes or product update into a card-by-card carousel plan with copy, layout, alt text and caption. Use it before you open your design tool.
Asks about your project and goals, then recommends suitable open-source or free licenses with plain-language tradeoffs. Use when publishing code, writing, data or designs.
Builds an educational outlook for one or more metals or commodities from price data and news you supply, with drivers, scenarios and caveats. Use for internal briefings, not as investment advice.
Reviews how an organization stores and shares sensitive data and proposes a prioritized protection plan covering access, encryption, sharing rules and monitoring. Use when tightening data handling in a small team.
Designs how non-player characters or enemies in a game decide what to do: experience goals, decision architecture, deliberate imperfections, difficulty tuning, performance limits and playtest metrics. Use when planning AI behavior for a game.
Turns an organization's goals and audience into a website plan with page structure, key features, content needs and a phased build order. Use it when starting or redoing a website.
Turns a 3D asset or scene idea into a production plan covering look, creation route, cleanup, texturing, and delivery checks. Use it before starting a hero asset or a batch of assets.
Designs a tested, low-noise detection rule for a suspicious behavior in your own logs, with false-positive tuning, evasion considerations, a safe test plan and analyst triage steps. Use it for defensive security monitoring.
Guides a bug fix that starts with a failing test, then the smallest fix, then proof nothing else broke. Use it when you or an assistant must fix a defect without causing regressions.
Designs a spreadsheet tracker for job or internship applications with columns, status rules, reminders and a weekly review routine. Use when your search is getting hard to keep organized.
Produces an evidence-based debt register for a codebase or module: ranked findings with file references, severity and effort, top fixes, quick wins and things that only look bad. Use it to plan refactoring work.
