Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

bahadirkisbet

@bahadirkisbet source repo

9 published skills

  1. ▌
    Adr · bahadirkisbet
    Use to record or document a significant, hard-to-reverse technical decision that has been made or is being finalized (framework, data model, service boundary, protocol, build-vs-buy) so the reasoning survives, or when the user says /adr. Also use before re-deciding something — to check existing ADRs first. This captures a decision; it does not deliberate one (weighing the options is less-is-more).
    0 installs
  2. ▌
    Bugfix Tdd · bahadirkisbet
    Use when fixing any bug, regression, or "it does the wrong thing" report. Not for net-new features (ordinary TDD) or pure behavior-preserving refactors.
    0 installs
  3. ▌
    Blind Review · bahadirkisbet
    Use when a major implementation is complete and per-task reviews have passed, before merging a multi-file feature or a finished plan — the final quality gate. Reviewers read the code independently and never see the implementer's account of the work; you pick which intent artifact they judge against — none (cold audit), the spec (compliance), or the plan (drift). Not for single-file fixes, docs-only changes, or behavior-preserving refactors.
    0 installs
  4. ▌
    Less Is More · bahadirkisbet
    Use before committing to any architecture, design, or non-trivial technical direction — when the user asks how to build or structure something, proposes a system or feature, or faces a hard-to-reverse structural decision. Not for localized code style or a single function's implementation.
    0 installs
  5. ▌
    More Is Less · bahadirkisbet
    More Is Less
    0 installs
  6. ▌
    Retrospective · bahadirkisbet
    Use when ending a long session, when the user says /retro or /retrospective, or after a session with multiple corrections, friction, or workarounds. Not for short sessions with no friction.
    0 installs
  7. ▌
    No Silent Errors · bahadirkisbet
    Use whenever a failure or error path is in play — error handling, exceptions, swallowed failures, fallbacks, or empty/None/default values standing in for missing required data — and when modeling a type so a failure cannot be represented silently. The concern is failures that pass unnoticed; reach for it any time a value, call, or branch could fail without anyone seeing. Not triggered merely because code is involved, or because input is being parsed or formatted — triggered when how something fails, or is kept from failing, is at stake.
    0 installs
  8. ▌
    Verify The Premise · bahadirkisbet
    Verify the Premise
    0 installs
  9. ▌
    Pipeline Verification · bahadirkisbet
    Use after any change, before calling it done or claiming it works — especially a change that touches shared code, a contract, or a user-visible path. Triggers whenever you are tempted to rely on unit tests alone.
    0 installs