Loading...
Loading...
Found 2,066 Skills
Map a topic as an interactive mind map so the user finds what they did not know to ask, then grow it branch by branch on request. Writes a map file and renders it to one HTML page with a script, no hand-written HTML. Use when the user wants to explore, map, or get oriented in a topic, asks "what am I missing", "what don't I know about X", "give me the landscape of X", "map this out", or says "go deeper on" a node of an existing map, and when another skill needs a tree drawn as a page.
Review a change against the repo's own coding standards in a fresh context, fix what is safe to fix in the working tree, and report the rest as a fixed-shape block. Use when a change is about to be committed or a branch is about to become a PR, when the user says "review this", "review my changes", "check this against our standards", or "make it good", and when another skill needs a standards pass before it commits.
Audits an existing developer documentation set's structure - a page-by-page inventory classified against the Diátaxis modes (tutorial, how-to, reference, explanation), mixed-mode and misplaced pages, coverage gaps per product surface, navigation drift against the file tree, a CNCF TechDocs rubric score, and a prioritized remediation queue. Use whenever the user mentions a docs structure or content audit, docs information architecture, Diátaxis, "our documentation is a mess", a docs gap analysis, what docs are missing, where a page should live, or reorganizing a documentation site - even if they only say "our docs are hard to navigate". Not for writing pages. Do NOT use for docs search ranking - use samber/developer-relations-skills@docs-seo.
Intelligently truncate text while maintaining content integrity. Suitable for novel text preprocessing and ensuring text does not exceed specified length limits
ADHD-friendly output formatting. Restructures responses with chunking, visual hierarchy, and front-loaded key points. Modes: clean, flow (default), zen. Use when user says "hyperfocus", "focus mode", "adhd mode", "adhd friendly", or invokes /hyperfocus.
Implement Three.js animation clips, skeletal animation, transitions, scroll timelines, and frame-independent motion.
upfront-design when a request is large enough that product behavior, system architecture, program design, and implementation order should be agreed with the user before code, or when given an existing design to resume or check.
Apple HIG guidance for selection and input controls including pickers, toggles, sliders, steppers, segmented controls, combo boxes, text fields, text views, labels, token fields, virtual keyboards, rating indicators, and gauges. Use this skill when the user says "picker or segmented control," "how should my form look," "what keyboard type should I use," "toggle vs checkbox," or asks about picker design, toggle, switch, slider, stepper, text field, text input, segmented control, combo box, label, token field, virtual keyboard, rating indicator, gauge, form design, input validation, or control state management. Cross-references: hig-components-menus, hig-components-dialogs, hig-components-search.
Prose rules per surface, and the loop that writes, rewrites and reviews prose against them. Use when writing or rewriting docs, code comments, commit messages, tickets, pull request bodies, review comments, skill files or CLAUDE.md, or when reviewing any of them for prose.
Execute deterministic, reproducible historical backtests from a start date, end date, and strategy concept using the Alpaca CLI plus agent-written workspace code. Use when the user wants to backtest a strategy, simulate historical trades, or return trades, diagnostics, and reproducibility artifacts.
Daily temperature high/low bracket and threshold contracts on Kalshi — contract structure, forecast→P(YES) map, settlement rules, cross-venue divergences, and weather-specific pitfalls
Implement and explain stable Rust language semantics with explicit toolchain and MSRV checks — ownership, borrowing, lifetimes, move semantics, traits, generics, associated types, pattern matching, closures, error propagation, and Edition differences. Use as the core Rust language skill when users ask for Rust syntax, compiler-error fixes, ownership/borrowing diagnoses, or version-sensitive stable code; hand std API selection (which collection, which smart pointer, which string type) to rust-stdlib, "how do I write X" pattern questions to rust-by-example, and specialized domains to their dedicated skills.