Use when a development board, SBC, MCU module, or board-level enclosure constraint must be resolved for hardware or CAD design.

Allows to interact with web pages by performing actions such as clicking buttons, filling out forms, and navigating links. It works by remote controlling Google Chrome or Chromium browsers using the Chrome DevTools Protocol (CDP). When Claude needs to browse the web, it can use this skill to do so.

Project-specific patterns for the Saleor Paper storefront built with Next.js 16, TypeScript, and Tailwind CSS. Use when working with product pages, checkout flow, caching, variant selection, filtering, SEO, or UI components. For universal Saleor API patterns, see the saleor-storefront dependency.

Complete reference for ecluse — ephemeral local environments for coding agents, any stack. Use this skill whenever ecluse is mentioned, a .ecluse.toml file is present in the repo, the user asks about worktree isolation, parallel dev environments, or port/database conflicts between branches. When a .ecluse.toml file is present in the repo, loading this skill before starting work is strongly recommended so you understand the isolation model and avoid port conflicts.

Web search and content extraction via Brave Search API. Use for searching documentation, facts, or any web content. Lightweight, no browser required.

Create or update the feature specification from a natural language feature description.

Execute the implementation plan by processing and executing all tasks defined in tasks.md

Validate current branch follows feature branch naming conventions

Create a feature branch with sequential or timestamp numbering

Disabled — commits are performed manually by the user, never by Spec Kit

Create a feature branch with sequential or timestamp numbering

Disabled — commits are performed manually by the user, never by Spec Kit

Generates requirements documentation (user stories, acceptance criteria, out-of-scope) for a feature in an AI-native MVP project. Invoke before any implementation of a new feature begins — a feature without requirements documentation should not be built. If the developer mentions wanting to add or implement something new, trigger this skill before any code is written.

Scans all authoritative documents (constitution, context, glossary, requirements) and all derivative documents (architecture decisions, architecture overview, MVP architecture spec, vision, implementation heuristics) to add missing citations, replace stale duplicate facts with pointers, and correct contradictions. Use this skill whenever a document has been written or revised in the current phase, whenever you suspect a constraint in one document is not reflected in another, or whenever an agent reading multiple documents has flagged a conflict. Safe to re-run — applying it a second time produces the same result as the first.

Enriches each user story's acceptance criteria with a "Relevant constraints" line pointing to the specific architecture decisions, implementation heuristics, design principles, and UI kit that apply to that story. Use this skill after any phase that introduces new constraints — after architecture decisions are written (Phase 3), after the UI kit is approved (Phase 4), and after implementation heuristics and design principles are established (Phase 5). Also invoke whenever a Phase 6 agent reads the acceptance criteria and lacks a clear picture of which constraints govern a particular story. Safe to re-run at any phase — each invocation only adds constraints not already listed; nothing is ever removed from an existing entry.

Use when building AI-powered applications with the Dedalus SDK (dedalus_labs)—covers orchestrating agents with DedalusRunner, defining local tools, using structured outputs with Pydantic/Zod schemas, streaming responses, routing via handoffs across models, connecting to MCP servers, and working across providers (OpenAI, Anthropic, Google, xAI, DeepSeek, Mistral).

Use when developers need to build MCP (Model Context Protocol) servers with dedalus_mcp—covers creating tools via @tool, exposing resources via @resource, defining user prompts via @prompt, using context utilities (progress, info, cancellation), and registering components modularly with collect().

WordPress PHP plugin development using Test-Driven Development (TDD) and functional programming principles. Use this skill when developing, testing, or maintaining WordPress plugins with focus on PSR-12 compliance, Composer integration, automated testing with PHPUnit, coding standards enforcement with phpcs/phpcbf, and git version control. Triggers include requests to create WordPress plugins, write WordPress PHP code, set up testing infrastructure, implement TDD workflows, or apply functional programming patterns in WordPress.

Use this skill to initialize and integrate the YouTube Playables JavaScript SDK into an HTML5 game. Covers SDK bootstrapping, game lifecycle signaling, persistent save data management, interstitial and rewarded ads, leaderboard score submission, player language detection, and audio/pause lifecycle hooks. Use when the user asks about YouTube Playables, building or embedding games for YouTube, the YT game SDK, YT Playables integration, or making an interactive playable game on YouTube.

Integrates the Yandex Games JavaScript SDK (YaGames) into JavaScript games. Initializes the SDK and lifecycle hooks, manages player authentication and authorization, handles per-player cloud storage, controls ad placements (interstitial, rewarded video, sticky banner), implements in-app purchases and leaderboards, retrieves remote config flags, and supports social features such as review prompts and home-screen shortcuts. Use when the user mentions Yandex Games, YaGames, yandex sdk, deploying a game to the Yandex.Games platform, or integrating features like ads, leaderboards, in-app purchases, or player authentication into a Yandex-hosted JavaScript game.