Loading...
Loading...
Found 93 Skills
Optional, modular cleanups and style improvements to apply on new mo:core projects (or after mo:core migration). Covers import ordering, unused import cleanup, and single‑expression return removal, with detection checks and automation recipes.
Stop AI coding agents from shipping sloppy code — over-abstraction, drive-by refactors, obvious comments, extra files, unrequested deps, giant unreadable files, or fishing outside the workspace for “inspiration”. Use when writing or editing code, implementing features, fixing bugs, splitting or organizing files, or when the user mentions slop, cleanup, keep it simple, minimal diff, file too big, hard to navigate, or stay in the repo.
Use when an app has to move onto a design system that already exists, such as "migrate the app to our design system", "move every screen onto the new components", a rollout, or an adoption audit. Not for making the system or for swapping raw values for tokens, which are build-design-system.
Apply systematic code refactoring with small steps, clear boundaries, and proven techniques. Use when improving existing code, reducing technical debt, cleaning up legacy code, or when user mentions refactoring, code cleanup, or code improvement.
Use this when the user asks to refactor, clean up, optimize, or improve code quality.
Use when the operator explicitly asks to iterate on a bounded objective until it is satisfied, such as a refactor, cleanup, documentation rewrite, non-ticket change, or ticket follow-up. Trigger on goal-loop, loop until done, iterate until clean, max rounds, or similar language. Do not self-trigger for ordinary implementation. Never commits.
Author and optionally direct-launch a two-node loop-graph run whose North Star is code convergence — delete unused code, merge duplicates, reuse, slim. Use when the user invokes /loop-converge, or asks to loop on dead code, duplication, unused exports, DRY cleanup, or merging twin implementations. Starts the owner interview (scope / authority / launch) immediately; supervisor is required. Not for adding features or a one-shot tidy. Do not execute or resume existing runtime node files from this authoring skill.
Optimize your SaaS app across four dimensions - Speed (page load, API response), Code (unused files, dead code), Database (orphaned data, schema hygiene), and Dependencies (package bloat, bundle size). Use when app feels slow, codebase feels bloated, or after significant development work accumulates. Each path follows AUDIT → CLEAN → PREVENT workflow.
Clean up code, remove dead code, and optimize project structure. Use when user wants to clean codebase, remove unused code, or optimize imports.
Aggressively clean up a codebase by removing AI slop, dead code, weak types, defensive over-engineering, duplication, and legacy cruft. Orchestrates 8 specialized subagents in parallel to deduplicate code, consolidate types, kill unused code, untangle circular dependencies, strengthen weak types, remove unnecessary try/catch, delete deprecated/legacy paths, and strip unhelpful comments. Use when the user asks to 'clean up the codebase', 'remove slop', 'improve code quality', 'remove dead code', 'kill AI slop', 'tighten types', 'remove legacy code', 'deduplicate code', 'DRY this up', 'untangle dependencies', or wants a thorough code quality pass. Also use when the user mentions code smells, technical debt cleanup, or refactoring for clarity — even if they don't use the word 'slop'.
React/Next.js/TypeScript 코드를 리팩토링하는 스킬. 컴포넌트 분리, 커스텀 훅 추출, 디자인 패턴 적용, 코드 정리 등. "리팩토링", "refactor", "코드 개선", "분리해줘", "정리해줘" 등의 요청 시 사용.
Remove redundant comments within the requested scope while preserving useful constraints and working code.