ryanwaits

Receives CSS and HTML changes made in CSS Studio via MCP and applies them to source code.

Analyze the Secondlayer codebase and identify exactly ONE high-leverage, low-risk quality-of-life improvement. Use when: user runs "/quality-of-life", asks for "a quick win", "something to improve", "code quality check", or "what should I clean up next".

Run a production smoke sweep against secondlayer prod — container health, husk canaries, decoder lags, op queue budgets, public subgraph reads, balance conservation, known-bug regression probes. Use when the user runs "/prod-smoke", asks to "smoke test prod", "check prod health", "is everything running smoothly", or "verify the subgraphs".

Use Secondlayer to build on the Stacks blockchain — index on-chain activity into typed Postgres tables (subgraphs), stream raw and decoded events (Streams + Index), deliver row-level webhooks (subscriptions), and call Clarity contracts from a viem-style TypeScript SDK. Invoke this skill whenever the user mentions Secondlayer, `sl`, the `@secondlayer/*` packages, Stacks indexing, sBTC, BNS, PoX/stacking, Clarity contract reads/calls, post-conditions, webhook subscriptions on chain events, or asks how to query, watch, or react to anything happening on the Stacks chain — even if they don't name Secondlayer explicitly.

Analyze Stacks ecosystem signals and map them to high-value product, marketing, security, and onboarding opportunities buildable with secondlayer tools (Index, Subgraphs, Streams, CLI, SDK, @secondlayer/stacks, MCP). Use when the user pastes a Stacks Discord "this week in Stacks" announcement digest, or points at any single source — a Hiro GitHub issue, a forum/X thread, a dev complaint about the Hiro API or another service, a protocol launch, or a historical hack/exploit writeup — and wants it parsed, its links fetched and analyzed, and turned into ranked opportunities for product validation, developer onboarding, ecosystem/dev-need solutions, security tooling, or brand content. Triggers on "scout the announcements", "stacks opportunities", "what can we build from this", "analyze this for product opportunities", "ecosystem scan".

Create a changelog, launch, announcement, or milestone video for ANY repo / package / release using the cadence CLI. Use whenever someone wants a video, reel, teaser, or animated showcase for a software feature, release, PR, changeset, SDK/CLI update, or milestone — phrasings like "make a changelog video for <repo>", "announcement video for the v2 release", "showcase the new <feature>", "a reel for our latest npm release", "render a 9:16 of <project>'s changelog", "milestone video — 1M downloads". Point it at a local repo path or a GitHub repo. It reads the project, writes a small data file, and renders an MP4. Trigger even when the user doesn't say "Remotion", "beats", or "render".

Documentation drift detection and sync for any API surface — TypeScript packages, OpenAPI/REST specs, Clarity contracts. Use when checking doc coverage, validating docs against an API, detecting drift, or fixing outdated documentation. Triggers on "doc coverage", "validate docs", "drift", "docs out of sync", "are my docs accurate", "update docs to match API".

Bootstrap and maintain a drift docs map — the committed page→type artifact for docs key-coverage mode (drift scan --docs-map). Use when setting up key-coverage for a docs site, mapping docs pages to spec types, classifying ambiguous option keys, or when asked to "set up docs coverage", "map docs pages to types", "bootstrap the docs map". The agent proposes; the human commits; CI runs the map deterministically.

Document undocumented API surface found by drift — generate signature-accurate JSDoc/doc stubs for exports that lack documentation. Use after `drift scan`/`drift coverage` reports undocumented exports, or when asked to "improve doc coverage", "document the API", "add missing docs". Produces stubs with TODO prose markers, never invented descriptions.

Fix documentation drift reported by drift scan/lint — stale signatures, wrong parameter names/types, references to removed or renamed exports, prose drift in markdown. Use after `drift scan` or `drift lint` reports issues, or when asked to "fix drift", "fix the docs", "sync docs to the API". Edits docs to match the API, never the reverse.

Verify an entire docs site/directory against the real API surface using drift as the truth oracle. Use when asked to audit docs accuracy, check hand-written guides against an OpenAPI spec or TypeScript package, find stale/phantom documentation, or produce a docs-drift report. Triggers on "verify the docs", "audit docs against the API", "are these guides accurate", "docs drift report".

Analyze the Drift codebase and identify exactly ONE high-leverage, low-risk quality-of-life improvement. Use when: user runs "/quality-of-life", asks for "a quick win", "something to improve", "code quality check", or "what should I clean up next".

Generate framework-ready API reference docs (Fumadocs, Docusaurus, or plain Markdown) for a TypeScript package using OpenPkg. Detects the target docs framework, extracts an OpenPkg spec, writes page-per-export MDX/MD with navigation (meta.json / sidebars) and optional search indexes, then verifies output. Use when the user asks to "generate API docs", "generate docs from my TypeScript exports", "add an API reference to my docs site", "scaffold fumadocs/docusaurus API pages", "create reference docs with openpkg", or runs "/generate-docs". Optional args: entry file, framework (fumadocs|docusaurus|markdown), output dir.

Analyze the OpenPKG codebase and identify exactly ONE high-leverage, low-risk quality-of-life improvement. Use when: user runs "/quality-of-life", asks for "a quick win", "something to improve", "code quality check", or "what should I clean up next".