780 reviewed prompts.
Explains any named algorithm in plain language with the main idea, a worked example, cost and common pitfalls, matched to your experience. Use it when you are learning or need to explain one to a teammate.
Compares an old and new API specification and writes a front-end focused change summary with breaking changes, new fields and migration steps. Use when a backend team ships a new spec version.
Turns rough testing notes into clear, reproducible bug reports with steps, expected and actual results, severity and suggested checks. Use it after a test session so developers can act without follow-up.
Splits a list of players into fair teams using skill ratings, fixed roles and preferences, then explains the balance. Use it for weekly sports games, classroom groups, game nights or workshop teams.
Runs a structured interview that surfaces gaps and trade-offs in a draft spec, then writes the finished specification. Use it when a rough spec needs to become something others can build from.
Converts a task you repeat often into a well-scoped skill: a name, a 'Use when' description that triggers reliably, step-by-step instructions, output shape, and test requests. Use it when building a team skill library.
Plans the smallest throwaway prototype, logic or visual, that settles one open design question, with cases to try and how to judge the result. Use before committing to a design.
Finds the weak spots in a prompt your team reuses, builds a small set of test inputs with pass checks, and proposes a minimal revision. Use when a saved prompt gives inconsistent results.
Converts a task you repeat often into a focused, reusable skill: when to use it, step-by-step method, checks and output shape. Use when you keep re-explaining the same process to an assistant.
Reviews a schema migration for production risks such as long locks, data loss and breaking running code, and proposes a safer rollout. Use before shipping any change to a live database.
Reviews code or a system design you own for security weaknesses, including web, API and AI-feature risks, with severity, impact, fixes and how to verify each fix. Use it before a release or a design sign-off.
Reviews an executive's upcoming calendar and request backlog against their priorities and recommends what to keep, delegate, shorten, or decline, with draft replies. Use for weekly planning by executives or the people who support them.
