Total 57,829 skills
Showing 12 of 57829 skills
Use when writing, moving, reviewing, or auditing documentation in a repository — choosing hierarchy and detail, separating tutorials from references, checking tutorial progression, trimming doc slop, responding to a documentation-budget gate failure, or requests like "improve the docs", "audit the docs", "govern the docs", "standardize the documentation of a repository", "where should this be documented", or "this doc is too long".
Ask which skill or flow fits your situation. A router over the docs/Agent-Note maintenance flow, the documentation governance run, the prose-and-docs tool layer, and the standalone git and game skills in this pack.
Turn a proven or user-requested workflow into a reusable skill. Use when the user asks to preserve, formalize, or reuse a repeated process.
Configure a repository for the docs-maintenance skills — scaffold the Agent Note decision tree, the bilingual pairing convention, the documentation standard, the session-discipline lines, the documentation budget gate, the change-scope tool, and the git hooks, and record where they live. Run once before first use of the maintenance flow.
Diagnose React runtime performance with React Doctor traces, live render outlines, Long Animation Frames, interaction timing, and component render evidence. Use when invoked as `/performance` for a slow interaction, unexpected re-renders, or a measured before-and-after comparison.
Record browser or Web UI interaction demos as optimized GIFs using the available browser tooling, state-based frame capture, and deterministic encoding, then publish to a dedicated assets branch when the task includes attaching the GIF to a pull request. Use when asked to make, record, or generate a GIF that demonstrates a browser workflow, and for every pull request that changes product-user-visible GUI behavior, which MUST include a GIF recorded from the pull request's real server and data flow.
Use before pushing, force-pushing, or marking a branch ready for review — and after any history rewrite — to select the smallest checks that cover the outgoing diff instead of reflexively running everything.
Generate targeted test scenarios for a LiveKit voice or chat agent and run them as simulations — locally, from the agent's own code plus what the user wants stress-tested. Use whenever the user wants to "test my agent", "what should I test", "create/generate simulation scenarios", "make a sim test suite", "use lk agent simulate", "stress-test the X flow", "set up scenarios for my agent", or wants to probe edge cases / refusals / regressions before shipping. Generates scenarios on the user's machine (their code is never uploaded) and lets the user deeply steer what gets tested. Trigger even without the word "simulation" when the user clearly wants to decide what to test and verify how their agent behaves across realistic conversations. Not for building a new agent from scratch (use the livekit-agents skill), load-testing, or ordinary unit tests.
Use when writing, reviewing, restoring, trimming, or auditing prose — deciding where documentation or comments are required across Markdown, skill frontmatter and bodies, JSDoc, code and test comments, prompts, descriptions, diagnostics, and CLI or UI strings, and preserving complete contracts while removing reasoning transcripts and repetition.
TypeScript-for-Roblox (roblox-ts) development workflow — compile TypeScript to Luau with rbxtsc, work with @rbxts/types, and apply TypeScript-to-Luau interop idioms in Rojo-synced Roblox projects. Use when working on a Roblox project that uses roblox-ts, rbxtsc, @rbxts packages, or a tsconfig targeting roblox-ts, or when the user asks about TypeScript for Roblox.
Compare screenshots to judge which image is less wrong, not to match a baseline. Use when a UI, game, document, render, chart, or generated asset needs objective visual telemetry, side-by-side inspection, crop/zoom review, or a fresh second opinion before accepting or rejecting a visual change.
Use when the user asks to "remember project context", review saved findings, initialize runtime memory, archive stale work, reconcile notes, or erase a subject; manages authorized HOT/WARM/COLD working memory across all disciplines while preserving registry event ownership and privacy controls. Not for changing canonical registry facts - route those through the owning registry. 项目记忆/跨会话