berserquir

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.

Infrastructure composition patterns — immutable infra, GitOps, golden images, cattle-not-pets, day-2 thinking. Tool-agnostic.

Container discipline — OCI images, runtime hygiene, security posture. Open standard (OCI), not vendor; registry/runtime from memory-long §stack.

GitOps discipline — desired state in git, reconciliation, drift semantics, environment promotion. Tool-agnostic (works with any reconciler).

Kubernetes workload discipline — probes, resources, RBAC, disruption budgets. CNCF standard, not vendor; cluster provisioning belongs to infra.

Routing & connectivity discipline — BGP, OSPF, hybrid links, the tunnel classics. Protocol-level (IETF), vendor syntax from memory-long §stack.

Release discipline — versioning, feature flags, progressive delivery, rollback. The deploy-side counterpart to pipeline-discipline (CI-side).

ML/LLM operations discipline — versioned model/prompt artifacts, eval gates, drift and cost monitoring. Minimal MVP scope (expands in F4).

Incident discipline — severity, containment-first, comms, blameless postmortems. Load when production is (or might be) on fire.

Code structure discipline — layering, dependency direction, composition, when patterns earn their place. Load for any non-trivial backend structure decision.

System architecture discipline — decomposition, boundaries, communication, scale, failure design. Load for architectural work; decisions land as ADRs.

Background work discipline — queues, retries, idempotency, delivery semantics. Load for any job, queue, webhook or scheduled work.

Caching discipline — invalidation, TTLs, stampede protection, layer choice. Load before adding any cache; caching is a bug you choose deliberately.

Observability discipline — structured logs, correlation, metrics, actionable alerts. Load when adding logging, metrics or diagnosing production behavior.

Infrastructure security discipline — identity, encryption, secrets, audit. Perimeter/platform counterpart to security-hardening (app-side).

Network architecture discipline — segmentation, routing, perimeter, traffic control. Cloud-agnostic; vendor constructs from memory-long §stack.

Platform structure discipline — environment strategy, account segmentation, landing zone, module composition. Cloud-agnostic.

DR/HA discipline — RTO/RPO as requirements, DR tiers, backup verification, failover design. Cloud-agnostic.

Technical SEO discipline — per-page metadata contract, structured data, site-wide crawlability. Web-universal; framework helpers from memory-long §stack.

CI/CD discipline — pipeline structure, credentials, debugging methodology, gates. Tool-agnostic; the CI platform comes from memory-long §stack.

FinOps discipline — cost allocation, budgets, commitment analysis, unit economics. Cloud-agnostic; vendor tooling from memory-long §stack.

In-Context Learning — select and inject worked examples (demos) before executing recurring task types. Load when a task matches a known pattern family.

Spec-Driven Development — the PRD/SPECS/TESTS triangle, EARS criteria, governance hierarchy. Load when creating or changing specs, features, or ADRs.

Universal testing discipline — pyramid, test quality, what never to mock. Load when writing or reviewing tests in any stack.

REST/API conventions — resource design, status codes, error shapes, validation-at-boundary. Load for any endpoint work.

Data layer discipline — migrations, transactions, integrity, query safety. Load for any schema or data-access work.

Accessibility discipline (WCAG 2.1 AA floor) — semantics, keyboard, contrast, screen readers. Load for any UI work.

Framework-agnostic component discipline — typed contracts, composition, environment safety, cleanup. Load for any UI component work.

Core Web Vitals budgets and frontend performance discipline. Load when work affects rendering, assets or interactivity.

Styling discipline for any mechanism (utility framework, CSS-in-JS, vanilla) — tokens, states, responsive, no ad-hoc values.

IaC state & module discipline — state hygiene, module boundaries, drift. Load for any IaC structural work.