Documentation router for Dioxus, the Rust framework for cross-platform (web/desktop/mobile) apps in one codebase. Use whenever the user works with Dioxus — writing `rsx!` markup, components (`#[component]`), signals and hooks (`use_signal`, `use_resource`, `use_memo`, `use_context`, `use_effect`), the router, fullstack / server functions (`#[server]`), assets (the `asset!` macro), or the `dx` CLI (`dx new`, `dx serve`, `dx bundle`, `dx doctor`). Also trigger on Dioxus setup, styling, or deployment questions, a `Cargo.toml` with a `dioxus` dependency, `.rs` files importing `dioxus::prelude::*`, migrating to 0.7, or any "how do I <X> in Dioxus" question. This skill does not bundle the docs — it routes to the smallest fetchable source (per-page markdown, a section `llms.txt`, or docs.rs) and carries an inline Dioxus 0.7 gotchas cheat-sheet.
Create or update the BRAND.md the writer's room writes to — by discovering an existing brand identity in the project (voice docs, published content, site copy), by importing a brand/voice document the user maintains elsewhere, by interviewing the user, or by refreshing the current file. Covers voice, audience, tone-by-context, vocabulary, no-go topics, on/off-voice example pairs, mechanics, and SEO/channels. Invoked on its own or by /writers-room:convene when no BRAND.md is found.
Convene the writer's room — hand off a topic and get back a finished, on-brand piece (article, blog post, or site copy). Runs a short upfront clarification interview, then hands the topic and answers to the showrunner agent, which spawns the room and writes the piece. Checks for a BRAND.md first and helps create one if it's missing. The room does the writing — this skill only interviews and hands off.
Scaffold a new plugin in the toolchest marketplace. Creates plugins/<name>/ with .claude-plugin/plugin.json, README.md, and skills/<skill>/SKILL.md, then patches the root marketplace.json and the root README plugin table. Use when the user asks to add, scaffold, or create a new plugin.
Verify that plugins/, .claude-plugin/marketplace.json, and the root README plugin table are all in sync. Reports any plugin that appears in one or two of those places but not all three. Use when the user asks to check, audit, or verify the marketplace state.
DESIGN.md format specification from Google Labs — a self-contained plain-text representation of a design system that keeps visual identity consistent across design sessions and between AI agents and tools. A DESIGN.md file has two parts: YAML frontmatter holding typed design tokens (colors, typography, spacing, rounded scale, components) plus a markdown body with design rationale and guidance. Tokens follow the Design Token JSON spec with {path.to.token} cross-references and convert cleanly to/from tokens.json, Figma variables, and Tailwind CSS — primary target is Tailwind v4 @theme CSS directives, with legacy v3 tailwind.config.js as fallback. Use when working with DESIGN.md files, defining or editing design tokens, generating a DESIGN.md from scratch, converting tokens to/from tokens.json / Figma / Tailwind v4 @theme / Tailwind v3 config, interpreting another agent's DESIGN.md, or answering questions about the DESIGN.md format.
Use when an agent needs to run sudo or another privileged Linux command from a non-interactive shell, especially after errors like "sudo: a terminal is required", "sudo: no askpass program specified", "sudo: no password was provided", or when sudo prompts cannot appear in the current harness. Helps detect installed askpass helpers, configure SUDO_ASKPASS, use sudo -A safely, avoid authentication lockouts, and ask the user for minimal manual setup when needed.
Decision-support dossier for picking a JS/TS animation or rendering library. Use this skill whenever the user is choosing, comparing, evaluating, or scaffolding a motion / animation / rendering / canvas / WebGL / WebGPU / 3D library for a web project. Covers 30 libraries across two buckets — motion (GSAP, Motion, react-spring, Anime.js, Popmotion, WAAPI, View Transitions, Lenis, Theatre.js, AutoAnimate, use-gesture, animate.css, tailwindcss-animate, tailwindcss-motion, tw-animate-css, react-transition-group) and rendering (three.js, react-three-fiber, react-three-rapier, Babylon.js, PixiJS, @pixi/react, Konva, react-konva, Fabric.js, p5.js, Phaser, Lottie, Rive, Remotion). Trigger when the user asks "what should I use for <animation/canvas/3D/scroll/physics/designer-asset/timeline>", when comparing two of these libraries, when evaluating bundle size / license / maintenance posture, when picking a stack for a creative/agency/interactive site, when building a portfolio with motion, when scaffolding scroll-drive