calebnewtonusc
@calebnewtonusc
Public Skills
life-ops
by calebnewtonusc
"The non-code, non-class half of a week: appointments, renewals, forms, passing commitments, the weekly review, what to drop. Use when planning a week, overloaded, or asking what they're forgetting."
interface
by calebnewtonusc
"Build any interface from a preset: dashboards, tables, forms, settings, wizards, feeds, HUD panels, landing pages. Use to build, lay out or redesign UI, or when it looks generic, ugly or like slop."
graph-engineering
by calebnewtonusc
"Knowledge graphs (ontology, extraction, entity fusion, GraphRAG) and task graphs (fan-out, verifiers, stop rule). Also unasked for serial work that could fan out, dedupe, or same-person matches."
stack-rules
by calebnewtonusc
"This kit's standards for Next.js, React, Supabase and Vercel work: components, API routes, schemas, RLS, deploys, styling, a11y, performance, state, tests. Use when writing, reviewing or auditing them."
reviewing-changes
by calebnewtonusc
"Review code for real problems before it goes anywhere. Use for review this, check for bugs, is this safe to merge, review my PR, before opening a PR, after a feature, or when called sloppy."
debugging
by calebnewtonusc
"Find the root cause of a bug instead of guessing. Use for something broken, an error or stack trace, it used to work, why is this failing, tracing data flow, crash, regression, bisect, debug this."
repo-health
by calebnewtonusc
"Find what has rotted in a project: dead code, unused imports, stale or vulnerable deps, env drift, what's safe to delete. Also for an audit, a messy repo, or which stalled projects to pick back up."
deep-research
by calebnewtonusc
"Research a topic, market, company or claim with checkable sources. Use for research, look into, compare, find out, a decision that needs evidence, or before writing for an outside audience."
grilling
by calebnewtonusc
"Grill the user about a plan, design or idea, one round at a time, until nothing is silently assumed. ONLY when asked: grill me, stress-test my plan, poke holes, what am I missing."
skill-forge
by calebnewtonusc
"Write a new skill, or fix one that isn't being obeyed. Use for a new skill, a skill being ignored, turning a repeated task into something reusable, installing someone's skill, or before any SKILL.md."
shipping
by calebnewtonusc
"Get a change safely out the door. Use for ship it, is this ready, push, deploy, put it live, run or write tests, safe to release, a failed build or deploy, and committing at the end of a session."
reflect
by calebnewtonusc
"Review a finished, stalled or failed session and propose evidence-backed edits to the instructions that steered it. Use for reflect, retro, what went wrong, or improving a skill or CLAUDE.md from a session."
openspec
by calebnewtonusc
"Turn a settled plan into an OpenSpec change (proposal, WHEN/THEN requirements, design, tasks) before code, then build and archive it. Use for spec it, openspec, opsx, or parallel agents on one feature."