Reusable Agent Skills for shipping real work.

Build high-leverage sales messages that attract qualified buyers and repel poor-fit prospects. Use when writing or diagnosing headlines, landing pages, outreach, ads, sales letters, lead magnets, or B2B messages where urgency, qualification, and conversion matter.

Segment customers and lists by 80/20 value, responsiveness, recency, frequency, and money. Use when identifying best customers, prioritizing follow-up, finding high-value buyers, pruning low-value accounts, or deciding what customer data to measure.

Diagnose and prioritize sales funnel improvements by economics, conversion, split testing, and high-value customer potential. Use when optimizing funnels, deciding what to test, improving CAC or profit, evaluating upsells, or choosing the few metrics that matter now.

Find hyper-responsive buyers and disqualify weak markets using 80/20 Sales and Marketing. Use when choosing a target segment, validating demand, screening prospects, finding urgent buyer problems, or deciding whether a market is worth sales and marketing effort.

Apply 80/20 power-curve thinking to sales, marketing, customers, offers, traffic, time, and operations. Use when finding leverage, diagnosing uneven results, prioritizing high-upside segments, or replacing average-based reasoning with Pareto and power-law analysis.

Apply 80/20 leverage to time, talent, assistants, outsourcing, hiring, salespeople, and low-value work. Use when deciding what to delegate, outsource, stop doing, hire for, trial, or remove so high-value people spend more time on their strongest work.

Prioritize traffic, media, lists, and audience sources with an 80/20 lens. Use when choosing acquisition media, deciding which traffic source to master, evaluating rented or owned lists, sequencing channel expansion, or shifting budget toward higher-leverage sources.

Create 80/20-style unique selling propositions, guarantees, and result-based offers. Use when positioning an offer, strengthening a value proposition, raising prices, creating a guarantee, or making a sales promise more specific and credible.

Build product A/B test briefs with hypotheses, success metrics, guardrails, baselines, proxy metrics, eligibility, variants, randomization, confidence, and launch criteria. Use when planning an A/B test from a product idea, writing an experiment spec, defining test/control variants, choosing metrics, or checking whether an experiment is ready to run.

Analyze and communicate A/B test results with metric readouts, subgroup analysis, data-quality checks, ad hoc investigation, visualization, and launch recommendations. Use when interpreting experiment results, preparing an A/B test report, explaining flat or mixed results, checking guardrails, segmenting test/control data, or turning experiment data into a product decision.

Plan A/B testing platform strategy, architecture, and build-vs-buy decisions for product engineering teams. Use when deciding whether to build or buy an experimentation platform, scoping feature flagging, targeting, assignment, exposure logging, metrics pipelines, dashboards, governance, or evolving a simple testing setup into a durable platform.

Plan adaptive experimentation strategies beyond fixed-horizon A/B tests. Use when evaluating sequential testing, early stopping, multi-armed bandits, Thompson sampling, contextual bandits, dynamic traffic allocation, exploration/exploitation tradeoffs, or readiness for adaptive testing infrastructure.

Use when adding, changing, or debugging Alpine.js behavior in Django-rendered templates, especially when Alpine.js coexists with HTMX partial updates.

Use when presenting or auditing expertise, credentials, certifications, advisory boards, expert quotes, trust badges, medical claims, legal claims, financial claims, institutional logos, titles, uniforms, or authority signals that could create undue deference.

Build B2B reach systems that make a defined market aware of the company through named accounts, real buyers, controlled delivery channels, and first-touch saturation. Use when the right market may not know the company exists, outbound gets little signal, brand awareness is vague, the target market is too broad, or the team needs a concrete account list and reach plan.

Audit and rewrite B2B sales messaging so the right buyers quickly understand the painful problem, concrete outcome, and mechanism behind the offer. Use when buyers see the company but do not remember it, cannot explain what it does, do not connect it to a trigger, or messaging sounds clever, vague, over-complex, generic, or too simplified for the buyer's world.

Diagnose the single B2B sales constraint currently limiting pipeline or revenue and route to the right repair workflow. Use when sales feels stuck, pipeline is weak, leads ghost, outbound is not working, conversion is unclear, or the team is debating whether to fix reach, messaging, follow-up timing, or trust.

Design recurring B2B buyer-presence systems that keep a company remembered until pain becomes urgent, using time-based visibility cadence instead of unreliable intent signals or linear funnel assumptions. Use when buyers know the company but deals stall, follow-up is inconsistent, the team waits for triggers, expands markets too early, or wants a 4-6 week account visibility rhythm.

Engineer B2B buyer trust by reducing perceived risk, stacking relevant proof, simplifying next steps, and designing sales calls to confirm confidence rather than persuade from scratch. Use when qualified buyers take calls, request proposals, start trials, or show interest but then stall, ghost, choose safer incumbents, or hesitate because proof, certainty, process, or risk reversal is weak.

Plan beta reading rounds for practical nonfiction and turn reader comments, abandonment, confusion, skepticism, and negative feedback into manuscript revisions. Use when recruiting beta readers, preparing reader instructions, synthesizing feedback, deciding whether a book is ready, or improving a draft from real reader data.

Plan and synthesize pre-draft reader conversations for useful nonfiction books, including listening interviews, teaching calls, reader-language capture, promise validation, scope refinement, and TOC testing. Use when validating a practical book idea, finding target readers, preparing interview prompts, testing a table of contents, or turning reader conversations into book decisions.

Optimize useful nonfiction book sales after the book is already working, including Amazon or retailer funnels, cover thumbnail clarity, store descriptions, authentic reviews, extra formats, pricing, upsells, piracy hooks, and fan engagement. Use when improving a book product page, purchase funnel, format strategy, pricing, direct sales, or post-launch growth.

Plan seed marketing for useful nonfiction books so the first 500-1000 target readers can start word of mouth. Use when choosing launch channels, planning a podcast or digital book tour, Amazon PPC, event giveaways, bulk sales, writing in public, content schedules, or email capture for a practical book.

Design and pressure-test useful nonfiction book promises, scopes, recommendation loops, and takeaway-first tables of contents before drafting. Use when planning, outlining, scoping, restructuring, validating, or testing a practical book, guide, manual, course-like book, or other reader-outcome-focused long-form nonfiction.

Run broken link building and link equity salvage workflows by finding relevant resource pages, checking outbound link status, verifying dead URLs, qualifying dead backlinks, preparing replacement outreach, and mapping old owned URLs to redirects. Use when finding broken link prospects, replacing dead resources, recovering lost backlinks, or auditing old URLs after migrations and redesigns.

Test-drive browser JavaScript behavior with DOM fixtures, test runners, smoke tests, onload timing, selector refactors, and integration tradeoffs with Selenium or end-to-end tests. Use when adding client-side behavior, debugging DOM tests, choosing between JS unit tests and browser functional tests, or making JavaScript testable without overusing Selenium.

Manage and query Calibre libraries with the calibredb CLI (local paths or Calibre Content server URLs). Use when listing books, searching/filtering library records, reading/updating metadata, adding/removing formats, exporting books, maintaining custom columns, running library checks, managing FTS indexing/search, or creating catalogs/backups from a Calibre library.

Design, write, review, and test code samples in developer documentation, including executable examples, explanatory snippets, request and response pairs, placeholders, outputs, language choice, sandboxing, and autogenerated samples. Use when docs include API examples, SDK snippets, CLI commands, config examples, tutorials, or code blocks readers may copy.

Calculate, review, and generate web color systems using RGB, HSL, LAB, OKLCH, contrast ratios, luminance, opacity, blend modes, and light/dark mode transformations. Use when auditing accessible colors, converting color models, deriving palettes, checking WCAG contrast, building theme tokens, or debugging opacity and CSS blend math.

Use when designing or auditing onboarding, activation flows, habit loops, pledges, public commitments, progressive profiling, retention programs, behavior-change plans, pricing flows, or lowball-risk funnels where consistency pressure may shape user decisions.

Use when sequencing offers, pricing tiers, proposals, negotiation anchors, product demos, before-after comparisons, concession framing, reason-giving, request wording, or comparative messaging where contrast effects or shallow reasons may distort decisions.

Use when adding, changing, testing, or debugging Cookiecutter templates, including cookiecutter.json variables, Jinja-rendered files, hooks, _copy_without_render, optional feature cleanup, and generated-project validation.

Derive and debug CSS Grid layout math for grid coordinates, line placement, spans, negative indexes, fr units, minmax(), fit-content(), repeat(), auto-fill, and auto-fit. Use when building grid systems, explaining track sizing, troubleshooting fr distribution, placing items by line numbers, or converting a layout sketch into CSS Grid formulas.

Explain, derive, and debug CSS math for measurement units, calc(), min(), max(), clamp(), custom properties, inheritance, em/rem scaling, percentages, viewport units, and box model formulas. Use when CSS dimensions compute unexpectedly, when mixing units, when building scalable spacing/type systems, or when reviewing box sizing and inherited values.

Evaluate whether customer, sales, investor, partner, or product meetings produced real commitment and advancement instead of polite interest. Use when interpreting meeting outcomes, stalled leads, trial requests, letters of intent, preorders, warm intros, case-study offers, unclear next steps, or compliments after a pitch.

Find and frame customer conversations through warm intros, communities, casual chats, events, advisors, landing-page replies, and meeting requests. Use when a team needs people to interview, cold outreach is failing, a meeting ask sounds needy or pitchy, or customer discovery needs a credible reason to talk.

Plan and audit customer discovery conversations that produce concrete evidence instead of compliments, opinions, hypotheticals, or feature-request noise. Use when planning customer interviews, rewriting interview scripts, validating startup ideas before building, avoiding biased questions, or applying Mom Test-style customer learning.

Turn customer conversation notes, interview transcripts, call summaries, CRM snippets, or research notes into shared team learning and next questions. Use when synthesizing raw customer notes, avoiding founder interpretation bottlenecks, extracting quotes and signals, updating beliefs, or deciding what to ask next.

Narrow broad customer categories into specific, reachable who-where segments for customer discovery, positioning, traction tests, sales outreach, or SEO personas. Use when feedback is inconsistent, the market is too broad, personas are vague, users request too many different features, or the team does not know where to find target customers.

Research developer documentation audiences by mapping user goals, learning objectives, business goals, developer traits, user questions, personas, user stories, journey maps, and friction logs. Use when planning docs for APIs, SDKs, platforms, CLIs, developer tools, onboarding guides, SaaS docs, or support-heavy docs before writing or restructuring content.

Draft developer documentation with clear goals, outlines, titles, headers, procedures, scenario walkthroughs, lists, callouts, skimmable structure, and reusable templates. Use when writing or rewriting READMEs, getting-started docs, tutorials, how-to guides, concepts, API guides, troubleshooting pages, migration guides, SaaS topics, or release documentation.

Edit and review developer documentation for technical accuracy, completeness, structure, clarity, brevity, peer feedback, technical review, technical verification, QA procedure testing, and feedback integration. Use when reviewing, editing, refactoring, or preparing developer docs for release, especially docs with procedures, examples, prerequisites, or high-risk technical claims.

Plan developer documentation by choosing content types, defining scope, making documentation decisions, researching features, planning scenarios, and turning user needs into a practical documentation plan. Use when planning READMEs, getting-started guides, concepts, tutorials, how-to guides, API references, troubleshooting docs, changelogs, release notes, Agile docs work, or multi-doc launch plans.

Research product and feature facts for developer documentation by mapping source-of-truth owners, validating behavior hands-on, interviewing SMEs, and turning uncertainty into doc-ready notes. Use when feature specs are incomplete, implementation details need user-facing meaning, SMEs disagree, or docs require evidence before planning, drafting, release notes, API docs, tutorials, scenarios, or troubleshooting content.

Plan and review survey-led digital PR campaigns that earn editorial links through credible data, methodology, story framing, journalist outreach, and promotion. Use when creating data studies, expert surveys, journalist pitches, methodology notes, PR exclusives, or linkable research assets for SEO.

Evaluate directories, listings, profiles, citations, associations, and resource indexes for legitimate link-building value, editorial quality, spam risk, local relevance, and submission fit. Use when deciding whether to submit to a directory, audit directory backlinks, compare listing opportunities, or reject low-quality indexes.

Optimize Django and pytest-django test execution in CI with cache configuration, slow-test splitting, database reuse strategy, parallel workers, pytest-xdist, CircleCI/GitHub Actions/Jenkins/Travis patterns, and full-coverage safeguards. Use when CI test jobs are slow, flaky under parallelism, missing slow-test coverage, or need a local-vs-CI test command design.

Diagnose and improve slow Django database-backed endpoints with evidence-first profiling, query-plan review, index selection, ORM loading fixes, batching, database-side computation, materialized views, and pagination choices. Use when a Django view, API, job, report, queryset, or database query is slow and the right optimization path is not obvious.

Move Django performance-sensitive Python loops into database-side computation with annotations, aggregates, filtered aggregates, F expressions, functions, Subquery, OuterRef, Exists, Window expressions, db_default, and GeneratedField. Use when Django code counts, sums, filters, flags, ranks, or derives values in Python after fetching rows.

Make Django deployment changes test-driven across Docker, production settings, Gunicorn, WhiteNoise/static files, environment variables, Ansible/server setup, staging smoke tests, and release checks. Use when containerizing Django, preparing production config, debugging staging, automating deploys, or deciding what deployment behavior functional tests should verify.

Test-drive Django validation across model constraints, forms, ModelForms, views, template errors, duplicate handling, and redirects. Use when adding or refactoring Django forms, surfacing validation errors, deciding model-vs-form-vs-view responsibility, or preventing invalid input from being saved.

Build and review HTMX interactions in Django server-rendered projects, especially generated django-saas-starter apps. Use when adding hx attributes, partial template responses, request.htmx branching, django-htmx response headers, forms, swaps, triggers, redirects, polling, boosted links or forms, or coordinating HTMX with Alpine.js local state.

Design safe Django and PostgreSQL indexes from measured query plans, including B-tree, composite, covering, partial, expression, GIN/JSONB, BRIN, and concurrent migration patterns. Use when a Django query plan suggests missing or mismatched indexes, a production table needs an index without write downtime, or existing indexes need review.

Model, migrate, refresh, and verify PostgreSQL materialized views in Django for expensive report or dashboard queries that can tolerate stale data. Use when ORM/index/query rewrites are not enough, the result is read often, freshness can be bounded, and a Django app needs unmanaged models, RunSQL migrations, refresh commands, or concurrent refresh.

Optimize Django ORM query loading by fixing N+1 queries, duplicate related-object queries, over-fetching, serializer/template query loops, and inappropriate select_related, prefetch_related, only, or defer usage. Use when a Django page, API, admin view, template, serializer, or queryset issues too many queries or loads more model data than needed.

Drive Django features with outside-in and double-loop TDD: user story, Selenium or functional test, focused Django unit/integration tests, minimal implementation, and refactor. Use when starting or changing Django behavior with tests-first workflow, red/green/refactor, working-state-to-working-state refactors, or deciding which layer should own the next test.

Improve Django and Django REST Framework pagination for large querysets using bounded page sizes, stable ordering, indexed ordering, offset limits, keyset pagination, DRF CursorPagination, and count-query tradeoffs. Use when list pages, admin views, APIs, exports, or infinite scroll become slow, inconsistent, or memory-heavy as result sets grow.

Use when adding, changing, testing, or debugging Django Q2 background tasks, scheduled jobs, qcluster workers, Redis broker configuration, or ORM broker fallback in Django projects.

Read and compare Django/PostgreSQL query execution plans using QuerySet.explain(), EXPLAIN, EXPLAIN ANALYZE, scan types, joins, estimates, actual timing, buffers, and row counts. Use when one SQL query dominates Django latency or when an index, ORM rewrite, pagination change, or materialized view needs proof from a query plan.

Find the Django ORM code and request path responsible for slow SQL by using APM traces, slow query logs, Django Debug Toolbar, query logging, and local reproduction. Use when a Django database performance issue is suspected but the exact queryset, view, serializer, template, or job causing it is not yet proven.

Process large Django querysets and write-heavy jobs with memory-safe reads, values/values_list, iterator chunking, set-based update/delete, bulk_create, bulk_update, F expressions, Func expressions, and batch sizing. Use when a Django command, task, migration, report, or loop reads or writes many rows and is slow, memory-heavy, or query-heavy.

Design, debug, and maintain Django Selenium functional tests with live server setup, explicit waits, test isolation, page objects, screenshots, CI artifacts, and staging checks. Use when browser tests are flaky, too slow, duplicated, failing in CI, need a page pattern, or should verify a Django user journey end to end.

Manage Django spikes and de-spiking with tests: branch experiments, exploratory code, learning capture, functional tests against spiked behavior, revert-and-rebuild, custom auth flows, email/token models, and dependency seams. Use when a Django feature was prototyped quickly and needs to be turned into production-quality tested code.

Mock Django test boundaries safely with override_settings, pytest settings, autospecced unittest.mock objects, output/input capture, requests-mock, VCR.py, outbound HTTP blocking, and time-freezing tools. Use when tests need to replace settings, HTTP calls, time, command output, stdin, or external services without broad fragile MagicMock patches.

Design faster, clearer Django test data and test structure with factories, setUpTestData, SimpleTestCase/TestCase choices, fixture-file cleanup, query optimization, and unit-vs-integration boundaries. Use when Django tests create too much data, rely on slow fixtures, overuse TransactionTestCase, duplicate setup, or need refactoring for speed without losing coverage.

Safely parallelize Django and pytest-django test suites with Django --parallel, pytest-xdist, test isolation checks, randomized order detection, shared-resource sharding, locks, and load balancing. Use when enabling parallel tests, diagnosing failures under parallel execution, handling flaky Django tests, or making caches, files, queues, and external resources safe across workers.

Improve slow Django test suites through measured profiling, safe test settings, database and migration tuning, parallel execution, test-data cleanup, and CI workflow changes. Use when Django or pytest-django tests are slow, CI test jobs take too long, database setup dominates runtime, or a user asks for a prioritized speedup plan rather than isolated test fixes.

Profile and measure slow Django test suites with Django's runner, pytest-django, shell timing, py-spy, cProfile, pytest durations, and profiler visualizations. Use when a Django project has slow tests, unclear test-runtime bottlenecks, CI timing problems, startup overhead, database setup overhead, or a request to find the slowest tests before optimizing.

Integrate documentation work with Agile product development by making docs visible in sprint planning, release trains, definitions of done, review timing, and retrospective improvement. Use when docs are missing from scrum boards, stories, acceptance criteria, release planning, or cross-team work, or when writers need a lightweight process for documentation inside Agile teams.

Gather, classify, prioritize, respond to, and act on developer documentation feedback from page feedback, support issues, community forums, field notes, sentiment, surveys, user councils, bug reports, and user follow-up. Use when setting up docs feedback channels, triaging docs issues, responding to frustrated users, prioritizing doc fixes, or converting feedback into actionable documentation work.

Manage developer documentation release, publishing, ownership, freshness, automation, maintenance, SaaS cadence, deprecation, deletion, redirects, and migration alongside software changes. Use when planning docs for a release, defining docs ownership, creating publishing checklists, setting up freshness checks, refreshing existing content, documenting SaaS releases, or retiring stale documentation.

Audit, organize, and redesign developer documentation information architecture, including content inventory, navigation, landing pages, sequences, hierarchies, webs, breadcrumbs, sidebars, metadata, redirects, migration, platform/tool selection, and maintainable IA decisions. Use when restructuring docs sites, improving findability, planning doc migration, evaluating docs tooling, or organizing large documentation sets.

Evaluate documentation platforms and authoring tools by requirements, workflow fit, migration risk, content model, search, integrations, portability, support burden, and cost. Use when choosing docs-as-code, CMS, wiki, DITA, API reference, static-site, help-center, or custom docs tooling, planning a migration, or deciding whether tooling will fix documentation problems.

Audit and measure developer documentation quality using functional quality, structural quality, accessibility, purpose, findability, accuracy, completeness, clarity, concision, consistency, analytics, user goals, doc goals, and metric plans. Use when evaluating docs, designing documentation metrics, selecting dashboards, or linking docs work to user and business outcomes.

Use when creating or improving persuasive copy, launch offers, fundraising appeals, onboarding prompts, sales pages, calls to action, or behavior-change messages where the goal is effective persuasion without deception, coercion, fake proof, fake scarcity, or overstated authority.

Keep technical nonfiction durable by separating timeless concepts, decision frameworks, and reader outcomes from fast-changing tool walkthroughs, UI steps, versions, vendor details, and companion resources. Use when scoping, outlining, revising, or updating technical books, self-hosting guides, software manuals, DevOps books, or other technical manuscripts that risk becoming outdated.

Improve experiment sensitivity and reduce traffic or duration requirements. Use when choosing sensitive metrics, working with minimum detectable effect, reducing variants, applying capping metrics, CUPED, variance reduction, or deciding how to get trustworthy A/B test signal with fewer users.

Choose the right product experiment type: superiority, non-inferiority, equivalence, A/B/n, or holdback-backed validation. Use when deciding what kind of A/B test to run, when the question is not simply "is variant better," when validating no degradation, proving similarity, comparing multiple variants, or selecting an experiment design for a mature product.

Verify and monitor running experiments for operational quality. Use when designing prelaunch QA, spot-check tooling, experiment canaries, A/A tests, leakage checks, interference monitoring, active experiment dashboards, alerts, or an experimentation quality roadmap.

Roll out an experimentation-friendly culture across product, engineering, data, and leadership teams. Use when introducing A/B testing to an organization, overcoming resistance to experiments, shifting teams away from launch-by-opinion, increasing experiment demand, defining rollout tactics, or creating an experimentation adoption plan.

Prioritize an experimentation platform roadmap across rate, quality, cost, usability, process, infrastructure, and advanced methods. Use when deciding which experimentation capability to build next, whether to platformize interleaving or adaptive testing, how to align experimentation with company goals, or how to trade off speed versus rigor.

Plan experiment throughput strategies for mature A/B testing programs. Use when testing capacity is constrained, teams are waiting for experiment slots, roadmap coordination is slowing learning, or a team must choose isolated, overlapping, parallel, or capacity-aware experiment scheduling without sacrificing result quality.

Use when adding, changing, deploying, testing, or debugging FastMCP MCP servers in existing Django apps, including ASGI mounting, stdio or sidecar servers, Django ORM access from MCP tools, auth and permissions, Streamable HTTP deployment, and MCP client tests.

Calculate and debug Flexbox layout math for flex base size, flex-basis, flex-grow, flex-shrink, the flex shorthand, fractional grow values, and min/max constraints. Use when flex items resize unexpectedly, when distributing free space along one axis, when comparing flexbox with grid, or when deriving predictable card, nav, toolbar, and row layouts.

Explain and apply foundational math for front-end development, including arithmetic, algebra, ratios, exponents, roots, linear equations, inequalities, geometry, trigonometry, coordinates, and choosing CSS versus JavaScript math. Use when a web design calculation needs first-principles explanation before applying CSS, JavaScript, Grid, Flexbox, responsive, or color-specific skills.

Balance game difficulty, resources, rewards, probability, progression, economies, and dominant strategies. Use when tuning combat, loot, upgrades, scoring, level curves, AI difficulty, risk-reward choices, or any system where numbers shape player decisions.

Create lightweight, living game design documents for AI-built games. Use when writing a game design brief, system spec, feature contract, content schema, implementation handoff, decision log, or when a coding agent needs durable project memory.

Choose the right geometric representation for game systems before implementing rendering, collision, procedural generation, editing, or conversion code. Use when deciding between meshes, SDFs, voxels, splines, parametric surfaces, fields, or hybrid geometry workflows for games.

Design or audit game controls, HUD, menus, feedback, input mapping, transparency, juiciness, channels, modes, and metaphors. Use when implementing UI, controls, camera, tutorials, status displays, accessibility feedback, or when players are confused about what happened.

Design, inspect, or repair game mechanics, core loops, rules, goals, actions, state, chance, secrets, skills, and emergent dynamics. Use when building gameplay systems, combat, puzzles, progression, simulations, board/card mechanics, or any feature where rules create player behavior.

Plan and implement conversions between game meshes, SDFs, voxels, images, contours, and smooth curves while preserving enough gameplay and rendering data. Use when repairing meshes, extracting meshes from fields, voxelizing geometry, contouring, denoising voxel data, generating LODs, or moving geometry between representations.

Plan, run, and interpret game playtests. Use when validating prototypes, onboarding, difficulty, mechanics, UI clarity, retention, or fun; when writing playtest scripts, surveys, observation plans, or telemetry requirements.

Turn a game idea into a focused design problem, risk-first prototype plan, and iteration loop. Use when starting a game, choosing what to build first, scoping an MVP, defining design questions, planning prototypes, or deciding whether an idea is ready for production.

Review a game for player impact, ethics, transformation, inclusion, monetization pressure, community risk, dark patterns, and hidden design agendas. Use before shipping manipulative loops, social systems, ads, monetization, retention mechanics, UGC, or player-generated communities.

Model game shapes, volumes, influence, procedural objects, and effects with signed distance functions, implicit functions, scalar fields, vector fields, and deformation fields. Use when building SDF primitives, field composition, raymarching inputs, organic procedural shapes, offsets, Booleans, deformation, or field-driven gameplay.

Design smooth game motion with splines, Bezier curves, interpolation, derivative continuity, path parameterization, and speed control. Use when implementing camera rails, waypoint paths, vehicle routes, projectile trails, animation curves, roads, rivers, or any motion/path system that must feel smooth.

Design and review game spatial query code for raycasts, picking, collision predicates, containment tests, orientation tests, and point/line/plane distances. Use when implementing or debugging ray-triangle hits, point-in-triangle checks, barycentric constraints, signed distance tests, or geometry predicates.

Design or evaluate game story, world, characters, spaces, presence, aesthetics, and indirect control. Use when adding narrative, quests, levels, environments, character arcs, worldbuilding, environmental storytelling, or emotional context to gameplay.

Design and debug game transform systems, coordinate spaces, local/world/view/projection matrices, homogeneous coordinates, camera constraints, and inverse transforms. Use when implementing object transforms, camera math, parent-child transforms, projection/unprojection, or coordinate-space conversions.

Apply vector math primitives for game rendering, collision, orientation, lighting, steering, and geometry predicates. Use when working with dot products, cross products, triple products, normals, projections, signed areas, signed volumes, facing checks, or vector normalization.

Plan, qualify, pitch, and track guest post placements that build links and expertise through audience-specific, citation-justified, editorially placeable off-site content. Use when checking guest post viability, making sales pages citable, creating guest post pitch titles, assessing publisher quality, reviewing guest post outreach, or tracking placements.

Design degradation holdbacks and long-term cumulative holdbacks for product experiments and feature rollouts. Use when a team needs a long-term counterfactual, wants to measure delayed impact after launch, is worried about metric degradation over time, needs to decide holdback size or duration, or must weigh the user/business cost of withholding a feature.

Design and review htmx endpoint contracts for server-rendered HTML fragments. Use when adding or debugging hx-get, hx-post, hx-put, hx-patch, hx-delete, hx-target, hx-swap, hx-select, out-of-band swaps, HX-Trigger events, partial template responses, redirects, retargeting, or response headers.

Plan and bootstrap server-driven web applications with htmx. Use when choosing htmx versus an SPA framework, setting up htmx in a server-rendered app, designing the first CRUD workflow, explaining the htmx mental model, or deciding how much JavaScript a server-driven feature needs.

Coordinate htmx with lightweight browser-side interactivity. Use when adding Alpine.js, _hyperscript, local UI state, custom events, dialogs, transitions, keyboard behavior, or browser-only state around htmx swaps in a server-rendered app.

Use the htmx JavaScript API for imperative integration in server-rendered apps. Use when calling htmx.ajax, htmx.process, htmx.trigger, htmx.on, htmx.off, htmx.onLoad, htmx.find, htmx.findAll, htmx.closest, htmx.addClass, htmx.removeClass, htmx.toggleClass, htmx.takeClass, configuring htmx.config, logging htmx events, or integrating non-htmx JavaScript with swapped content.

Build and review realtime and near-realtime htmx features. Use when implementing polling, load polling, job status updates, WebSockets, Server-Sent Events, htmx ws or sse extensions, streaming server-rendered fragments, multi-client updates, reconnect behavior, or deciding between polling, SSE, and WebSockets.

Implement common htmx interaction recipes in server-rendered web apps. Use when building lazy loading, boosted links/forms, active search, inline validation, delete buttons, CSS transitions, form reset, optimistic updates, pagination, infinite scroll, toggled selection, polling, custom dialogs, request headers, click-to-edit, or HTML/JSON endpoint splits.

Review and harden security for htmx and server-driven web apps. Use when handling user-supplied HTML, escaping or sanitizing fragments, adding CSP, evaluating XSS risk, configuring CSRF or cookies, loading htmx from a CDN, using SRI hashes, accepting hx-* attributes from content, or reviewing htmx request headers and history caching.

Evaluate A/B tests for inclusive product impact across user groups, accessibility needs, device constraints, privacy behavior, bandwidth, geography, and underrepresented segments. Use when checking whether an experiment benefits or harms different user groups, planning segmentation dimensions, auditing test/control balance, interpreting subgroup effects, or reviewing product changes for inclusive experimentation.

Use when auditing landing pages, emails, sales scripts, pricing flows, fundraising asks, product UX, or negotiations for persuasion mechanisms, pressure tactics, manipulation risk, fake urgency, fake social proof, authority misuse, or ethical rewrites.

Use JavaScript number math safely for front-end UI behavior, including expressions, precedence, coercion, NaN, Infinity, floating-point precision, BigInt limits, modulo wrapping, rounding, random values, and repeatable UI randomness. Use when building sliders, carousels, counters, animation values, randomized UI, financial-ish display values, or debugging numeric edge cases in browser JavaScript.

Design sustainable link-building campaigns that connect business goals, linkable assets, publisher ecosystems, metrics, resources, and campaign templates. Use when planning a link-building campaign, choosing tactics, defining link-building KPIs, mapping links to business outcomes, or turning SEO authority goals into an executable campaign brief.

Plan, draft, review, and operate audience-relevant link outreach campaigns with personalization, subject lines, response handling, tracking, and bulk-send guardrails. Use when writing link outreach emails, pitching resource pages, handling outreach replies, planning blogger or journalist outreach, reviewing subject lines, or managing link acquisition workflows.

Qualify, score, filter, and prioritize link-building prospects by relevance, trust, editorial quality, authority, outreach fit, spam risk, and asset readiness. Use when reviewing raw URL lists, deciding which sites are worth outreach, auditing link target quality, segmenting prospects, or rejecting risky link opportunities.

Research link-building opportunities by mapping assets to opportunity types, building query libraries, analyzing competitor backlinks, finding scrapeable lists, and expanding prospecting seeds. Use when finding link prospects, creating link prospecting queries, mapping guest post/resource/directory opportunities, or producing a prospect research map before qualification or outreach.

Find, prioritize, and reclaim missed link opportunities from unlinked brand mentions, image uses, content citations, broken owned URLs, outdated references, and attribution gaps. Use when auditing mentions, requesting credit links, fixing attribution, handling negative mentions, or salvaging lost backlinks.

Plan, audit, and prioritize linkable assets that publishers, curators, experts, and community owners have a real reason to cite. Use when creating link-worthy content ideas, auditing existing assets, turning market pains into assets, analyzing competitor linkable content, or deciding what to build before link prospecting and outreach.

Audit and improve the site architecture around linkable content before promotion, including orphan pages, internal links, hubs, URL stability, crawlability, canonicals, conversion paths, and link equity flow. Use when a linkable asset exists but may be buried, isolated, technically weak, or poorly connected to business pages.

Plan, draft, repurpose, and audit LinkedIn articles and newsletters that demonstrate expertise and support a professional content strategy. Use when writing long-form LinkedIn articles, newsletter editions, article teasers, follow-me articles, issue plans, or post-to-newsletter repurposing.

Write and audit LinkedIn comments and reply strategies that add professional value, start useful discussion, and increase ethical visibility. Use when drafting comments on LinkedIn posts, replying to comments, improving comment prompts, or planning comment-based engagement without spam.

Generate and prioritize LinkedIn content ideas from audience problems, industry news, questions, hashtags, competitor posts, source material, and growth experiments. Use when planning LinkedIn post topics, content calendars, thought-leadership angles, post series, or idea backlogs.

Plan, measure, and iterate LinkedIn content experiments using post hypotheses, format tests, analytics, comments, and learning loops. Use when comparing LinkedIn hooks, formats, topics, hashtags, posting cadence, newsletters, documents, videos, or content performance data.

Draft, revise, and audit LinkedIn feed posts for professional visibility, personal brand, audience value, comments, and ethical reach. Use when writing LinkedIn posts, feed updates, text posts, document or video captions, hashtag/mention plans, post hooks, or short-form LinkedIn content.

Plan, prospect, evaluate, fulfill, and measure local sponsorship campaigns that build local visibility, relationships, and links through events, nonprofits, community organizations, and local publishers. Use when finding local sponsorship link opportunities, evaluating sponsorship packages, building local links through nonprofits or events, measuring sponsorship ROI, or using local relationships for SEO.

Choose methods for measuring long-term product impact after or beyond an A/B test. Use when comparing long-term holdbacks, post-period analysis, continuous monitoring, CLV models, delayed effects, short-term versus long-term metric tradeoffs, or lower-cost alternatives to long-term holdbacks.

Make a product, landing page, pricing page, launch page, free tool, or social preview easier to understand, buy, remember, and share using Marc Lou-inspired viral product patterns.

Analyze nonfiction manuscripts for reader engagement signals, including heading-level word counts, slow starts, long slogs, weak takeaway titles, value pacing, beta-reader comment dropoff, and abandonment risks. Use when auditing a book, guide, manual, course-like draft, or technical manuscript for value density, reader experience, or beta-feedback engagement patterns.

Plan evaluation strategies for machine-learning product changes. Use when deciding between offline evaluation, interleaving, online A/B tests, multi-armed bandits, or model filtering for ranking, recommendation, search, personalization, or other ML-powered user experiences.

Model target players, motivations, emotions, pleasures, needs, flow, novelty, judgment, and interest curves. Use when defining who a game is for, shaping retention, diagnosing boredom or confusion, designing progression, or aligning gameplay with a desired emotional arc.

Create product-led SEO strategies that turn product value, user intent, page architecture, taxonomy, and scalable user experiences into organic growth. Use when a user asks for SEO strategy, organic growth planning, content/product SEO, programmatic SEO direction, search moat creation, or wants to avoid keyword-list SEO.

Use Python mocks and fakes as a design tool without losing behavioral confidence. Use when testing external dependencies, choosing monkeypatch versus unittest.mock.patch, isolating slow boundaries, avoiding mock-heavy tests, interpreting mock call assertions, or refactoring toward clearer dependency seams.

Audit and revise practical nonfiction drafts for reader experience, value pacing, front-loaded insight, value-per-page, boredom, and beta-readiness. Use when editing, restructuring, shortening, or reviewing a book, guide, manual, course-like manuscript, or long-form educational draft so readers receive useful value quickly and keep reading.

Use when designing or auditing free samples, lead magnets, trial offers, concessions, referral gifts, favor exchanges, freemium onboarding, consultation offers, or give-first sales strategies where reciprocity, obligation, uninvited gifts, or concession tactics may affect decisions.

Build link opportunities through genuine publisher, expert, partner, and community relationships before asking for mentions or links. Use when planning reciprocity-first outreach, expert roundups, content promotion networks, partner collaboration, warm pitches, or long-term link relationship systems.

Derive, review, and debug responsive web layout math for fluid widths, media query ranges, viewport units, percentages, and CSS clamp() formulas. Use when building responsive layouts, converting fixed designs to fluid CSS, calculating breakpoints, choosing vw/svw/lvw/dvw units, or deciding whether CSS math or JavaScript measurement should own a layout behavior.

Use when adding, changing, testing, or debugging Rust HTTP APIs and services, especially when Codex needs black-box integration tests, random-port app startup, real database test isolation, external HTTP mocks, or CI-ready cargo verification for Actix, Axum, Warp, Rocket, or similar Rust web frameworks.

Design and review Rust async code around task ownership, suspension points, cancellation, blocking work, and runtime boundaries. Use when writing, refactoring, or reviewing futures, async functions, Tokio tasks, spawn, JoinHandle, Send futures, async traits, cancellation, or mutexes across await points.

Build and review Bevy game asset loading pipelines with typed asset catalogs, path validation, loading states, handle ownership, sprite sheets, audio, and runtime resource checks. Use when organizing Bevy assets, replacing hard-coded paths, adding loading screens, diagnosing missing handles, or packaging Rust game resources.

Design and review Bevy 2D collision broadphase systems with AABB bounds, spatial indexes, typed collision events, and benchmark-driven test beds. Use when replacing O(n^2) collision checks, adding spatial partitioning, diagnosing Bevy collision performance, or separating broadphase, narrowphase, and response systems in Rust games.

Design and review Bevy fixed-step 2D physics loops with velocity components, deterministic movement, collision prediction, interpolation, impulses, and tweened presentation. Use when movement depends on frame rate, collision misses appear at high speed, physics and animation are tangled, or Bevy gameplay needs stable simulation steps.

Build and review Bevy procedural world generation with grid resources, deterministic seeds, reachability checks, chunk or room spawning, background generation boundaries, and gameplay-safe entity materialization. Use when creating tile maps, dungeon-like spaces, mining bases, or generated levels in Rust Bevy games.

Design and review Bevy game state flow with plugins, AppState enums, OnEnter and OnExit setup, state-scoped cleanup, menus, pause screens, transitions, and run conditions. Use when adding reusable Bevy game state management, debugging duplicated entities after transitions, or separating menu, loading, playing, paused, and game-over logic.

Build and review bracket-lib style Rust 2D game loops, state structs, game modes, input handling, rendering calls, and restart flow. Use when creating a small Rust game with bracket-lib, porting a tutorial loop, or debugging tick/update/render state behavior.

Design and review thread-based Rust concurrency with explicit ownership, sharing, and synchronization choices. Use when writing, refactoring, or reviewing threads, scoped threads, channels, Arc, Mutex, RwLock, Condvar, atomics, OnceLock, LazyLock, Send, Sync, deadlocks, or shared state.

Prepare Rust crates for publishing with Cargo metadata, versioning, README and license checks, package dry-runs, feature verification, docs.rs readiness, examples, changelog notes, and secret-safe release gates. Use before cargo publish, crate release PRs, or sharing a reusable Rust library.

Move Rust game monsters, items, loot, effects, spawn weights, level gates, and balance numbers into validated data files using Serde-friendly schemas. Use when replacing hard-coded spawn functions, adding RON or JSON content templates, or making game content editable without recompiling.

Use when preparing, containerizing, configuring, testing, or reviewing Rust services for deployment, especially Docker multi-stage builds, runtime configuration, environment overrides, secrets, health checks, SQLx offline builds, release profiles, image-size reduction, or production startup validation.

Use when modeling, validating, refactoring, or reviewing Rust service domain boundaries, especially when replacing primitive String fields with newtypes, parse-don't-validate constructors, private invariants, TryFrom/FromStr parsers, request DTO boundaries, or property tests.

Use when adding, changing, debugging, or reviewing Rust service error handling and observability, especially when separating domain errors from HTTP responses, adding thiserror/anyhow, implementing ResponseError or IntoResponse, adding tracing spans, redacting secrets, or diagnosing async failures.

Design and review Rust FFI boundaries that keep raw declarations isolated behind safe ownership, lifetime, error, and cleanup wrappers. Use when writing, refactoring, or reviewing unsafe extern blocks, C ABI wrappers, repr(C) types, CString, CStr, raw handles, Drop cleanup, bindgen, cbindgen, or panic-safe foreign boundaries.

Finish and package small Rust games with MVP lock, playability checks, resource packaging, release builds, smoke tests, and disciplined post-MVP polish. Use when preparing a Rust game prototype for sharing, packaging bracket-lib assets, or deciding what finishing work belongs before release.

Plan small, playable Rust game implementation slices from a short design brief, MVP, stretch goals, and acceptance checks. Use when starting a Rust game, scoping a prototype, converting a game idea into work items, or preventing an AI coding agent from overbuilding.

Use when designing, implementing, testing, or debugging Rust service workflows that must be safe under retries, duplicate requests, crashes, concurrent submissions, background workers, queues, email/payment/notification side effects, idempotency keys, transaction isolation, or save-and-replay API behavior.

Design and review Rust iterator pipelines and collection code for clear ownership, allocation, ordering, and error behavior. Use when writing, refactoring, or reviewing iterators, HashMap Entry usage, collect, FromIterator, Extend, custom iterators, or allocation-heavy loops.

Design and review Rust ECS gameplay code using Legion-style entities, components, resources, systems, schedules, queries, command buffers, and spawners. Use when building ECS-driven Rust game features, migrating game state into ECS, or debugging system ordering and component composition.

Optimize Rust libraries with criterion benchmarks, feature-flag matrices, cargo bench workflows, dependency gating, regression baselines, and evidence-driven API performance tradeoffs. Use when adding or reviewing Rust library benchmarks, cargo features, optional dependencies, or performance claims before publishing.

Design and review Rust ownership, borrowing, lifetimes, and interior mutability so data flow matches the domain model. Use when writing, refactoring, or reviewing Rust code that hits move, borrow checker, aliasing, Clone, Copy, Rc, Arc, RefCell, or lifetime problems.

Design and review Rust roguelike procedural maps, map-builder traits, generator harnesses, field-of-view, spatial memory, Dijkstra/pathfinding, and simple monster AI. Use when adding dungeon generation, FOV, map memory, chasing behavior, or visibility-constrained AI to a Rust game.

Use when adding, changing, testing, or reviewing security-sensitive Rust web service behavior, especially login flows, password hashing, credential checks, session cookies, flash messages, admin route protection, auth middleware, user enumeration defenses, or moving CPU-heavy password work off async executors.

Use when adding, changing, testing, or reviewing Postgres persistence in Rust services that use sqlx, especially when designing migrations, query! or query_as! calls, PgPool injection, transactions, compile-time checked SQL, SQLx offline mode, repository boundaries, or database-backed integration tests.

Design and review Rust tile maps, map indexing, collision checks, map builders, camera-relative rendering, layered drawing, and tile themes. Use when building 2D grid worlds, roguelike maps, tile cameras, or bracket-lib style rendering systems.

Design and review Rust trait APIs, generic bounds, dispatch models, and conversion contracts for clear public interfaces. Use when designing, refactoring, or reviewing traits, generics, trait objects, associated types, impl Trait, From/TryFrom, AsRef, Borrow, or crate APIs.

Build and review turn-based Rust game flow using turn-state enums, phase-specific schedules, intent messages, movement resolution, combat resolution, wait actions, and win/loss states. Use when implementing roguelike turns, tactical action order, ECS message entities, or decoupled input and action systems.

Isolate and review unsafe Rust behind small, documented, testable boundaries with explicit invariants. Use when writing, refactoring, or reviewing unsafe code, raw pointers, unsafe functions, unsafe traits, MaybeUninit, pointer aliasing, panic safety, Miri checks, or safe abstractions over unsafe internals.

Write and review Rust library documentation with rustdoc module docs, public API examples, doctests, examples directories, missing-docs gates, docs.rs readiness, and user-first crate narratives. Use when documenting a Rust crate, improving docs before publishing, or turning examples into tested rustdoc.

Plan and write SaaS documentation for managed services, continuous releases, provider/customer responsibility boundaries, UI/browser constraints, runbooks, support enablement, and release readiness. Use when documenting cloud products, hosted services, admin consoles, fleet-wide changes, service operations, incident or runbook procedures, SaaS release notes, customer-controlled settings, or internal docs that support customer experience.

Audit and improve commercial pages so they have legitimate citation reasons for guest posts, resource pages, digital PR, partnerships, and editorial mentions. Use when a sales page needs citable sections, proof points, tools, data, definitions, expert quotes, or less promotional link targets before outreach.

Operate scaled link outreach with segmentation, templates, personalization variables, pilot batches, suppression lists, deliverability checks, reply diagnostics, compliance review, and campaign reporting. Use when planning bulk outreach, reviewing email operations, scaling a proven offer, or debugging low reply rates.

Use when designing or auditing deadlines, limited seats, inventory messages, waitlists, expiring discounts, launch windows, limited editions, loss-framed copy, competition cues, checkout urgency, or scarcity claims that may create pressure to act quickly.

Plan and check the final production tasks for self-publishing nonfiction books, including copyediting, final review readers, proofreading, layout, cover files, print-on-demand, ISBNs, and launch-readiness sequencing. Use when preparing a manuscript for publication after beta reading or when auditing a self-publishing checklist.

Find product-led and blue-ocean SEO opportunities from customer demand, query behavior, competitive gaps, search result features, communities, and proprietary product strengths. Use when researching SEO opportunities, organic growth ideas, competitive SEO gaps, programmatic SEO concepts, or when keyword tools show little volume.

Map SEO personas, search intent, funnel stage, expected content format, CTA, device context, and localization needs into actionable organic search plans. Use when planning keyword research, SEO content briefs, funnel mapping, search intent analysis, persona-driven content, or when traffic is not converting.

Prioritize SEO initiatives as product roadmap work with impact, effort, confidence, resourcing, executive pitch, cross-functional ownership, quarterly planning, and business KPI alignment. Use when building SEO roadmaps, scoring SEO work, requesting engineering/design/content resources, annual planning, executive buy-in, or turning SEO recommendations into product-ready asks.

Use when the user is unsure which LVTD skill or marketplace plugin fits their problem, asks what skill to use, describes a cross-domain workflow, or needs help choosing among installed or source LVTD skills.

Use when selecting, writing, or auditing testimonials, reviews, ratings, case studies, usage stats, customer logos, waitlists, community signals, popularity claims, marketplace rankings, group-norm messages, or any proof that relies on what other people do or believe.

Design hands-on technical nonfiction chapters as runnable labs, worked examples, exercises, checkpoints, troubleshooting paths, and reader outcomes. Use when turning technical book sections, tutorials, self-hosting chapters, DevOps guides, programming lessons, or infrastructure explanations into practical labs that readers can complete and verify.

Verify technical nonfiction manuscripts for runnable accuracy, including commands, configuration, code snippets, links, version drift, screenshots, prerequisites, security warnings, expected outputs, and reproducibility. Use when auditing self-hosting, DevOps, programming, infrastructure, data, security, or software tutorial drafts before beta reading, publication, or release.

Diagnose technical SEO issues using discovery, crawling, indexing, ranking, Google Search Console, internal links, crawl budget, canonicals, duplicate content, redirects, and migration risk. Use when traffic drops, pages are not indexed, Search Console shows errors, canonicals differ, migrations are planned, or a technical SEO audit is needed.

Design a sustainable test architecture using test desiderata, test pyramid tradeoffs, fast and slow test separation, integration boundaries, CI feedback loops, and architecture choices that make code testable. Use when a test suite is too slow, too brittle, too mock-heavy, unclear about unit vs integration coverage, or needs a testing strategy before major growth.

Apply the Bullseye framework from Traction to brainstorm, rank, test, and focus startup traction channels. Use when choosing growth channels, overcoming channel bias, prioritizing marketing experiments, or deciding which acquisition channel deserves focused effort.

Research and shortlist startup traction channels before running Bullseye tests. Use when comparing acquisition channels, studying how similar companies grew, finding underused distribution strategies, or preparing the outer ring for a Traction-style growth process.

Set traction goals and identify the Critical Path from Traction so teams focus only on milestones needed for growth. Use when a startup has too many priorities, needs growth goals, is debating product versus marketing work, or wants to decide what not to do.

Design email marketing traction tests from Traction for acquisition, engagement, retention, revenue, and referrals. Use when planning email courses, newsletter sponsorships, lifecycle sequences, retention emails, or email-driven growth experiments.

Plan existing-platform, trade show, offline event, speaking, and community-building traction experiments from Traction. Use when testing platform distribution, conferences, meetups, talks, forums, local events, or community-led startup growth.

Plan paid acquisition tests from Traction across SEM, social/display ads, and offline ads. Use when designing ad experiments, keyword tests, audience tests, paid channel budgets, or deciding whether a paid channel can acquire the right customers profitably.

Plan business development, sales, and affiliate traction experiments from Traction. Use when testing partnerships, direct sales conversations, outbound lists, affiliate programs, channel partners, or revenue-oriented startup acquisition channels.

Plan PR-oriented traction experiments from Traction, including targeting blogs, publicity, and unconventional PR. Use when pitching bloggers or reporters, designing publicity stunts, earning launch coverage, or validating PR as a startup growth channel.

Review traction experiment results and recommend whether to double down, iterate, repeat Bullseye, or pivot. Use when analyzing growth test data, comparing channel performance, deciding if a channel moved the needle, or reassessing startup traction strategy.

Plan SEO and content marketing traction experiments from Traction. Use when creating organic growth tests, SEO page strategies, content calendars, blog experiments, link-building tests, or deciding whether content can become a core acquisition channel.

Design cheap, measurable traction tests from Traction for startup growth channels. Use when planning marketing experiments, middle-ring tests, A/B tests, acquisition test spreadsheets, channel validation, or growth experiment success criteria.

Plan viral marketing and engineering-as-marketing traction experiments from Traction. Use when designing referral loops, viral coefficients, engineered acquisition tools, calculators, microsites, widgets, or product-led assets that acquire customers; use make-product-viral instead for landing-page audits, shareability reviews, pricing-page polish, or social-preview optimization.

Use when improving cold outreach, sales conversations, customer discovery, community moderation, referral asks, partnership messages, interviews, or relationship-based persuasion where similarity, compliments, familiarity, cooperation, association, or rapport may affect trust.

Assess whether experiment results are credible enough to influence product decisions. Use when checking false positive or false negative risk, underpowered metrics, suspiciously large lifts, replication needs, meta-analysis, stratified sampling, covariate adjustment, or whether A/B test insights should be trusted.

Design and review visual content for developer documentation, including screenshots, architecture diagrams, boxes-and-arrows diagrams, flowcharts, swimlanes, video decisions, accessibility, performance, annotations, and visual maintenance. Use when creating or auditing diagrams, screenshots, visual explanations, or media in technical docs.