You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.
A process for reviewing self-improvement logs from skills and deciding which lessons should become permanent rules. It distinguishes verified facts from temporary workarounds or one-off incidents.
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback.
A read-only storage analysis tool for macOS and Windows that scans disks and creates an interactive HTML report. The report is a web page showing where storage is being used.
A slash-command shortcut for starting a structured security review of a codebase. It checks for secrets, injection flaws, authentication and cryptography problems, and risky dependencies, then writes a report.
Check and fix common markdown formatting issues after writing or editing any .md file. MUST be invoked whenever you have just written or edited a markdown file (via Write or Edit tools). Checks table formatting, code-block fences, blank lines, ambiguous headers, and other rendering hazards; fixes what it can and flags…
★not rated 9 22d agoA97 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: