780 reviewed prompts.
Designs a clear, validated tool (function) definition that AI assistants can call reliably: naming, parameters, field order, output and error shapes, safety rules and example calls. Use it when connecting an assistant to your own APIs.
Produces a clear sitemap, section purposes and page priorities for an institution or organization website, based on its audiences and goals. Use it before briefing a designer or building a new site.
Rules for designing web pages and interfaces that look deliberately made rather than template-generated: varied structure, honest content, consistent design tokens and a solid mobile layout. Use when creating or reviewing landing pages, sites or UI mockups.
A way of working for any change that touches user-facing text. Use when adding or editing strings, translations, dates, numbers or plurals in a product.
Rewrites a rough coding request into a structured brief with goal, context, constraints, out-of-scope items and a testable done condition, ready to hand to an AI coding assistant or a developer.
Diagnoses what makes working code hard to change and lays out small, low-risk refactoring steps with a safety net of tests and a before/after example. Use before cleaning up a messy module.
Reviews smart contract code for security flaws, risky admin powers and wasteful gas use, with exploit scenarios, fixes and tests to add. Use it before an external audit or any deployment that holds funds.
Critiques a product requirements draft or one-pager, ranking its weakest points, listing missing evidence and suggesting the questions to answer before building. Use before committing engineering time.
Reviews container orchestration manifests or deployment configs for reliability, security and cost problems and returns prioritized fixes with corrected snippets. Use before a production rollout or during a platform audit.
Audits a web page's code or test report for loading speed, accessibility, search basics and security hygiene, ranks issues by user impact and gives before/after fixes plus a pre-release checklist. Use it before launching or redesigning a page.
Designs a reliable data pipeline from named sources to an analytics-ready layer, covering layers, rerun safety, schema changes, quality checks, monitoring and backfills. Use when planning a new pipeline or reworking a fragile one.
Turns a rough game mechanic idea into a buildable spec: purpose, player fantasy, inputs and outputs, how it fits each gameplay loop, tuning values, edge cases, onboarding and playtest questions. Use before handing a mechanic to engineers or artists.
