Flutter Cross-Project Patterns — Unified Programming Lessons

Sources: CarSah (LL-001–LL-020) + Hermex_Android (LL-001–LL-042) + Azdal Patterns: 54 — full bodies are in the four reference files below (split 2026-08-22 because SKILL.md exceeded 100K and patches were being rejected). Purpose: SINGLE source of truth for ALL Flutter/Dart/Android programming lessons. Load before every implementation task. Governance/process lessons belong in agent-repo-handoff-loop (referenced from there) — this skill is code-level.

Enforcement levels (adopted 2026-08-11 — founder decision)

Every pattern is classified by two exclusion filters then a weighted score:

1. 🚪 GATE — machine-enforced: a lint/test/script fails the build if violated. Universal truth + costly to retrofit.
2. 📏 RULE — documented convention enforced by review. Universal truth but not machine-detectable.
3. 🧭 JUDGMENT — project decision: the skill gives criteria, the answer depends on project context.

Negation axis (RFC 2119 mapping): 🚪 MUST / MUST NOT · 📏 SHOULD / SHOULD NOT · 🧭 MAY.

How to read this skill (IMPORTANT — this file is now an index)