Index-then-retrieve for large files, specs, or docs instead of pasting them whole into context. Use when a doc/spec/log would cost hundreds+ tokens to read in full, when the user says /sc (index) or /uc (retrieve), or asks to "save context on this doc" /…
StarchyBomb/superlazy
SkillsMP has collected 13 skills from StarchyBomb/superlazy. Open a skill to review its source and details.
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 13
- GitHub stars
- 2
- GitHub forks
- 0
Skills in this repository
Showing 13 of 13 collected skills.
Silent root-cause debugging. Use on any bug, test failure, build failure, or unexpected behavior, BEFORE proposing or writing any fix.
Build MCP servers with minimal tokens. Use when creating or modifying an MCP (Model Context Protocol) server integrating any external API or service, in TypeScript or Python.
Silent planning and execution for multi-step tasks. Use when a task spans several files/steps, or when a written plan exists and must be executed.
One-shot signature map of a codebase (function/class names + line numbers, no bodies) instead of a Glob/Grep/Read tour. Use when starting work in an unfamiliar or large codebase, before exploring with multiple directory-wide searches, or when the user asks to…
Silent code review — giving and receiving. Use after completing a task/feature before calling it done, and whenever review feedback arrives, before implementing any suggestion.
Create or improve skills with minimal tokens. Use when the user wants a new skill, wants to edit/optimize an existing skill, or wants a workflow captured as a skill.
Core silent coding mode. Use before writing or modifying ANY code. Minimal code, minimal output, full quality. Always load this first; every other superlazy-* skill assumes this contract.
Silent subagent-driven plan execution. Use when executing an implementation plan with independent tasks and subagent support is available.
Silent test-driven development. Use when implementing any feature or bugfix in a project that has a test setup, before writing implementation code.
Evidence before any completion claim. Use immediately before saying done/fixed/passing, before any ✅, and before committing or creating a PR.
Silent isolated workspace setup. Use when starting feature work that needs isolation from the current workspace, or before executing an implementation plan.
Maximum-savings loadout — stacks output economy, input/context economy, and tool-output economy into one skill. Use when the goal is squeezing token/credit cost as hard as possible while keeping quality unchanged or better, or when the user says "ultralazy",…