Pragmatism — Aparigraha (अपरिग्रह)
Aparigraha — non-accumulation. Four directional gates on every change: (1) Check-Before-Create — search the codebase and declared dependencies for an equivalent before authoring anything new; (2) Conform-Before-Improve — match house style within scope, surface deviations as suggestions instead of silently rewriting; (3) Surgical-Before-Sweeping — produce the minimal diff that solves the problem, every change reversible in one step; (4) Validate-Before-Trust — whenever reusing or modifying existing code, walk the edge-case checklist (null/empty, boundaries, type/locale, concurrency, failure paths, performance envelope, domain edges, backward compatibility). Checking is mandatory; reusing is conditional.
Read the full skill on GitHub. The site shows the first section; the canonical full content with all principles, examples, and rules lives in the repo.
View full SKILL.md on GitHub ›What the full skill covers
- Context
- Scope
- The Four Directional Principles
- Invocation Triggers
- Decision Tree — Where to Route
- Inputs
- Outputs
- Guardrails