Explicit advanced workflow for generating, inspecting, dry-running, and validating plain FDM `.gcode` with real slicer CLIs. Use only when the user asks Replicator to generate G-code, needs headless/reproducible slicing, or cannot use a slicer UI.

SDFormat/SDF model and world generation, validation, and simulator handoff. Use for `.sdf` files, SDFormat XML, Python `gen_sdf()` sources, models, worlds, links, joints, poses, frames, inertials, visual/collision geometry, mesh URIs, sensors, lights, physics, plugins, includes, Gazebo, static SDF review, or simulator-specific metadata. Do not use for signed-distance-field geometry.

Patch the code so `scripts/local-checks.sh` passes, after /implement-mainspec — a narrow post-implement polish specialist. Reads the (remediation-rich) check failures, fixes the underlying cause, never silences a check, re-verifies, and commits. Invoked headless by the dispatcher's two-strike local-checks gate; the dispatcher owns the retry counter. Triggers - fix-local-checks, fix lint, fix local checks, fix typecheck, make checks pass, post-implement polish (project)

Work on the `snb-worktime-webui` project in the SNB repository: a Go application with an embedded web UI for calculating employee worktime from Windows session snapshots and workstation or network activity windows. Use when adding features, fixing bugs, adjusting parsing rules, changing calculation logic, refining the web UI, updating Windows build flow, or integrating new telemetry sources for this specific project.

Use this skill for Panda CSS work: setting up or migrating @pandacss/dev, editing panda.config.* files, integrating PostCSS or the Panda CLI, using generated styled-system imports, css/cva/recipes/patterns/jsx APIs, tokens and semantic tokens, staticCss or dynamic styling, and troubleshooting missing generated styles or extraction issues.

Integrate and use argon-router in React web applications with Effector. Use when tasks involve creating routes and routers, wiring RouterControls/history adapters, composing routes with chainRoute/group/createVirtualRoute, rendering views with RouterProvider/createRoutesView/Outlet, building links with Link/useLink, and managing URL query state with trackQuery and @argon-router/paths.

Test a client against a Prism mock server built from an OpenAPI spec. Use when the user wants to test against a mock API, drive a client or harness through an OpenAPI spec, verify request payloads or 422 behavior against a spec, or when a task needs a local fake of a REST API for fast, deterministic testing.

Performs genomic interval overlap, nearest, merge, coverage, complement and subtraction on Polars DataFrames, and reads or writes BED, VCF, BCF, BAM, CRAM, GFF, GTF, FASTA and FASTQ data. Use for coordinate-aware genomic joins, read-depth analysis, lazy bioinformatics I/O, SQL queries or migration from bioframe.

Implements and debugs browser Summarizer, Writer, and Rewriter integrations in JavaScript or TypeScript web apps. Use when adding availability checks, model download UX, session creation, summarize or write or rewrite flows, streaming output, abort handling, or permissions-policy constraints for built-in writing assistance APIs. Don't use for generic prompt engineering, server-side LLM SDKs, or cloud AI services.

Implements and debugs browser Translator API integrations in JavaScript or TypeScript web apps. Use when adding Translator support checks, language-pair availability flows, model download UX, session creation, translate() or translateStreaming() calls, input-usage measurement, or permissions-policy handling for on-device translation. Don't use for server-side translation SDKs, cloud translation services, or generic multilingual content pipelines.

Installs, configures, audits, and operates Agent Package Manager (APM) in repositories. Use when initializing apm.yml, installing or updating packages, validating manifests, managing lockfiles, compiling agent context, browsing MCP servers, setting up runtimes, or packaging resolved context for CI and team distribution. Don't use for writing a single skill by hand, generic package managers like npm or pip, or non-APM agent configuration systems.

Implements and debugs browser Proofreader API integrations in JavaScript or TypeScript web apps. Use when adding Proofreader availability checks, monitored model downloads, proofread flows, correction metadata handling, or permissions-policy checks for built-in proofreading. Don't use for generic prompt engineering, server-side LLM SDKs, or cloud AI services.

Implements and debugs browser Language Detector API integrations in JavaScript or TypeScript web apps. Use when adding LanguageDetector support checks, availability and model download flows, session creation, detect() calls, input-usage measurement, permissions-policy handling, or compatibility fallbacks for built-in language detection. Don't use for server-side language detection SDKs, cloud translation services, or generic NLP pipelines.

Implements and debugs browser WebMCP integrations in JavaScript or TypeScript web apps. Use when exposing imperative tools through document.modelContext (with a navigator.modelContext fallback), annotating HTML forms for declarative tools, handling agent-invoked form flows, or validating WebMCP behavior in the current Chrome preview. Don't use for server-side MCP servers, REST tool backends, or non-browser providers.

Review one linked Oracle Forms legacy-evidence package produced by leg-spec-from-code-oracle for semantic relationships, cross-fact ambiguities, apparent conflicts, missing runtime context, and source-supported reconciliations. Use after Oracle code evidence extraction and before target requirement curation when the master specification and its operation, decoded-source, and database children need a human-readable semantic review overlay without modifying extracted evidence or generating target requirements, UI designs, tests, or implementation decisions.

Answer questions about live production system behavior — current variable values, execution durations, hit counts, and value distributions — by instrumenting running services with Lightrun MCP tools. Use when the question requires live runtime data rather than static code analysis (e.g. "show recent requests to this endpoint", "show the runtime distribution for this operation", "what values appear for this expression in production?", "which branch runs for customer X?"). Do not use for incident diagnosis, pull-request review, code changes, setup, or deployment. Route latency, timeout, deadline, SLO, or hang diagnosis to lightrun-slow-execution-diagnosis when available; route other diagnosis, or fallback when that skill is unavailable, to lightrun-live-runtime-debugging when available. If neither diagnosis skill is available, report the scope gap.

Creates and edits trusted local Letta Code mods, including tools, slash commands, local-only model providers, lifecycle/turn events, scoped conversation helpers, panels, and capability-gated behavior. Use when asked to make a mod, add an agent-callable tool, add a slash command, add a local provider/model adapter, transform turns, react to app events, or add lightweight mod UI outside the dedicated /statusline flow.

Add fast, local, typed decisions to any project with Laya, an open-source non-generative decision model (pip install laya). It classifies, routes, scores and answers yes/no questions about a piece of text, returning calibrated probabilities in roughly 20-35 ms on a laptop GPU, with no LLM call and no data leaving the machine. Use this skill whenever the user wants to classify or route text, triage tickets or emails, detect spam, phishing, toxicity or intent, put a guardrail in front of an agent or LLM, score something against a rubric, or replace an LLM-based classifier to cut latency or cost. Also use it when they mention Laya, Jev, a "System 1 model", "typed decisions" or a "decision model", even if they never name Laya.

Creates Architecture Decision Records (ADRs) in MADR format and arc42 documentation. Generates plan-context.md as the context bridge to Claude Code. Use this skill when the user mentions "architecture", "ADR", "arc42", "Architecture Decision", "tech stack", "solution design", "system design", "architecture review", "plan-context", or similar. Also when requirements exist and the next step is technical structuring. This skill creates PROPOSALS. Claude Code makes the final decisions based on the real state of the codebase.

Author an engineering-change Product Requirements Document (PRD) that requires inspecting a code repository — verifying the requester's claims against the actual codebase, interviewing them down the design tree, deciding module and interface boundaries, then filing the result as a GitHub or GitLab issue. Use when the deliverable is a repo-grounded implementation spec for engineers. Trigger on "spec this feature out", "turn this idea into an issue", "engineering PRD", "write this change up before we build it", "plan this against the codebase", or a rough feature idea that must become an actionable engineering spec. Runs five phases (INTAKE, VERIFY, INTERVIEW, MODULES, WRITE + FILE) gated on a decision ledger. Boundary — for PM-facing product requirements aimed at stakeholders (Lean PRD, one-pager, AARRR or HEART metrics) use `prd-generator` instead.