Skip to content

umararshad4/honey-stack / skills/principles

principles

Verified

Engineering principles index; read the leaf file before citing a principle.

Principles

Each row is one engineering principle. The gist is a pointer, not the principle: the leaf file holds the rule, its limits and its tells.

Cite a principle only if you read its file this session. A citation from the gist alone borrows the name without the content, and the leaf's caveats ("skip it when…", "distinct from…") are usually what decides the case.

Use

  1. Match the situation to a row by its gist. Done when: you have one to three candidate rows, or none fits.
  2. Read each candidate's file in references/. Done when: every principle you will cite has been read this session.
  3. Apply it, and when you cite it, name the file and the line that decided the call, e.g. "per references/fix-root-causes.md: a guard is a fix only when the state it handles is legitimate".

Index

PrincipleGistFile
Attack the premiseTwo fixes on one premise failed the same gate: test the premise before a third fixreferences/attack-the-premise.md
Boundary disciplineValidate at system edges (CLI, config, network, APIs); trust internal types; keep logic purereferences/boundary-discipline.md
Build the leverNon-trivial work gets a codemod, script or generator a reviewer can rerunreferences/build-the-lever.md
Encode lessons in structureA repeated instruction or correction becomes a lint, flag, check or scriptreferences/encode-lessons-in-structure.md
Exhaust the design spaceNo precedent for a UI or architecture call: prototype two or three, compare side by sidereferences/exhaust-the-design-space.md
Experience firstChoose user delight over implementation convenience; fewer polished featuresreferences/experience-first.md
Explain the numberBefore trusting a measured number, find what limits it and what else it might measurereferences/explain-the-number.md
Fix root causesTrace the symptom to where the system first went wrong and fix it therereferences/fix-root-causes.md
Foundational thinkingGet core types and data structures right before logicreferences/foundational-thinking.md
Guard the context windowRoute bulk output to subagents; keep summaries in the main threadreferences/guard-the-context-window.md
Laziness protocolBias toward deletion and the smallest change that solves itreferences/laziness-protocol.md
Make operations idempotentSteps converge to the same end state after crashes, restarts and retriesreferences/make-operations-idempotent.md
Migrate callers, then delete legacy APIsMove every caller and delete the old API in one wave; no compat layerreferences/migrate-callers-then-delete-legacy-apis.md
Minimize reader loadCount layers to trace and state to hold; collapse one-caller wrappersreferences/minimize-reader-load.md
Model the domainEncode the domain in a data structure instead of scattered conditionalsreferences/model-the-domain.md
Never block on the humanReversible work: decide and keep going instead of askingreferences/never-block-on-the-human.md
Outcome-oriented executionIn phased rewrites, converge on the target; no throwaway intermediate compatreferences/outcome-oriented-execution.md
Prove it worksVerify against the real artifact, not a proxy or a self-reportreferences/prove-it-works.md
Redesign from first principlesA new requirement reshapes the design instead of being bolted onreferences/redesign-from-first-principles.md
Separate before serializing shared stateConcurrent writers: remove the sharing first, lock only for a real invariantreferences/separate-before-serializing-shared-state.md
Sequence verifiable unitsSmall units that each end verified, checked before the nextreferences/sequence-verifiable-units.md
Subtract before you addRemove dead code and redundant layers first, then build on the simpler basereferences/subtract-before-you-add.md
Test behavior, not implementationAssert what users observe; tests survive internal refactorsreferences/test-behavior-not-implementation.md
Type-system disciplineIllegal states unrepresentable, branded primitives, parse at boundaries, exhaust variantsreferences/type-system-discipline.md
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 196kUpdated Claude CodeCodexVerifiedInstall