Zaid Mukaddam

Skills

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

20 skills · open source on GitHub

npx skills 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. Every stage below shows both halves, quoted from the source on GitHub.

Lenses

The same desk, a different person at it. Pick one and watch the reasoning change.

Zaid Mukaddam · The engineering standards for these codebases, where unverified claims count as defects.

/think-like-zaid review this pull request against the quality bar
  1. Match a named reference product
  2. Go to the primary source
  3. Verify in the running thing
  4. Delete before you complicate
  5. Fix the mechanism, not the symptom
  6. Cover every item, and name what you would skip
  7. Prefer current versions, with a stability check

Quoted from the skill

Working rules

/no-scripted-editing

Never 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.

/no-scripted-editing rename userId to accountId across the app
  1. The rule
  2. What counts as scripted editing
  3. Three specific failures this prevents
  4. What is still fine
  5. When a script genuinely is the right tool
  6. What to do instead

Quoted from the skill

/pr-discipline

Decide whether work is one pull request or a stack before writing it, and keep the description matching the diff as it exists now.

/pr-discipline split this branch into reviewable pull requests
  1. The shape of a mergeable change
  2. The description matches the diff, not the intent
  3. Shape the commits, not just the final diff
  4. Every review comment gets a disposition
  5. Ready means re-checked, not remembered
  6. Keep a stack honest
  7. When one PR is the right call

Quoted from the skill

/commit-discipline

One line, a conventional type prefix, lowercase after the colon, no body. A body is the rare exception, not the default.

/commit-discipline write the commit message for these changes
  1. The default shape
  2. When there is no prefix
  3. Name everything the commit does
  4. The body is the exception
  5. Match the weight of the message to the weight of the change
  6. Never attribute a commit to a tool

Quoted from the skill

Methods

/think-first-principles

Rebuild a decision from what must be true rather than from precedent, then name the cheapest test that settles the rest.

/think-first-principles do we need a vector database for this?
  1. Recover the real objective
  2. Label the assumptions, keep what survives
  3. Compute the floor
  4. Rebuild, deleting first
  5. Attack it, then give the cheapest test

Quoted from the skill

/think-like-a-staff-engineer

Treat 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-staff-engineer review this migration plan
  1. Name complexity as the thing you are minimizing
  2. Design the interface twice before building once
  3. Make the module deep, and put the seam where something varies
  4. Build a feedback loop before building a theory
  5. State claims so they can come back false
  6. Cut a tracer bullet, then widen
  7. Prefer deleting complexity to rearranging it
  8. Unify knowledge, not text
  9. Choose the option that stays easiest to change
  10. Sharpen the words before sharpening the code
  11. Plan only as far as you can see
  12. Leave the reason behind, not only the fix

Quoted from the skill

/think-like-a-design-engineer

Own the shipped result rather than the handoff, and verify in the running interface.

/think-like-a-design-engineer polish the settings page
  1. Decide the intent before touching pixels
  2. Name the defaults you are rejecting
  3. Build hierarchy from space and weight before size
  4. Write the copy as part of the interface
  5. Let accessibility set the floor
  6. Ask whether it should animate before asking how
  7. Model interaction on the physical world
  8. Reach for what already exists
  9. Treat states as the work, not the cleanup
  10. Verify by looking at the running interface
  11. Review with evidence, and say what you rejected
  12. Train taste on purpose

Quoted from the skill

Writing

/draft-x-post

Draft 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.

/draft-x-post launch the new miniscira
  1. The two questions every draft has to answer
  2. What the code rules out
  3. Mode: launch
  4. Mode: update
  5. Mode: banger

Quoted from the skill

© 2026