mikewolfd

Use when the user explicitly asks for a multi-agent coding session (pair program, XP session, popcorn, subagent pair work). Matches **popcorn-xp** plugin — file-bus / **session task-*** (default). For native Agent Teams, use **popcorn-xp-team** plugin + **popcorn-xp-team** skill.

Popcorn XP pair-programming protocol — core rules, advice lifecycle, session file formats, subagent and Agent Teams transports for teammates in an XP session. Auto-loaded into popcorn-xp agents via the skills field.

Use when the user explicitly wants Popcorn XP with **native Claude Agent Teams** (coordinator lead, TaskUpdate, SendMessage, context-store hooks). Matches **popcorn-xp-team** plugin. For default file-bus workflow, use **popcorn-xp** plugin + **popcorn-xp** skill.

Popcorn XP pair-programming protocol — core rules, advice lifecycle, session file formats, and subagent transport for teammates in an XP session. Auto-loaded into popcorn-xp agents via the skills field. Native agents from other plugins should invoke this skill as their first action to load the protocol.

Use when the user asks for a multi-agent XP-style session on Codex — "pair program", "xp session", "popcorn", "popcorn this task", "team of agents", or subagent pair work with LOG.md and ADVICE.md. Subagent/file-bus mode only (no Claude Agent Teams). Lead orchestrates; driver, navigator, and advisor use the vendored protocol skills.

Manage the user's soap-making supply inventory (oils, butters, fats, additives). Cross-references items against the soap-calc oil and additive JSON databases and saves a validated inventory.md file. Use when the user: (1) lists oils or additives they have on hand, (2) asks to add or remove items from their inventory, (3) asks to show, update, or clear their inventory, or (4) says things like "here's what I have" or "add castor oil to my inventory." Do NOT use for recipe formulation or lye calculations — use the soap-formulation skill for those.

Expert soap recipe formulation, troubleshooting, and educational guidance for cold process (CP), hot process (HP), bar soap (NaOH), and liquid soap (KOH). Use when the user asks to: (1) formulate or generate a soap recipe, (2) troubleshoot soap problems ("why is my soap soft/crumbly/not lathering/getting DOS"), (3) substitute or compare oils, (4) review or improve an existing recipe, (5) get formulation advice on fatty acid balance, superfat levels, or additive choices, or (6) learn about soap making chemistry and techniques. Do NOT use for melt-and-pour soap, syndet bars, or cosmetic regulatory questions.

Use when the user asks to review code changes, a PR, a diff, or a patch. Apply a semi-formal review workflow: explore methodically, ground claims in file:line evidence, trace callers/callees and tests, and produce a structured findings-first review.

Use when auditing or debugging web UI accessibility — running a WCAG audit or a11y sweep of a site, page, or branch diff, OR interactively diagnosing a reported accessibility issue: a screen-reader / VoiceOver, keyboard, focus, focus-trap, contrast, ARIA, form-error, live-region, or modal problem in a rendered web app, or a failing axe / a11y check. Covers DOM-first audits and inline component debugging on macOS with VoiceOver.

This skill should be used when the user asks about the U.S. Web Design System (USWDS), including USWDS components, USWDS utility classes, USWDS design tokens, USWDS patterns, government website design, Section 508 accessibility for USWDS, USWDS Sass settings, USWDS theme settings, USWDS color tokens, USWDS typography tokens, USWDS spacing tokens, USWDS layout grid, installing USWDS, USWDS Sass compilation, or building accessible government web interfaces. Relevant when the user says things like "which USWDS component should I use", "what USWDS utility class", "how do I use USWDS design tokens", "USWDS form pattern", "USWDS accessibility", "government design system", "how do I install USWDS", "USWDS theme settings", or "configure uswds-core".