Write subject lines that get emails opened and found later: specific, honest, and action-signaling. Use when the subject line decides whether your email is opened, prioritized, or…
Run a team of growth agents that designs an experiment, builds the variant, analyzes the result, and passes an ethics gate before anything ships.
Prepare for a penetration test by fixing scope, rules, and access up front, then turn its findings into tracked, verified remediation.
Determine, apply, and record sales tax or VAT correctly by jurisdiction, product type, and customer status.
Run a lab of researcher agents that search in parallel, verify sources independently, and synthesize a cited answer.
Recover revenue from failed recurring charges with retries, clear notice, and a graceful path back, without harassing customers.
Return structured problem+json errors with stable codes, retryability signals, and correlation ids. Use when standardizing API error shapes or making failures debuggable across…
Run an open source review board that gates incoming dependencies on license compatibility, sets the policy for contributing back, and requires a security review before adoption.
Choose a compression codec and level by weighing size reduction against CPU cost, and place compression where the bytes are actually scarce.
Choose between flexbox and grid by content shape and build layouts that survive real content. Use when structuring a page or component layout, or fixing overflow and alignment…
Extract the lesson from a mistake by examining the reasoning that produced it, rather than only the outcome. Use after something goes wrong, personally or as a team.
Build and ship a small site that loads fast, reads well, and can be updated, choosing the simplest stack that fits.
Reject excess work deliberately under overload so the system serves some requests well instead of failing all of them.
Get the tone of an email right: warm, professional, and matched to the reader and situation, without the coldness email invites.
Assign credit for conversions across touchpoints honestly, knowing what each model hides. Use when deciding where to spend and channels each claim the same conversions.
Operate an error budget so reliability decisions follow a written policy instead of an argument: burn-rate alerts, feature freezes, and a clear escalation path.
Decide where functions-as-a-service fit using cold-start, limit, and cost-crossover math. Use when choosing between serverless and containers, or rescuing a serverless design that…
Group related events so a burst of activity produces one message instead of twenty, with rules that stay predictable.
Pass App Store and Play review on the first attempt and recover fast from rejections. Use when preparing a mobile submission, writing store metadata, or responding to a review…
Run red-green-refactor honestly with the smallest failing test first, refusing test-after backfill dressed up as TDD.
Decide where frontend state lives and how it flows, so UIs stay predictable as they grow. Use when structuring components, adding state, or untangling prop-drilling and sync bugs.
Choose between local stdio and remote HTTP transports for an MCP server based on trust, deployment, and who runs it. Use when deciding how a server will be hosted and reached.
Layer input filtering, output validation, injection defense, and human escalation around LLM features.
Structure an email so a skimming reader gets the point, the context, and the ask in the right order. Use when an email has more than a line or two and the layout decides whether…
Build immutable, provenance-tracked artifacts promoted unchanged through environments. Use when designing a build pipeline or fixing "works in staging, breaks in prod" from…
Cut startup latency by deferring heavy imports, precompiling ahead of time, and pruning the dependency tree that loads before first useful work.
Run alert triage as agents that dedup the storm, rate severity by user impact, match a runbook, and draw a hard human-escalation line.
Operate as an accessibility specialist who audits against WCAG, trains teams to stop shipping the same defects, and owns the compliance sign-off.
Ask a model to reason before answering when the task needs intermediate steps, and know when it costs more than it gives.
Scan commit history and CI for leaked credentials and rotate on every hit, because a pushed secret is already compromised.
Run a production readiness review that checks SLOs, runbooks, capacity, and dependencies before an on-call team agrees to own a service.
Minimize, classify, mask, and expire personal data so any leak or legal request reaches as little of it as possible.
Model NoSQL data from access patterns first, with single-table and denormalization discipline. Use when designing for a document or key-value store, or when a relational mindset…
Run an Architecture Review Board that filters proposals by blast radius, reviews them through fixed lenses, issues binding decisions recorded as ADRs, and honors an appeals path.
Write replies that answer the question, respect the customer's time, and avoid the phrases that make people angrier. Use when writing any customer-facing support message.
Operate as a product designer who designs the whole flow, specs every state, defends the work in critique, and hands off at build fidelity.
Find why threads are stuck forever by dumping their state and building the wait-for graph that reveals the lock cycle.
Evaluate vendors with agents that build a comparable requirement matrix, research each option, check security and data terms, and prepare a recommendation for human sign-off.
Keep a project alive without burning out its maintainers, through scope limits, shared load, and honest signals about capacity.
Keep the public API small by defaulting to private visibility and retiring symbols through deprecation before deletion.
Use present value, rate, and payment functions correctly, with consistent periods and sign conventions. Use when modelling loans, investments, or discounted cash flows.
Build dashboards that answer specific questions at a glance, rather than displaying every available metric. Use when a team needs shared visibility into an ongoing situation.
Write so the reader understands on the first pass: plain words, concrete nouns, one idea per sentence.
Use HTTP caching correctly with etags, max-age, and stale-while-revalidate so clients and proxies reuse responses without serving stale data.
Answer a request for a copy of someone's data completely, on time, and without exposing anyone else. Use when building an export path or responding to an access request.
Load web fonts without layout shift by subsetting the file, setting font-display, preloading first-paint weights, and matching fallback metrics.
Track every vendor's cost, renewal, usage, and access with agents that flag waste and surface renewals before they auto-renew.
Turn a rough draft into finished writing through structured revision passes: cut, clarify, then polish. Use when improving your own or others' writing after the first draft exists.
Grant repository and organisation access through teams and least privilege, and review it before it drifts.
Explain something to someone with no background, without condescension and without jargon that quietly requires prior knowledge.
Connect MCP servers into an application with lifecycle management, capability negotiation, and graceful degradation when a server is unavailable.
Write a code style guide people actually follow by deciding once, automating enforcement, and logging exceptions.
Use an API gateway for cross-cutting edge concerns without letting it absorb business logic, including the BFF variant.
Operate as an engineering manager who grows people, protects delivery health, hires deliberately, and shields the team from noise.
Keep your service healthy when a dependency is slow or failing, through timeouts, retries, circuit breakers, and fallbacks. Use when an external call sits in a request path.
Decide what deserves a notification, on which channel, and at what urgency, before building any of it.
Apply Python idioms where they cut bookkeeping and clarify intent, and refuse them where the clever form hides control flow.
Correct or forgive misspelled queries without turning precise searches into fuzzy guesses. Use when users mistype and get nothing, or when fuzzy matching returns irrelevant…
Drive API development from an OpenAPI spec as the contract, with linting, codegen, and drift detection.
Universal links and deep linking skill for implementing iOS Universal Links, Android App Links, custom URL schemes, and deferred deep linking across mobile platforms.