Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing test registry or TESTS.md. Use for test inventory, test gap analysis, unit/integration/contract/E2E/smoke classification, bug-to-test regression protection, consumer/provider contract testing, test-necessity review, and pre-delivery evidence review.

Audits CLAUDE.md files and `.claude/rules/` for context bloat and emits ranked fixes — trim inventory entries, extract sections, flag rarely-used skills for slash-only. Invoke with /optimize-claude-md [audit|trim|extract] for "CLAUDE.md is too big" or the large-CLAUDE.md warning.

Plans, generates, runs, and heals Maestro end-to-end flows for Expo and React Native apps, spec-first, with `testID` locators and Maestro Cloud via EAS. Use for native flows (web flows go to `e2e-testing`); triggers on "add mobile e2e", "maestro flow", "expo e2e", "/e2e-testing-mobile".

Plans, generates, runs, and heals Playwright end-to-end tests through a spec-first loop with Playwright Test Agents and `@playwright/mcp`. Use when adding E2E coverage or hardening a flaky flow; triggers on "add e2e", "test this flow", "verify the user journey", "/e2e-testing".

Projeta telas, fluxos e design systems; audita UX, acessibilidade e corrige achados focados. Facelift amplo vai para `89-ui-facelift`. Trigger em: "design system", "wireframe", "aesthetic anchor", "responsiva em telas", "protótipo no Figma", "paleta", "WCAG", "componente visual", "mobile first", "decisão de UX", "auditar essa tela", "design dessa interface".

Azure AI Vision Image Analysis SDK for captions, tags, objects, OCR, people detection, and smart cropping. Use for computer vision and image understanding tasks.

Collect volatile forensic evidence from a compromised host by following the order of volatility, preserving memory, network connections, running processes, and system state with documented chain of custody before they are lost. Use before isolating, shutting down, or remediating a compromised host, especially when fileless or memory-resident malware is suspected, root cause analysis is needed, or the evidence must hold up in legal proceedings.

Manage a stateful, run-directory-based proof project: continuation across runs, run-local source bookkeeping, manual GPT Pro handoff packages when a local attempt stalls, and an optional DeepSeek second opinion as additional evidence only. Use when the user asks for proof-run orchestration, a GPT Pro handoff, or cross-run proof continuation — use /proof-writer for ordinary proof drafting and /proof-checker for rigorous verification or submission acceptance.

Use CodexBar CLI local cost usage to summarize per-model usage for Codex or Claude, including the current (most recent) model or a full model breakdown. Trigger when asked for model-level usage/cost data from codexbar, or when you need a scriptable per-model summary from codexbar cost JSON.

Debug, maintain, and use the joelclaw memory system — observer capture/dreams, Brain .svx stores, neat-memory curation, Telegram delivery, reaction grading, wiki rendering. Load whenever work touches the memory system, the curator, dreams, observations, grading, or a memory surface misbehaves.

Perform deep, multi-source research using Google Gemini's Deep Research Agent. Use this skill whenever the user asks for comprehensive research, literature reviews, competitive analysis, market research, technology surveys, or any investigation that requires synthesizing information from many web sources. Also trigger when the user says "deep research", "research this thoroughly", "do a comprehensive study on", or wants a structured report with evidence gathered from across the web — even if they don't mention Gemini by name.

Selecting WHO handles work is the Routing table; selecting HOW they handle it (Direct, Lightweight, Standard, Full) is Response Mode. This skill contains the complete decision table, exemplar prompts for each mode, the Lightweight spawn template, and the upgrade rules. Squad coordinator loads this on demand once routing has identified the agent — to pick the right ceremony level for the task.

Makes an agent crypto-native for onchain capital markets. Use for ANY question about DeFi, vaults, curators, yield, stablecoins, synthetic dollars, RWAs (real world assets), tokenized stocks, lending, perps, options, LP positions, or onchain credit. Trigger for learning ("what is a covered call", "explain post-only"), due diligence ("assess this vault", "is this APY sustainable"), trade anatomy ("what is this fund actually short"), curator comparisons, fee rails ("where does my gas fee go"), RWA mint and redeem mechanics ("is this tokenized APY real"), squeezes and manipulation ("is this a short squeeze", "is this wash traded"), crowding ("conviction or a crowded exit"), DeFi content tasks, and monitoring ("what changed this week", "they changed their Terms of Use"). Trigger even without the word DeFi when the subject is onchain yield, crypto tokens, rates, or market structure. Refresh live data before anything numeric. Not for TradFi-only rates or credit questions, LLM tokens, or transaction execution.

Entry point for authoring or modifying an MPS language — index of all aspects (structure, editor, constraints, behavior, typesystem, intentions, actions, generator, textgen, accessories, generation plans), the recommended authoring order, cross-aspect call patterns, dependency/rebuild rules, and validation flow. Start here when defining a new language or when you do not know which aspect-specific skill applies.

Start and scale networked products using Andrew Chen's "The Cold Start Problem" framework for network effects. Use when the user mentions "network effects", "chicken and egg", "cold start", "two-sided marketplace", "atomic network", "hard side", "liquidity", "critical mass", "invite-only launch", "how do I get my first users", or "the marketplace has no buyers or sellers". Also trigger when launching a marketplace, social, or collaboration product that is worthless without other users, deciding launch sequencing and seeding tactics, or diagnosing stalled network growth at scale. Covers the five stages: cold start, tipping point, escape velocity, hitting the ceiling, and the moat. For word-of-mouth virality, see contagious. For habit-driven retention, see hooked-ux.

Review a Meshtastic-Android change against KMP architecture, Compose Multiplatform and Modern Android Development conventions, starting from the four defect classes that keep recurring because neither the compiler, detekt nor spotless can see them. Use this for any PR review, for self-review before pushing, and whenever asked whether a change is safe to merge.

Configure external SAML login providers, ACS/IdP URLs, metadata, signing certificates, realms, and claims. Use for Azure or generic IdPs; portal SAML SSO app providers belong to configuration-sso-app.

Design a dynamic research team and plan using agent teams -- analyzes question, composes team, creates executable research plan. Use when the user wants to plan multi-agent research on a question or topic, or invokes /prp-research-team.

Design a dynamic research team and plan using agent teams -- analyzes question, composes team, creates executable research plan. Use when the user wants to plan multi-agent research on a question or topic, or invokes /prp-research-team.

Inspect and exercise local HTML design artifacts and library prototype previews with the existing agent-browser CLI, including screenshots, interaction checks, and rendered DOM snapshots. Use when rendered evidence helps author or review a design; excludes browser installation, remote services, and unrelated browser automation.