Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
Provides guidelines for safe git usage. Use when the user asks about "git safety", "safe git practices", "git best practices", or before performing git operations that could be destructive.
Official integration patterns for Mapbox GL JS across popular web frameworks (React, Vue, Svelte, Angular). Covers setup, lifecycle management, token handling, search integration, and common pitfalls. Based on Mapbox's create-web-app scaffolding tool.
Provides comprehensive guidance for Domain-Driven Design (DDD) concepts, strategic design, tactical design, and architecture patterns. Includes DDD applicability assessment, Pattern Boundaries table (what each pattern is and is NOT), Complexity Ladder (when to adopt each level), Core Concepts quick reference with Entity/ValueObject/Aggregate patterns, full architecture landscape overview, anti-patterns with fixes, multi-language reference implementations, and complete primary source references. Use when the user asks about DDD basics, needs to understand DDD concepts, evaluates DDD applicability, or wants an introduction to domain-driven design.
Open the prefab edit stage for a prefab instance or prefab asset GameObject. Modifications inside the edit stage propagate to all instances. Pair with 'assets-prefab-close' to exit the stage when done.
Answer-only mode. Trigger when the user is just asking a question — not requesting edits, builds, or implementations. Respond directly with the answer. No file changes, no commands, no plans.
Run a multi-agent pipeline to produce detailed technical requirements and a ticket-ready summary. Creates a feature branch, persists session state, and supports resume. Optionally seeds from a prior brainstorm or meeting session, takes the ticket from --ticket <KEY> and auto-fetches its Jira description, or starts ticket-less via --no-ticket (reconcile with a real ticket later via the reconcile subcommand). --help prints usage and starts nothing.
A soft expanding ring that draws the eye to ONE element — a primary CTA, an unread badge, a new
dot. Honors prefers-reduced-motion. One per screen; never use more than one at once or as pure
decoration (attention splits and nothing wins).
Write and run acceptance tests with axx, black-box against services (REST and OpenAPI, WireMock, SQL, MongoDB, Kafka, logs, files, web apps in real browsers, cloud services). Use when turning acceptance criteria into .feature files, adding scenarios, or editing axx.yaml.
Guide for hyperparameter selection — learning rate formulas, LoRA rank, batch size, group size, schedules, and model-specific tuning. Use when the user asks about learning rate, batch size, hyperparameter tuning, or how to configure training parameters.
Challenge a position, decision or draft with a steerable panel of expert personas before you commit, send or ship it. Use when asked to poke holes, pressure-test, find what is missing, play devil's advocate, or prepare for a meeting. For a structured, cross-checked readiness verdict, use assess-release-readiness.
Index of b3ehive's five portable swarm skills (compete, execution, learn, optimization, looper) for Codex, Claude Code, Cursor, Grok Build, opencode, OpenClaw, and Hermes.
Audit and improve web accessibility following WCAG 2.1 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
Svelte best practices for writing, editing, or reviewing Svelte/SvelteKit components and modules. Use when touching Svelte reactivity, props, events, snippets, each blocks, styling, context, actions/attachments, stores, or Svelte 5 runes.
Analiza, genera y mantiene la documentación principal del proyecto en README.md de forma profesional, técnica, viva y sin exponer secretos ni inventar información.