nateslabach
- 19 skills
- 0 followers
- 6 hours ago last updated
- ▌ Adhd · nateslabachFormats output for ADHD-friendly action — lead with the next step, number tasks, restate state, cut fluff. Use when named (adhd), when the user mentions ADHD or focus/executive-function constraints, or when they ask for steps they can execute immediately.
- ▌ Prisma · nateslabachTypeScript and Prisma ORM best practices for schema design, type-safe queries, migrations, and error handling. Use when writing Prisma schemas, building database access layers, or debugging query performance in TypeScript projects.
- ▌ Depth UI · nateslabachApplies depth-driven layered color and shadow principles to elevate average UI into polished, readable interfaces for both light and dark themes. Use when improving or reviewing UI components, setting up a design token system, applying consistent depth and shadow to an interface, or making a flat or inconsistent UI feel more refined without a full redesign.
- ▌ Pushback · nateslabachStress-tests ideas by surfacing assumptions, counterarguments, and confidence gaps. Use when evaluating claims, proposals, plans, or decisions that need rigorous intellectual scrutiny.
- ▌ Subagent · nateslabachGround rules for an effective subagent in a loop, workflow, or graph run. Stay in scope, escalate when stuck, return structured results. Use when acting as a subagent, writing subagent prompts, or reviewing delegated agent behavior.
- ▌ CSS Reset · nateslabachApplies a modern CSS reset covering box-sizing, margin removal, text rendering, media defaults, and root stacking context. Use when starting a new web project, creating a global stylesheet, or when the codebase lacks sensible CSS defaults.
- ▌ Just Stop · nateslabachStops "just one more" small tweaks that add scope without changing the outcome. Use when named (just-stop), or when about to implement extra polish, cleanup, or drive-by fixes beyond the stated goal.
- ▌ Mini Loop · nateslabachAutonomous build-verify-fix loop that runs until an explicit Definition of Done passes. Use when named (mini-loop) or when the user says exactly "run a loop".
- ▌ Asd Ste100 · nateslabachWrites in ASD-STE100 simplified technical English — short sentences, plain words, active voice. Use when the user wants terse technical prose, names this skill, or asks for STE100.
- ▌ Vibe Audit · nateslabachRuns a comprehensive 20-point code quality audit on a "vibe-coded" codebase that was shipped fast and now needs hardening. Use this skill whenever the user mentions vibe coding, vibe audit, code audit, code review, code cleanup, hardening a prototype, productionizing a codebase, technical debt cleanup, or asks Claude to "audit my code", "review my codebase", "clean up my project", or check a freshly-shipped project for common quality issues. Also use when a user shares a repo and asks what's wrong with it or how to make it production-ready.
- ▌ Code Review · nateslabachConducts a structured 3-phase code review — understanding intent, cataloguing issues by severity, and stress-testing with adversarial questions. Use when reviewing a code diff, pull request, or snippet for correctness, edge cases, security issues, and merge readiness.
- ▌ Model Bench · nateslabach bundleRun a 3-leg evaluation against a newly released LLM. Leg 1 is trap questions with deterministic answers, leg 2 is an agentic orchestration task with a planted failure, leg 3 is a brownfield feature build in a real repo. Use when the user wants to vibe-check, test, evaluate, or compare a new frontier model, or mentions model-bench, model vibe check, or launch-day protocol.
- ▌ Brutal Truth · nateslabachDisables the AI's default hedging, diplomatic softening, and social-nicety layers to deliver cold, unfiltered, consequentialist analysis on any topic. Use when the user wants the AI's actual assessment without padding, regardless of how harsh or uncomfortable the honest answer is.
- ▌ Create Issue · nateslabachCraft a single, high-quality GitHub issue from a developer's description of a bug, unexpected behavior, or desired enhancement. Walks through reproduction, codebase exploration, and structured drafting so the issue is actionable on arrival. Use when user wants to file an issue, report a bug, request a feature, or document a problem they've encountered.
- ▌ Human Writing · nateslabachStrips AI fingerprints from written text by enforcing banned vocabulary, forbidden sentence structures, and authentic prose patterns. Use when writing articles, documentation, social content, emails, or any text that should read as human-authored rather than AI-generated.
- ▌ Token Maxxing · nateslabachGenerates as many digits of pi as possible and writes them into files inside a tokenMaxxing/ folder. Use when the user asks to token-maxx, fill a file with pi digits, test agent output throughput, or generate N pi files sequentially or in parallel.
- ▌ React Component · nateslabachGenerates complete, production-ready React/TypeScript components using Tailwind CSS. Use when building UI components in a React or Next.js project that requires TypeScript, Tailwind styling, and accessible interactions.
- ▌ Shut Up And Drive · nateslabachCuts fluff and leads with what matters. Applies Parkinson's Law, Pareto, and Goodhart's Law so every word earns its place. Use when the user wants terse output, names this skill, or signals that responses are too padded.
- ▌ Engineering Judgment · nateslabachApplies Chesterton's Fence, Occam's Razor, the Peter Principle, and Dunning-Kruger to technical decisions. Use before refactoring, architectural changes, or any task where changing existing behavior carries risk or requires judgment about what the user actually needs.