Skills

Agent skills that change how a decision gets reasoned about, not what gets built.

21 skills · open source on GitHub

npx skills@latest add zaidmukaddam/skills

Each one ends with the cases where it goes wrong, so two of them disagreeing is more useful than one being confident. Read the source on GitHub.

Working rules

no-scripted-editingNever edit tracked files by running a script. No sed, no perl, no one-liners that write files, because each lands a change with no reviewable diff.pr-disciplineDecide whether work is one pull request or a stack before writing it, and keep the description matching the diff as it exists now.commit-disciplineOne line, a conventional type prefix, lowercase after the colon, no body. A body is the rare exception, not the default.

Writing

draft-x-postDraft against what the published For You ranking code rewards. A private share outranks a like by a wide margin, and irritation costs more than everything else earns.

Methods

think-first-principlesRebuild a decision from what must be true rather than from precedent, then name the cheapest test that settles the rest.think-like-a-staff-engineerTreat the decision as the unit of work, not the diff. Design the interface twice, and build a feedback loop before a theory.think-like-a-design-engineerOwn the shipped result rather than the handoff, and verify in the running interface.

Lenses

Each applies the judgment of a particular person to your problem.

Zaid MukaddamThe engineering standards for these codebases, where unverified claims count as defects.zaid Guillermo RauchCount the round trips and delete one, and design the limits in from the start.rauchg Lee RobinsonLet the artifact carry the argument, and name the confounders behind any single number.leerob shadcnShip open code the consumer owns, with great defaults and an escape hatch to zero.shadcn Dax RaadPrice what actually gets consumed rather than the sticker rate.thdxr Dillon MulroyPlan at the call-stack level before any code exists, and design for the person debugging at 2am.dillon-mulroy Theo BrowneStop asking how much code to read and start asking how much to generate.theo dok2001Pick the cheapest compute primitive that fits, and argue from traffic composition rather than benchmarks.dok2001 Malte UblKeep the harness, the agent, and the code it writes in separate security contexts, and pay the durability tax on purpose.cramforce Andrej KarpathyPredict capability from what the supervision signal can verify, and name where your analogy breaks.karpathy Naval RavikantTreat truth as the goal rather than a tactic, and prefer explanations that are hard to vary.naval Garry TanJudge by outcomes rather than inputs, and ask who is funded by the problem continuing.garrytan Sam AltmanCommit to a dated goal with the failure probability stated, and concede errors in the first clause.sama Elon MuskFind the actual limiting factor and solve only that, and gate releases on a condition rather than a date.elonmusk