All authors
Claude Skills by logicleap-labs
github.com/logicleap-labs11 skills0 installs0 views
- Accessibility GateUse before declaring a UI change done, fixed, working, ready, or shipped. Forces a real accessibility pass across keyboard flow, focus visibility, accessible names, contrast, reduced motion, and the platform's native semantics.Votes: 0GitHub stars: 2
- Migration SafetyMANDATORY before any destructive database or schema work — DROP TABLE/COLUMN, TRUNCATE, DELETE or UPDATE across rows, irreversible ALTERs, data backfills, schema migrations. Forces the method: state the exact target → dry-run to count what's affected → write the rollback → only then execute. Triggers on \"drop the table\", \"delete the old rows\", \"clean up the data\", \"truncate\", \"remove the column\", \"write a migration\", \"alter the schema\", \"backfill\", any raw SQL against a real d...Votes: 0GitHub stars: 2
- No DebugMANDATORY before declaring code "done", "ready", or ending a turn after writing or debugging a function/handler/module. Use whenever you added a debug print while working something out — console.log, debugger, pdb.set_trace(), breakpoint(), binding.pry, byebug, dd()/var_dump()/print_r(), dbg!(), a "print('here')" or "console.log('DEBUG', x)". Forces you to strip the debug noise before shipping, and to reach for a real logger when you actually need persistent logs. Triggers on "let me add a lo...Votes: 0GitHub stars: 2
- No Silent AssumptionsMANDATORY before declaring code "done", "ready", or ending a turn after working with anything you couldn't fully verify — an environment you didn't inspect, a data shape you inferred, an API whose behavior you didn't test, an edge case you decided not to handle. Forces you to track every material guess while working and surface them in a short "Assumptions:" block before claiming done. Triggers on "I'll assume", "assuming the API returns", "probably fine", "should work", "not sure if", "guess...Votes: 0GitHub stars: 2
- No SlopMANDATORY before declaring prose "done" or ending a turn after writing a README, doc, blog post, comment, or any .md/.mdx/.txt/.rst. Use whenever you write or edit prose and are tempted to reach for an AI-tell cliché — "delve into", "it's worth noting that", "a testament to", "navigate the complexities", "rich tapestry", "in today's fast-paced world", "unlock the full potential", "seamlessly integrate", "elevate your", or a pile-up of decorative em-dashes. Forces you to cut the tell and say t...Votes: 0GitHub stars: 2
- No StubMANDATORY before declaring code \"done\", \"ready\", or ending a turn after writing a function/handler/module. Use whenever you write or edit code and are tempted to leave a placeholder — TODO/FIXME, NotImplementedError, an empty `...` body, \"your code here\", \"implementation goes here\", a stub return, or a half-built path. Forces you to finish the job: real, working implementation, or an explicit intentional-stub declaration. Triggers on \"I'll add this later\", \"placeholder for now\", \...Votes: 0GitHub stars: 2
- No SwallowMANDATORY before declaring code \"done\", \"ready\", or ending a turn after writing or editing anything with a try/catch, except, or error path. Use whenever you wrapped something in a handler and left the body empty — `except: pass`, `except Exception: pass`, `catch (e) {}`, `catch {}`, `.catch(() => {})`, `.catch(() => null)`, an empty `if err != nil {}` in Go. Forces you to handle the error, log it, re-raise it, or return a real fallback instead of silently swallowing it. Triggers on \"jus...Votes: 0GitHub stars: 2
- Scope GuardUse at the START of any focused task — a bug fix, one feature, a single file's refactor — and ALWAYS when more than one agent shares a working tree. Declare which files the task is allowed to touch so edits outside that set are blocked. Triggers on "only change X", "just fix the bug in", "don't touch anything else", "stay in your lane", "scoped change", "while you're in there" (the thing to prevent), shared-tree / multi-agent work, and any task where creep is the risk.Votes: 0GitHub stars: 2
- Secret GuardUse whenever you are about to put a credential, API key, token, or password into code — or whenever a secret already appears in a file you're editing. Triggers on \"add the API key\", \"paste the token\", \"hardcode the secret\", \"set the password\", \"AWS/Stripe/OpenAI/GitHub key\", \"connect to <service>\", \"use this credential\", config/setup work that wires up a third-party service, and any moment a real secret value is in hand. The rule: secrets go in the environment, never in source.Votes: 0GitHub stars: 2
- Verify Before DoneMANDATORY before declaring ANY code change "done", "fixed", "working", "ready", "shipped", or before ending a turn after editing source. Use whenever you modified code, config, scripts, SQL, infra, or tests and are about to say it works. Forces you to RUN something that exercises the change (test, build, lint, typecheck, smoke script, reproducible command) and record the evidence. Triggers on "done", "fixed", "working", "all tests pass", "build succeeded", "should work now", "ready to merge".Votes: 0GitHub stars: 2
- Visual Self ReviewMANDATORY acceptance gate before declaring ANY visual or UI work "done", "good", "working", or before screenshotting an interface and ending the task. Use whenever you build, redesign, restyle, or fix a user-facing screen in ANY stack — Xcode/SwiftUI/UIKit apps, iOS/macOS, web (Next.js/React/HTML), Electron, Flutter, generated design mockups — and whenever you are asked to "review the screenshot", "check what you built", "is this good", "spot the issues", or "look at this design". Forces a st...Votes: 0GitHub stars: 2