slfg
Swarm-enabled LFG. Run these steps in order, parallelizing where indicated. Do not stop between steps — complete every step through to the end.
Sequential Phase
- Optional: If the
ralph-loopskill is available, run/ralph-loop:ralph-loop "finish all slash commands" --completion-promise "DONE". If not available or it fails, skip and continue to step 2 immediately. /ce:plan $ARGUMENTS/ce:work— Use swarm mode: Make a Task list and launch an army of agent swarm subagents to build the plan
Parallel Phase
After work completes, launch steps 4 and 5 as parallel swarm agents (both only need code to be written):
/ce:review mode:report-only— spawn as background Task agent/compound-engineering:test-browser— spawn as background Task agent
Wait for both to complete before continuing.
Autofix Phase
More from udecode/plate
code-simplicity-reviewer
Final review pass to ensure code is as simple and minimal as possible. Use after implementation is complete to identify YAGNI violations and simplification opportunities.
60vercel-react-best-practices
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 improvements.
46grill-me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
37frontend-design
Build web interfaces with genuine design quality, not AI slop. Use for any frontend work - landing pages, web apps, dashboards, admin panels, components, interactive experiences. Activates for both greenfield builds and modifications to existing applications. Detects existing design systems and respects them. Covers composition, typography, color, motion, and copy. Verifies results via screenshots before declaring done.
34git-history-analyzer
Performs archaeological analysis of git history to trace code evolution, identify contributors, and understand why code patterns exist. Use when you need historical context for code changes.
33best-practices-researcher
Researches and synthesizes external best practices, documentation, and examples for any technology or framework. Use when you need industry standards, community conventions, or implementation guidance.
33