Loading...
Loading...
Found 10,110 Skills
Design and validate texture-state transitions for Blender animations without ugly whole-image crossfades, texture popping, misregistered morphs, or target-engine-incompatible Python-only swaps. Use when animating between multiple source textures, mascot/logo states, style states, lightmaps, decals, or UI skins.
One-time setup that maps the codebase and gathers user-provided product context to write a root PROJECT.md overview of what the project is, who it serves, how it is structured, and how it runs. Use when the user invokes $setup-project-md, says "setup project md", "create PROJECT.md", or asks for a complete project overview document at the repo root.
Run a complete repository-native, spec-anchored development loop inspired by DeepSeek Harness. Use for feature development, bug fixes, simplification, architecture, process, or testing work that changes behavior, contracts, structure, test strategy, durable formats, or decision rationale; when asked to write, review, continue, implement, reject, supersede, archive, or verify a spec/Agent Note/RFC/ADR; or when code, tests, current-state docs, and decision rationale must converge in one change. Also use for read-only spec-to-code drift checks. Do not create a spec for a purely mechanical local edit that changes none of those things.
Manage Symfony configuration with .env files, parameters, secrets vault, and environment-specific settings
Handle message failures with retry strategies, failure transport, and recovery in Symfony Messenger (Recoverable/Unrecoverable exceptions)
Orchestration mode: the fleet-manager only plans, dispatches, supervises, and reviews — all code changes are delegated to fleet-workers (matching the fleet-manager's harness, model, and effort by default) in visible herdr tabs, each in its own git worktree. Use when the user runs /fleet, says "fleet mode", or asks to orchestrate work across delegated agents. "fleet off" deactivates.
Use this when unexpected failures occur in tasks, when users provide corrections, when requests for missing capabilities are made, or when reusable project patterns are discovered. It is responsible for depositing high-value experiences into `.learnings/` and deciding whether to elevate them to project rules or independent skills.
Professor's review queue — student output waits here for professor approval before going to clients or courts. Only active if "formal review queue" supervision style was chosen at setup; otherwise dormant. Use when the professor wants to see what's waiting for review, approve, edit-then-approve, or return an item.
Append a dated event to a matter's history file and refresh the log row — captures new developments, status changes, risk re-assessments, deadline shifts, and settlement authority changes. Use when the user wants to log an update on a matter, note a development, or record a status change against the portfolio.
Professor's one-time clinic setup — practice areas, jurisdiction, supervision style (formal review queue / configurable flags / lighter-touch), and handbook/rules upload. Writes CLAUDE.md so every other skill and every student who runs /ramp reads from the same clinic context. Use on fresh install, when CLAUDE.md has placeholders, when re-doing setup with --redo, or when re-checking integrations with --check-integrations.
Review open NPRM comment periods, log decisions, track deadlines. Use when an NPRM has a comment window open and you need to surface deadlines, decide whether to file, or record a filing / not-filing / waived decision (--decide CMT-ID).
Triage an inbound demand letter — extract fields, cross-check the portfolio, assess merit, present response options with a recommendation, and hand off to matter-intake or demand-intake if escalation is warranted. Use when the user says "we got a demand letter", "triage this demand", or shares an incoming demand to evaluate.