القائمة
Universal testing discipline — pyramid, test quality, what never to mock. Load when writing or reviewing tests in any stack.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Context engineering — memory navigation, textual graph traversal, progressive disclosure, recovery. Load when assembling context for a task or when lost.
Implementation-side security discipline — headers, dependencies, secrets, authz. Load for hardening work (sec-ops domain).
Commit conventions, branching, anchors in messages, and the git safety rules. Load for any git operation beyond status/diff.
Anti-generic-AI design discipline — bans, tells, and the slop test. Load for ANY new UI surface or visual redesign. Inspired by Impeccable (Apache 2.0).
Motion & animation discipline — purpose, performance, reduced-motion. Load when work involves animation, transitions or scroll effects.
Microcopy discipline — buttons, errors, empty/loading/success states, alt text. Voice and tone come from the project's memory, not from this skill.
| name | testing-discipline |
| description | Universal testing discipline — pyramid, test quality, what never to mock. Load when writing or reviewing tests in any stack. |
Stack-agnostic: frameworks come from memory-long §stack; targets from TESTS.md. This is the discipline layer.
.only/.skip), assertions on internals, test-order dependence, weakening coverage configs to pass (hook-enforced)Unit ~70% (fast, isolated, logic) · Integration ~20% (boundaries: API contracts, DB access) · E2E ~10% (critical user paths only — expensive, flaky-prone).
The unit under test · the project's type system · pure functions · time/randomness (inject instead). Mock only true boundaries: network, filesystem, third-party services, clocks.
Each test: one behavior, named as a sentence (rejects expired tokens), arrange-act-assert visible, failure message diagnosable without reading the test body.