aouellets

Use when a founder needs to understand or model ownership and dilution. Triggers on "model my cap table", "how much will I be diluted", "option pool", "SAFE conversion", "post-money vs pre-money", "what do I own after this round", "pro rata". Turns equity from a black box into a model the founder controls.

Use when a founder needs to prepare materials for investor due diligence. Triggers on "set up a data room", "what goes in a data room", "diligence checklist", "prepare for due diligence", "investors asked for our data room". Builds the organized, staged room that makes diligence fast and confidence-building.

Run structured commercial, financial, technical, and legal diligence.

Help the user build a realistic budget, a debt-payoff plan, and savings goals from their actual numbers.

Use after a term sheet is signed and the founder needs to get to wired money. Triggers on "how do I close the round", "what happens after the term sheet", "confirmatory diligence", "closing documents", "when does the money arrive", "how long to close", "wire the funds". Manages the path from handshake to cash without deals dying in the home stretch.

Use before a founder starts pitching to check they are actually ready. Triggers on "am I ready to raise", "what do I need before fundraising", "will I pass diligence", "fundraise checklist", "what are investors going to find". Surfaces the gaps that kill rounds before the first meeting.

Use when a founder is shaping the team for a raise or hiring against the round. Triggers on "team slide", "what hires do investors want", "how much equity for an early hire", "key hire before fundraising", "is my team fundable", "hiring plan for the round". Connects the team story, the gap-filling hires, and the equity to grant.

Build a compelling founder story arc for seed and Series A pitches.

Produce and run a word-for-word gym intro-consult script using the CLOSER sequence (Clarify, Label, Overview, Sell, Explain, Reinforce) to take a booked lead to a paid membership. Use when a gym owner or coach asks for a sales script, says "how do I close the consult", "intro consult", "no-sweat consult", "CLOSER framework", "present the price", "I'm bad at selling memberships", or wants to prep for or review an intro consult. Do NOT use when the request is dissolving a specific objection, speeding up lead response, or building a follow-up cadence — use objection-handling-and-speed-to-lead instead; do NOT use to set the price or guarantee — use gym-pricing-and-guarantees instead.

Pick the lead channels that fit a gym's stage, back daily activity out of a member goal, and build a 30-day lead plan across the Core Four (warm outreach, content, cold outreach, paid ads). Use when a gym owner says "I need more leads", "how do I get members", "what marketing should I do", "build a lead plan", "warm/cold outreach", or "what's a lead magnet". Do NOT use when the owner wants other people to bring in members (referrals, affiliate partners, agencies, employees) — use referral-and-affiliate-system instead; for paid-ad creative and budget depth, hand off to gym-meta-ads-funnel.

Build or sharpen a gym's core offer into a one-page canvas — Value-Equation score, problem-to-solution stack, scarcity/urgency/bonus amplifiers, and a MAGIC name — so the right prospect feels stupid saying no. Use when an owner says "build my offer", "my offer isn't converting", "what should I include", "make my offer irresistible", "design my challenge offer", or "name my program". Do NOT use when the task is choosing the price point or writing guarantee language — use gym-pricing-and-guarantees instead; do NOT use when the task is the day-by-day run-of-show for a challenge — use gym-transformation-challenge instead.

Write gym Meta (Facebook/Instagram) ad creative, structure the lead-to-consult funnel, set the budget, and read funnel costs against the challenge economics. Use when a gym owner asks to write Facebook/Instagram ads, says ads aren't converting or cost per lead is too high, asks what to spend on ads, or wants to build or scale a Meta ad funnel that fills a challenge or front-end offer. Do NOT use for general A/B creative-testing methodology — use ad-creative-testing instead; do NOT design the offer being sold or the consult close — use gym-transformation-challenge and closer-sales-script instead.

Model gym unit economics — Client-Financed Acquisition, 30-day cash, CAC, LTV, LTV:CAC, and payback — and return a verdict on whether growth self-funds. Use when a gym owner asks "what's my CAC", "how much can I spend to get a member", "what should my challenge cost to break even", "is my gym profitable to scale", "what's my LTV:CAC", or "why does growth stall when ads work". Do NOT use for generic SaaS or non-gym business unit economics — use unit-economics instead.

Set a single-location gym's price points and design a risk-reversal guarantee it can actually afford, with margin math so a refund never bleeds the business. Use when a gym owner asks "what should I charge", wants to set or raise a membership or challenge price, asks "is a money-back guarantee safe" or "how risky is my guarantee", or needs guarantee language to put on an offer. Do NOT use when constructing the whole offer (value stack, bonuses, scarcity, naming) — use grand-slam-offer-builder instead; do NOT use when testing whether the price self-funds acquisition — use gym-money-model instead.

Designs a gym's 6-week transformation challenge as a self-funding front-end offer and the week-by-week ascension that converts challengers into recurring members. Use when a gym owner asks to "design a 6-week challenge", structure a "transformation challenge", build a "front-end offer to fill my gym", plan a challenge "run-of-show", or figure out "how do I convert challengers to members". Do NOT use when the request is about the paid ads, audiences, or lead forms that fill the challenge — use gym-meta-ads-funnel instead.

Build a gym's role-outcome hiring funnel — scorecards, work-sample screening, A-player pay logic, hire-order sequencing — and turn the owner's work into handoff-ready SOPs. Use when a gym owner says "hire a coach", "find A-players", "first hire for my gym", "build an interview process", "document my processes", "write an SOP", or "get out of the day-to-day". Do NOT use when the user needs a generic, inclusive, legally-careful job posting for any company — use job-description-writer instead.

Map competitors across product, pricing, and positioning and produce sales-ready battle cards.

Build a focused GTM plan — ICP, positioning, channels, and a sequenced launch — instead of a scattershot.

Use when you are running an actual launch day in real time across channels. Triggers on "launch day runbook", "we launch tomorrow", "Product Hunt launch day plan", "hour by hour launch schedule", "who does what on launch day", "PH / Hacker News / Twitter / email sequencing", "launch day checklist", "our launch is going sideways", "contingency if we get rate-limited / Show HN flops / site goes down". Turns the plan into a minute-by-minute war room. Do NOT use when you are still picking the launch date, beats, or channel mix — use [[launch-plan-sequencer]] for the calendar first; this is the execution companion that runs the day it lands on.

Use when planning a product launch end-to-end and you need the full dated timeline. Triggers on "plan my launch", "launch plan", "how do I sequence a launch", "pre-launch checklist", "what happens before launch day", "launch timeline", "GTM launch plan", "coordinate a launch across channels", "who owns what for launch". Builds the pre-launch → launch-day → post-launch arc with a channel & asset checklist, owners, and dates. Do NOT use when you need the minute-by-minute run-of-show for the day itself — use launch-day-runbook instead. Do NOT use to write the core message — use positioning-statement and messaging-hierarchy. Do NOT use to design the self-serve adoption motion — use plg-motion-designer. Do NOT use to build the sales deck, battlecard, or demo script — use sales-enablement-kit.

Use when turning a positioning statement into actual copy — building the value proposition, message pillars, proof points, and per-channel messaging that keep the website, ads, and sales deck all saying the same thing. Triggers on "write our value proposition", "message pillars", "messaging framework", "messaging house", "key messages", "proof points", "our website and sales say different things", "per-channel messaging", "on-message copy". Takes the positioning-statement as input and feeds landing-page-copy. Do NOT use when you have not yet fixed positioning — use positioning-statement first. Do NOT use when you need the actual hero/landing page words — use landing-page-copy. Do NOT use to sequence launch phases — use launch-plan-sequencer; for the hour-by-hour go-live — use launch-day-runbook; for the sales deck/talk track — use sales-enablement-kit; for the in-product activation flow — use plg-motion-designer.

Use when designing a product-led, self-serve activation motion for signups. Triggers on "design our PLG motion", "self-serve onboarding", "what is our aha moment", "define activation", "activation rate", "time-to-value", "onboarding funnel", "in-product nudges", "set activation milestones", "signup to value", "free-to-paid", "PQL". Defines the aha moment, the activation milestones to it, and the in-product nudges and metric gates between each step. Do NOT use for outbound/sales-led launch sequencing — use [[launch-plan-sequencer]] instead; for arming a human sales team with collateral, use [[sales-enablement-kit]] instead; for the page that captures the signup, use [[landing-page-copy]]; for pricing tiers and the paywall, use [[saas-pricing]] and [[pricing-strategy]].

Use when defining or sharpening what a product IS before writing copy or planning a launch. Triggers on "how do I position this", "what category are we in", "who is this really for", "positioning statement", "we sound like everyone else", "nobody gets what we do", "frame the product", "April Dunford positioning". Runs competitive alternatives → unique attributes → the value they enable → best-fit segment → market frame, producing one tight defensible paragraph. Do NOT use for the actual page/headline wording — use [[messaging-hierarchy]] instead; for price points — use [[pricing-strategy]] or [[saas-pricing]].

Reason about pricing from value, competition, and cost, and land on a structure that fits the business.

Drafts a margin-aware 3-email cart-recovery sequence that reminds, handles objections, then incentivizes only as a last touch. Use when a checkout is started but not completed and you need cart-recovery (abandoned-cart) emails, when wiring an abandoned-cart flow in Shopify, Klaviyo, or similar, or when asked to recover lost carts without overspending on discounts.

Writes an Amazon product title, five bullets, and backend search terms that obey Amazon's character, byte, and keyword rules while staying click-worthy in the search grid. Use when drafting or fixing a Seller Central listing, rewriting an Amazon title or bullet points, packing backend search terms, or recovering a listing flagged or suppressed for content. Do NOT use when writing on-site product-detail-page copy for your own storefront or marketing site — use product-description-writer instead.

Write the intro and lower-page copy for an ecommerce collection or category page so it ranks for a commercial query while pushing shoppers toward a product fast. Use when you have a collection/category page (e.g. "women's merino base layers", "standing desks") and need the above-grid intro blurb, the H1, and the supporting SEO content below the product grid. Do NOT use for standalone marketing or campaign landing pages — use landing-page-copy instead; do NOT use for a single product's description — use product-description-writer instead.

Builds an honest "X vs Y" or "best alternative to X" comparison page — scannable table plus use-case routing copy — for high-intent commercial searches. Use when the user wants to create a "vs" or "alternative-to" page, a competitor comparison table, or copy that names a rival and asks which product to choose.

Writes the single on-site PDP master copy — a benefit-led, scannable product detail page in the brand's voice — from a raw spec sheet or feature list. Use when you have a spec list, feature bullets, or a bare template description for one product and need conversion copy for its on-site product detail page. Do NOT use for Amazon or marketplace listings — use amazon-listing-optimizer instead; do NOT use to spin one master into many size/color variants — use variant-copy-scaler instead.

Mines customer reviews and Q&A into a pre-purchase PDP FAQ and objection-handling block that answers shopper hesitation before it forms. Use when you have a review or Q&A export and want to write or rebuild a product page FAQ, reduce returns from preventable surprises, or shoppers keep asking the same pre-purchase questions. Do NOT use when analyzing support tickets or CSAT/NPS verbatims to find quality root causes — use CSAT Root Cause Analysis instead.

Generates distinct, on-brand copy for every size, color, and bundle variant from a single master description, splitting shared core from a thin per-variant layer to avoid thin or duplicate-content pages. Use when one product ships in many variants (colors, sizes, bundles, SKUs) and you need per-variant PDP copy, or when near-identical variant pages are creating duplicate-content or canonical problems. Do NOT use when writing the single master or parent PDP description from specs — use product-description-writer instead.

Designs automated drip and onboarding email sequences that activate users. Use when building a new onboarding flow, extending a drip series, or diagnosing low activation rates.

Drafts short, personalized recruiting outreach and InMail messages to a passive candidate from their public professional profile. Use when sourcing or contacting a passive candidate, drafting an InMail or LinkedIn sourcing message, or personalizing recruiting outreach from a profile URL or profile summary. Do NOT use when writing sales or founder cold email to prospects — use cold-email-craft instead.

Consolidates multiple interviewer scorecards into a calibrated hire/no-hire summary that foregrounds evidence, surfaces disagreement, and flags bias risks for a human panel. Use when you have collected scorecards or written feedback from a completed interview loop and need to run the debrief, calibrate divergent ratings, or produce a defensible decision write-up. Do NOT use when you are preparing questions or rubrics before interviews — use interview-question-kit instead.

Generates a structured candidate-interview question set where every behavioral (STAR) and role-specific item maps to a defined competency and ships with good/mixed/weak answer anchors. Use when planning or writing a hiring interview loop, building an interview question bank, or turning a job rubric or competency list into per-interviewer questions and scoring anchors. Do NOT use when consolidating completed scorecards into a hire decision — use interview-debrief-synthesizer instead.

Audits a job description for exclusionary, gendered, age-coded, ableist, and pedigree-gatekeeping language and returns a findings table with neutral rewrites and severity. Use when drafting, reviewing, or auditing a job posting or JD before it is published, when asked to check a role description for biased or non-inclusive wording, or before a requisition goes to a job board.

Draft an inclusive, role-relevant, level-calibrated job posting from a hiring manager's role brief. Use when an employer is writing or revising a job description, JD, or job posting — you have a role brief, leveling rubric, or comp band and need outcome-based requirements, plain compensation/logistics, and inclusive tone. Do NOT use when tailoring a candidate's resume or cover letter to a posting — use job-application instead.

Drafts unambiguous candidate offer letters and respectful, legally-careful candidate rejection notes for a human to review and send. Use when you are asked to write, draft, or word an offer letter, an offer email, or a candidate rejection/decline note — or to soften, tighten, or de-risk an existing draft of one. Do NOT use when writing performance feedback for a current employee — use feedback-writer instead.

Produces a 30/60/90-day onboarding plan for a specific role with phased milestones, first-week setup, observable success criteria, and ramp reviews. Use when a new hire has an accepted offer or start date, or when asked to write, draft, or improve a 30/60/90 / ramp / onboarding plan for a role. Do NOT use for the structure of ongoing recurring 1:1s — use 1on1-agenda instead.

Turn a job description into a weighted, anchored rubric for the pre-interview resume/CV screen so applicants are filtered against the same job-relevant criteria, in writing, before opinions form. Use when you have a JD and an applicant pile and need to decide who advances to interviews, set up a fair resume screen, or replace gut-feel resume sorting with a defensible filter. Do NOT use when building the interview-loop scorecard interviewers fill in during or after interviews — use hiring-scorecard instead.

Rewrites a section or page into concise, self-contained answer blocks that AI answer engines and search snippets can lift and cite verbatim. Use when restructuring a blog post, FAQ, docs page, or landing copy to win a featured snippet or get quoted by AI Overviews, ChatGPT, or Perplexity, or when a draft buries its answer in setup. Do NOT use for keyword research, full-article drafting, or technical/crawlability SEO — use a dedicated SEO or copywriting skill instead.

Produces a prioritized refresh plan for a decaying published page — a refresh/consolidate/retire verdict plus ordered update actions to recover or grow rankings. Use when an existing URL is losing traffic or rankings, during a periodic content-decay sweep, or when asked to "update", "refresh", or "revive" an old article. Do NOT use when planning coverage for a draft that is not yet published or ranking — use SERP Gap Analyzer instead.

Maps internal links and anchor text between a new or updated article and an existing URL inventory to strengthen a topic cluster. Use when you have a draft or published page plus a list of existing site URLs (sitemap, export, or pillar/cluster map) and need to decide which pages to link to and from, and with what anchor text.

Collapses a raw keyword list into topic clusters and a pillar/cluster page architecture with one primary keyword and a prioritized build order per cluster. Use when you have a keyword export (CSV/GSC/keyword-tool dump) and need a content plan that says which pages to build, not a flat list. Do NOT use when labeling individual queries by intent or recommending page types — use search-intent-classifier instead; do NOT use when choosing internal links or anchor text between pages — use internal-linking-mapper instead.

Writes title tags and meta descriptions that fit SERP pixel and character limits, place the keyword for relevance, and frame the snippet to drive clicks. Use when writing or rewriting a page title tag or meta description, fixing a page that ranks but gets few clicks, or differentiating a SERP snippet against competitors. Do NOT use when the request is broad on-page or technical SEO (headings, internal links, schema, crawlability) — use seo-optimizer instead.

Label a keyword's dominant search intent and prescribe the page type (blog, comparison, category, landing, or hub) that can rank for it. Use when choosing blog vs landing vs comparison for a target keyword, auditing why a well-built page won't rank, or screening a keyword list for intent before producing content.

Outputs the subtopics, entities, and questions a draft is missing versus the pages already ranking for its target query, classified by whether each gap is worth closing. Use when you have a draft (or outline) plus a target query and want to know what to add before publishing, or when you can name the 3-5 URLs currently ranking and want to close coverage gaps against them.

Audit and rewrite pages to rank, without keyword stuffing.

Generates a typed API client from an OpenAPI/Swagger spec, with a hand-controlled transport wrapper for timeouts, auth, and typed errors. Use when integrating a REST API that ships an openapi.yaml/swagger.json, when generating or regenerating a client from a spec, or when a hand-written client keeps drifting from the upstream contract. Do NOT use when the task is the backoff/retry policy itself — use rate-limit-handler instead; do NOT use for cursor pagination or keeping a local copy in sync — use pagination-and-sync-engineer instead.

Produces an API version scheme (date-pinned header or URI), a breaking-vs-additive change policy, and a published deprecation/sunset timeline with translation shims. Use when removing or renaming a field or endpoint, tightening validation, cutting a "v2", binding a partner integration to a version, or planning how long an old version lives. Do NOT use when designing the resource shape, URLs, status codes, or pagination of a new endpoint — use REST API Design instead; this skill owns only the version scheme and deprecation path layered on top of that contract.

Wraps flaky upstream dependencies in circuit breakers, aggressive timeouts, and per-dependency bulkheads so a slow or failing service degrades gracefully instead of cascading into a full outage. Use when a slow or unavailable upstream is stalling your threads, outbound calls hang with no timeout, one dependency's outage is taking down unrelated traffic, or you are integrating a network call that can realistically be slow or down. Do NOT use when the goal is staying under a provider's request quota or handling 429s — use rate-limit-handler instead; do NOT use to size a database connection pool — use connection-pool-tuner instead.

Adds client-supplied idempotency keys and request deduplication so at-least-once delivery and client retries return the first result instead of double-charging or double-shipping. Use when building a write endpoint that triggers payments, orders, emails, or other non-reversible side effects, or before exposing any unsafe POST behind a retrying client or queue. Do NOT use for inbound third-party webhook handlers whose dedup is keyed on a provider event ID — handle those in your webhook receiver and reference this skill for the storage pattern instead.

Build correct cursor pagination and incremental delta sync against a paginated API, handling inserts, deletes, watermarks, resumability, and idempotency. Use when paging a list/changes endpoint, fetching a large dataset, or keeping a local copy in sync — especially when a sync skips or duplicates rows, you have an offset/page=N loop, or you are designing a cursor or updated_at watermark. Do NOT use when generating a typed API client or SDK from a spec — use api-client-generator instead.

Adds retry-with-backoff, Retry-After handling, and client-side throttling so a caller stays under an upstream API's rate limits instead of hammering it. Use when you call a rate-limited or quota-enforced third-party API, see 429 or 503 responses or Retry-After headers, or have a worker fleet that needs to share one upstream's quota. Do NOT use to fail fast when a dependency is down — use circuit-breaker-builder instead; do NOT use to scaffold the HTTP client itself — use api-client-generator instead.

Hardens an inbound webhook endpoint so it verifies the sender signature on the raw body, resists replays, and acknowledges fast by persisting-then-enqueueing before any processing. Use when building or reviewing a handler that receives webhooks from Stripe, GitHub, or any third party, when adding HMAC signature verification, or when a sender is replaying events or hammering you with retries after slow acks.

Design REST APIs that are consistent, discoverable, and easy to consume.

Produce a reproducible signing, versioning, and store-declaration pipeline so an iOS or Android build passes App Store Connect / Play Console submission. Use when building or uploading a distribution .ipa/.aab, fixing signing/provisioning-profile or entitlement errors, bumping CFBundleVersion/versionCode, filling App Privacy / Data safety forms or PrivacyInfo.xcprivacy, wiring Fastlane lanes, or diagnosing a store rejection. Do NOT use for general (non-mobile) release steps like changelogs, tagging, or backend deploys — use prepare-release instead; do NOT use for store listing titles, descriptions, or keywords — use app-store-copy instead.

Architects Flutter widget trees and Riverpod or Bloc state so rebuilds are scoped, build() stays pure, and const widgets skip recomposition. Use when building or refactoring Flutter screens in .dart files, fixing jank or rebuild storms, choosing between Riverpod and Bloc, or wiring StatelessWidget/StatefulWidget, Consumer, or BlocBuilder. Do NOT use for Android Jetpack Compose UI — use jetpack-compose-builder instead; do NOT use for React Native — use react-native-pro instead.

Builds Android Jetpack Compose UI with hoisted state, unidirectional data flow, and recomposition-safe patterns. Use when writing or refactoring @Composable functions, Compose screens in Kotlin/.kt files, ViewModel/StateFlow wiring, LazyColumn lists, or fixing Compose recomposition jank. Do NOT use when the screen targets Flutter or a generic cross-platform mobile UI — use flutter-widget-architect instead.

Build local-first mobile storage with an optimistic local store, durable mutation outbox, deliberate conflict resolution, incremental pull, and idempotent background retry. Use when a mobile feature must keep working offline, when edits made offline must reconcile with the server later, or when reconciling a local database (Room, SwiftData, SQLite, Realm) against server state. Do NOT use for simple response caching of read-only data or for strong-consistency operations like payments and inventory counts — disable those offline instead.

Diagnoses and fixes mobile jank, dropped frames, and growing memory by capturing a trace or heap snapshot, isolating the worst frame or leak, fixing it, and re-measuring against the frame budget. Use when a mobile app stutters or drops frames, scrolling a long list is slow, memory grows over repeated navigation, or the UI feels laggy on a real device. Do NOT use when the bottleneck is a server-side or web hot path (slow endpoint, query, render time) — use optimize-performance instead.

Wires native mobile push end to end on APNs and FCM — device-token registration, alert and silent payloads, permission priming, server send path, and tap routing into the app. Use when you are adding push to an iOS or Android app, debugging why a push never arrives or never wakes the app, wiring the .p8/service-account server sender, or handling a notification tap. Do NOT use for web/browser push (Web Push/VAPID), in-app banners, or platform notification dashboards — and for navigating a tapped payload into a specific screen, use a deep-link router instead.

Build and ship production React Native apps.

Build clean, performant, accessible SwiftUI views.

Write consumer-driven contract tests at service and API boundaries so an incompatible change fails a build instead of breaking integrations silently in production. Use when a client and a service (or two services) must stay in sync across separate deploys — adding a Pact consumer test, replaying a pact file in provider verification, publishing pacts to a Pact Broker / PactFlow, gating with can-i-deploy, or after a renamed field or changed status code broke a consumer that unit tests passed.

Produces a risk-ranked list of untested critical paths and branches, with the specific missing cases and the smallest test that buys the most safety. Use when a coverage report shows high line coverage you do not trust, when deciding what to test next, or when auditing a suite before a release cut — anytime the question is "which gap actually matters," not "what is the percentage."

Converts an acceptance criterion or user story into one maintainable Playwright or Cypress end-to-end test that reads like the journey it covers. Use when turning a Given/When/Then acceptance criterion or user story into a browser test, when asked to "write an E2E test for this AC", or when a feature's critical journey (login, checkout, signup) needs a single automated scenario. Do NOT use when writing general Playwright tests, configuring the runner, or fixing existing test flakiness — use playwright-testing or flaky-test-detangler instead.

Root-causes intermittently failing tests and eliminates the hidden dependency at its source instead of retrying around it. Use when a test passes locally but fails in CI, goes green on a CI re-run, fails roughly one run in ten, or is already tagged "flaky." Do NOT use when the task is to design the fake or stub that replaces a real dependency — use mock-stub-designer instead.

Designs the minimal set of test doubles for a unit or integration test and decides, per dependency, what to fake versus exercise for real. Use when a test touches an external boundary — an HTTP/third-party API, payment or email/SMS SDK, the database, the filesystem, the system clock, or randomness — or when existing tests over-mock and pass while the system is broken.

Runs mutation testing on already-covered code and turns each surviving mutant into a specific missing assertion, exposing tests that execute code but verify nothing. Use when line coverage is high yet a bug slipped through, when reviewing a critical module (pricing, permissions, auth, state machines) before release, or when you are asked to run Stryker, PIT, mutmut, or cosmic-ray. Do NOT use when the goal is to find which code paths are untested at all — use coverage-gap-finder instead.

Builds realistic domain fixtures, factories, and edge-case datasets with the builder pattern and valid defaults. Use when a test needs domain objects, seed data, factories, or boundary/edge-case inputs; do NOT use when a test needs to fake a network call, database, clock, or third-party SDK — use mock-stub-designer instead.

Write end-to-end Playwright tests that are resilient, readable, and free of flakiness.

Produces a documented inventory of the implicit business rules, edge cases, and bug-as-feature behaviors that tangled code encodes, with real input-to-output examples, so a rewrite preserves behavior. Use when you are about to rewrite, port, or replace legacy code whose only specification is the source, and you see policy buried in conditionals, magic numbers, hardcoded dates, or per-customer special cases. Do NOT use when you need an executable safety net before refactoring — use characterization-test-writer instead; do NOT use when you need to find service boundaries in a monolith — use monolith-decomposer instead.

Writes pinning and characterization tests that lock in the current behavior of untested legacy code before a refactor, so any later behavior change trips an alarm. Use when you are about to refactor, rewrite, or modify an untested legacy function/module and need a safety net first, when code has no tests and its "correct" behavior is simply whatever it does today, or when you must capture existing output (bugs included) before touching it. Do NOT use when writing tests for new behavior you are building red-green — use tdd-expert instead; do NOT use to decide which code is worth testing or to rank coverage gaps — use coverage-gap-finder instead.

Proves code is unreachable with converging evidence, then removes it and its tests, fixtures, and flags in reversible slices without breaking dynamic callers. Use when deleting suspected dead code, cleaning up after a migration or feature retirement, trimming a bloated module, or before estimating work on unfamiliar code. Do NOT use when you want to survey and rank an area's debt without committing to deletion — use find-tech-debt instead.

Drives a major-version framework bump as a sequence of small, reversible, CI-gated PRs using official codemods and changelog diffing while keeping the app green. Use when bumping React, Rails, Spring Boot, Angular, or any framework across a major version with breaking API/config changes; do NOT use for language or runtime version jumps (Python 2 to 3, Node majors, Java LTS) — use language-version-migrator instead.

Ports a codebase across a breaking language or runtime version using compatibility shims, automated transforms, and old-vs-new verification. Use when migrating Python 2 to 3, jumping Node major versions, moving across Java LTS releases, or any runtime upgrade where source must change to keep compiling or behaving correctly. Do NOT use when upgrading an application framework's major version (React, Rails, Spring) — use framework-upgrader instead; and skip this when the runtime change is purely operational (base image, CI matrix, deploy target) with no syntax or semantic breaks.

Finds and sequences one bounded-context seam to extract from a monolith, gated on dependency, data-ownership, and transaction-boundary evidence, and produces an incremental strangler extraction plan. Use when you are planning to carve a service out of a monolith, deciding where to cut, or evaluating whether a candidate seam is ready to extract.

Produces an incremental migration plan that runs a legacy and a new system side by side behind a routing seam, slicing and sequencing whole capabilities so the old system stays live until its last route is cut. Use when planning to replace or rebuild a large, business-critical system that must keep serving traffic throughout. Do NOT use when extracting a single service from a still-living monolith — use monolith-decomposer instead; for generic non-migration implementation planning, use the plan skill instead.

Audits third-party dependencies for CVEs, abandoned packages, license risk, and supply-chain hygiene indicators. Load when adding new packages, reviewing a lockfile, or preparing for a security review.

Diagnoses connection pool exhaustion from captured evidence and sets correct pool sizes and timeouts across app pools and PgBouncer. Use when you see "too many clients"/connection-limit errors, pool checkout/acquire timeouts, idle-connection or "idle in transaction" pile-up, or serverless functions storming the database on a traffic spike. Do NOT use when the problem is an unreliable external service (third-party API, downstream microservice) needing retries or fallbacks — use circuit-breaker-builder instead.

Read a captured EXPLAIN ANALYZE plan, name the single bottleneck node, and prescribe a targeted fix for it. Use when a specific query is slow and you have (or can capture) its execution plan from Postgres or MySQL and need to know WHICH node is burning the time and why.

Recommends, orders, and prunes indexes for a specific query or table — composite column order, partial and covering indexes, duplicate/unused cleanup, and write-cost tradeoffs. Use when a query is slow and EXPLAIN shows a Seq Scan or a sort, before adding a CREATE INDEX, or when auditing a table's index set for bloat or duplicates. Do NOT use when the table is too large and needs partitioning or a time-series strategy — use partition-planner instead; do NOT use when the query shape itself is the problem (function-wrapped predicates, leading wildcards, correlated subqueries) — use query-rewriter instead.

Rewrite a schema migration into independently deployable, zero-downtime steps that never take a long-held blocking lock on a live table. Use when you are about to run an ALTER TABLE, CREATE INDEX, add a constraint, rename a column, or change a column type against a production database with live traffic. Do NOT use for greenfield table/column design with no rows yet — use database-schema instead; do NOT use for broad correctness/integrity review of a migration — use review-db instead.

Detect ORM loop-of-queries (N+1) patterns from query logs and eliminate them with batched eager loading, keeping the N+1s that are cheap. Use when a list endpoint is slow, a request issues many near-identical SELECTs differing only by an id, query logs show repeated SELECTs in a loop, or a tool like the bullet gem flags an N+1 in ActiveRecord, Prisma, SQLAlchemy, or Hibernate.

Produces a partitioning or sharding plan for an oversized table — range/list/hash strategy, partition-key choice, composite-key and pruning constraints, and a verdict on whether to partition at all. Use when one table has grown past tens of millions of rows or hundreds of GB, vacuum/autovacuum on it runs for hours, retention deletes are giant DELETEs, or you are deciding between range/list/hash partitioning or sharding a hot table. Do NOT use when the goal is choosing indexes for specific slow queries — use index-advisor instead.

Rewrites a structurally inefficient SQL query into a faster equivalent that returns byte-identical results — correlated subqueries to joins or LATERAL, accidental cross joins to explicit ON predicates, OR-across-columns to UNION, SELECT * to projected columns, and deep OFFSET pagination to keyset. Use when a query is slow because of its shape rather than its indexes — EXPLAIN shows a Cartesian blowup, a per-row subquery, or OFFSET discarding tens of thousands of rows — and the indexes are already in place. Do NOT use when the fix is adding or reordering an index — use index-advisor instead; do NOT use to diagnose an unknown slow query from its plan — use sql-query-optimizer instead.

Diagnoses read-replica lag and the stale-read bugs it causes, then applies read-after-write consistency strategies to fix them. Use when a read returns data older than a just-committed write ("the row I just saved disappeared"), when replica lag monitoring alerts or grows after a backfill, or when deciding which reads must hit the primary versus a replica.

Use when someone starts lifting, hits a strength or hypertrophy plateau, restructures a lifting program, or wants to build strength or muscle — designing a progressive resistance program with splits, compound movement patterns, sets/reps, progressive overload, and deloads from barbells and dumbbells. General fitness guidance, not medical advice. Owns resistance/strength training only. Do NOT use to program high-intensity interval conditioning or circuits (use fitness-program), a steady-state aerobic-base or Zone 2 block (use zone-2-cardio-plan), or a mobility/flexibility routine (use mobility-routine).

Use when someone asks to build a steady-state cardio plan, train an aerobic base or Zone 2, structure easy or endurance weekly cardio, train by heart-rate zones, or improve resting heart rate, VO2, or endurance. Builds a heart-rate-zone aerobic training block with session structure, modality choice, and progression. General fitness guidance, not medical advice. Do NOT use to design a strength or lifting program (use Strength Training Plan), high-intensity interval conditioning, HIIT, or circuits (use Conditioning & HIIT Program), or a mobility/flexibility routine (use Mobility Routine).

Explains common lab panels in plain language and what questions to bring to a doctor. Use when reviewing blood test results and wanting to understand what markers mean. Education only; not medical advice or diagnosis.

Designs prehab and mobility work to reduce injury risk for shoulders, knees, lower back, and hips. Use when starting a training program or addressing chronic tightness. General movement guidance; not medical advice; consult a physio for existing injuries.

Assembles an evidence-informed weekly longevity routine covering sleep, zone 2 cardio, strength training, and dietary patterns. Use when building or auditing a long-term health practice. General wellness guidance; not medical advice.

Builds a daily mobility and flexibility routine for desk workers targeting hips, thoracic spine, shoulders, and ankles. Use when addressing stiffness, poor posture, or building a movement practice. General guidance; not medical advice.

Helps users build a sustainable nutrition plan centered on protein targets, whole foods, and adherence strategies. Use when planning meals, adjusting macros, or building lasting dietary habits. Not medical advice.

Build a personalized sleep protocol from chronotype, light exposure, environment, and recovery goals.