This is a new rule

Generate component anatomy specifications with numbered markers and attribute tables directly in Figma. Use when you need to document the structure and elements of a UI component.

Manage language versioning and perform large-scale codebase upgrades.

Interactive PRD exploration and Product Decision Record creation (greenfield)

Generates a well-formed Hacknet Computer XML node for the Gatekeeper Protocol extension. Use when the user asks to create a new node, test node, relay node, Gatekeeper node, or GP network node. Also use when adding nodes to the Extension/Nodes/ directory.

Implements backend features and bug fixes in this Go project, maintains router-based backend API documentation with request/response JSON contracts, updates Postman collections, and validates changes with build and test commands.

Test that components send correct query parameters or request arguments. Use when testing filtering, sorting, pagination, or any read operation where request parameters matter. Use for test-scoped mock customization.

After a code change, find affected tests, update them to match new behavior, then run the full validation pipeline once. Use when the user has made or asked for a code change and wants to make sure nothing is broken.

Release one or more packages from this monorepo using the scripts in `.cursor/scripts/release/`.

Create valid Opentrons Python API protocols for OT-2 and Flex robots. Use when creating, writing, editing, or helping with protocol files, liquid handling automation, or Opentrons protocol development. Also use when debugging protocol errors to trace into API source code.

Deploy RHDH to an OpenShift cluster using local-run.sh for E2E test execution, with autonomous error recovery for deployment failures

Import, merge, or combine repositories into an Nx workspace using nx import. USE WHEN the user asks to adopt Nx across repos, move projects into a monorepo, or bring code/history from another repository.

Maintains the @ekaone/mask-card TypeScript library (credit card masking). Use when working on PAN/credit card masking, maskCard/maskCardAuto/detectCardType/isValidCard changes, PCI display guidance (first 6 + last 4), docs/examples, Vitest tests, tsup builds, versioning, or npm publishing for this repo.

Updates benchmark documentation with latest results including README tables, speedup plots, and library metadata. Use when updating documentation, generating comparison tables, or when the user mentions update_docs.sh or documentation generation.

Analyzes Claude Code usage patterns and provides comprehensive recommendations. Runs usage analysis, discovers GitHub community resources, suggests CLAUDE.md improvements, and fetches latest docs on-demand. Use when user wants to optimize their Claude Code workflow, create configurations (agents/skills/commands), or set up project documentation.

Using System.CommandLine 2.0. Commands, options, SetAction, custom parsing, middleware, testing.

CSS quality audit. Checks for unused selectors, specificity issues, duplicate rules, and design token compliance.

Build tool for Go projects. Use when the user wants to create, edit, or understand Way-specific Magefiles, build targets, or automate Go project tasks.

Living documentation auditor that compares requirements vs UI/behavior vs API contract vs test results to detect spec drift, outdated docs, and undocumented features.

tiptap

Skill roster that helps select the right specialist skill for the current task. This skill is always relevant and should be consulted when the task would benefit from specialist expertise. Use proactively at the start of complex tasks.

Пиши тесты в андроид-проекте правильно. Используй этот навык при написании любых типов тестов (unit, integration, UI), тестировании бизнес-логики, сетевых функций и компонентов UI.

Use when operating peky from the CLI or TUI, especially for AI agents who need reliable, low-error procedures. Covers how to target sessions/panes correctly, use scopes, avoid confirmation prompts, and keep CLI/TUI/daemon in sync.

Use to verify if the code/logic aligns with the Vietnamese business spec. Mandatory cross-referencing with BR-* rules before implementation.

Use when the user wants to position their product or define market category. Applies April Dunford's framework, Moore's positioning statement, and Neumeier's Onliness Test. Produces positioning doc, category analysis, and messaging hierarchy. Triggers: positioning strategy, market category, differentiate from competitors. Works standalone; uses /fh:startup-design output if available. Does NOT handle code planning or development. (Codex adapter)

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.

Use when the user wants a quick project readiness check or asks to verify whether the current project is ready to work on. Respond with a one-sentence readiness summary after a brief inspection.

Write or update JSDoc markdown/includes for @duplojs/playwright in jsDoc/, by first detecting the current public export structure, then choosing the right documentation path layout, examples, and source-code {@include ...} annotations.

Use when working in the ackermann_rover_humble repository or changing its Docker, Gazebo, RTAB-Map, Nav2, ros2_control, RealSense, PX4, rover monitoring, Control Center, tmux session, or verification flows. Provides the repo-specific subsystem map, launch/script entrypoints, architecture references, and mandatory validation workflow.

Comprehensive Playwright MCP testing guide for the Strudel live coding app. Use this skill to systematically validate the frontend using structured checklists. Trigger with /playwright-testing.

Manage GitHub issue execution with `gh` in this repository, including scanning open issues, retrieving issue details, creating issue branches, opening draft PRs, and keeping test/push hygiene. Use when a user asks to work an issue, check issue/PR status, or start/continue issue-driven implementation.

Refactor shared server/client TypeScript contracts into a common models directory and eliminate cross-boundary imports (for example client importing server classes). Use when client code depends on server module exports for types or when generated client code needs DTO/view-data/method contracts without bundling server implementation files.

Set or refine source-control policy for repository structure, branch naming, merge strategy, commit hygiene, and secrets-in-git discipline. Use when bootstrapping a repo, tightening PR flow, or documenting branch and release policy.

Enforce the main OpenSpec spec format with overview, scope, interfaces, and requirements.

Manage named field selection specifications that control which columns appear in a view , in what order , and how they are formatted or computed . Each projection captures a JSON serialized ProjectionField [ ] describing key , optional label , visibility , formatter , computed expression , and weight . Projections can be merged so that overlay fields win on key conflict and new fields are appended , and can be evaluated directly against a JSON row array to produce projected rows containing only the specified fields in the specified order

SSR-safe, designer-approved D3 charting for TanStack Start (React). D3 for math, React for rendering, Tailwind v4 tokens, Biome linting.

Plan code refactors by defining goals/non-goals, mapping dependencies, sequencing phases, and specifying verification and rollback checkpoints; triggers: refactor plan/restructure/rename/move modules.

Refresh hackathon submission materials for this repo whenever features, docs, or product positioning change. Use when the user asks to update submission content, rewrite judging criteria answers, regenerate the latest product summary, or prepare current demo/pitch artifacts from the codebase state.

Analyze, trim, and optimize project dependencies

Activate this skill ONLY if the current repo is `watchfolio_backend`, or

Apply ML/AI project delivery guidance for data exploration, feasibility, experimentation, testing, responsible AI, and operating ML systems. Use when the repo includes model training, inference, data science workflows, or ML-specific delivery planning.

Apply when designing or implementing REST API endpoints, routes, or controllers. Covers URL conventions, HTTP methods, status codes, error responses, pagination, versioning, authentication, security, caching, file uploads, health checks, and common API antipatterns. Framework-agnostic HTTP-level patterns. Project conventions always override these defaults.

>

Validate readiness to advance between development phases. Produces a PASS/CONCERNS/FAIL verdict with specific blockers and required artifacts.

Guide for designing and implementing native-feeling, "good Mac citizen" apps: fast, elegant, accessible, and deeply integrated with macOS workflows.

Use when a user brings a new capability, feature request, or enhancement need for greater in vague terms. Interviews conversationally and produces a scoped-need document. Applies Gate 1 (greater-mission alignment), Gate 2 (narrowest scope with API stability), Gate 3 (specialist routing).

This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.

Validate spec-implementation-test alignment and convergence for spec groups. Checks spec completeness, atomic spec coverage, implementation evidence, test evidence, and traceability. Use after implementation and tests are complete.

Deploy locally, run security scans and behavioral tests, check CI/CD, and verify OpenSpec spec compliance