React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance…
How the Furl context-compression plugin works in Claude Code and Codex — the furlcompress / furlretrieve / furlstats / furlpurge / furlsearch / furllist MCP tools, the > retrieval flow, and Claude Code's optional automatic hooks. Use when the user asks what Furl is doing, how to compress or retrieve content, why…
Spec-Build-Test loop — the user defines a spec, then three agents iterate (Builder implements, Tester validates, Supervisor monitors for freezes) until the result matches. Works for any digital function — UI, APIs, CLI tools, conversational AI, data pipelines, and more.
A read-only audit checklist for Hermit and Claude Code setups, covering how they are structured, used, checked, and improved, including token use and model selection.
Inspect, create, relate, update, audit, standardize, and organize Plane work items with the Plane Workflow MCP tools. Use for project briefings, filtered work queries, dependencies, task lifecycles, modules, and backlog improvements.
How to grade a Daedalus run (or pasted agent transcript), root-cause the failure, and ship the fix to Daedalus CORE as a stacked PR — without modifying the prompt-vault sandbox (read-only grading). Covers recurring bug archetypes (Unicode punctuation patch mismatch, syntax-vs-type mislabel, emoji box misalignment…
Plan focused tests with CodeMeridian by finding relevant test shields, coverage gaps, impacted behavior, and the smallest useful test set before implementation.
Use when a Looper-managed GitHub repo needs scheduled pre-merge QA — a PR carries the looper:qa label, the spec stage reaches looper:spec-ready, or the Looper reviewer loop requests an independent second pass. Runs the full QA cycle (Looper state probe → PR checkout → ffs code review → language-specific test suite →…
Complete guide to the shared-agents shell CLI (sa). Use when the user asks how to run sa, sa help, install, sync, review, pending, unapprove, check, uninstall, status, or any shared-agents terminal command. Also use when explaining setup, wizard, or troubleshooting the CLI after sa install.
★not rated 4 3mo agoA✓ AI review69 tokens
originalMIT
Write Markdown files that pass markdownlint with zero warnings. Use when creating or editing .md, .mdc, or .mdx files, writing documentation, updating README files, or creating Cursor rules and skills.
Add persistent, interactive task plan management to your agent. Wingman tracks plans and tasks across a long conversation — Claude creates plans, ticks tasks after completing work, and a live panel renders inline in the chat. Install the MCP server first, then use these tools to manage plans and tasks throughout any…
Persistent memory and task coordination for AI coding sessions. Creates a .fireteam/ folder with mission context, task state, checkpoints, and handoff notes that survive session restarts, context limits, and crashes. Use this skill whenever the user wants to set up a fireteam, continue a fireteam, resume after a…
Minimal implementation ladder before writing code. Apply before each edit; question over-scope during planning. Complements caveman (prose). Inspired by DietrichGebert/ponytail (MIT).
Audit a codebase for handcrafted code that duplicates functionality already available in the project's dependencies. Reads package.json, launches parallel exploration agents, verifies replacement feasibility, and produces a structured refactor plan. Audit only -- does not execute changes.
Use when the user asks for an extensive, maximum-quality, whole-codebase review or audit and wants a consolidated findings report (read-only, default). Add --autopilot to run a fully autonomous performance pipeline: read Supabase signals, deep-dive via dynamic workflows, refine fixes with a headless Codex pass, apply…
★not rated 4 2d agoA0 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: