stackslisted

# stacks ## Overview One home for the **per-stack structure & build conventions** of stacks that fall **outside the pack's implicit default** (the web stack — TS/Supabase/PWA — which every other skill already assumes). One skill, many stacks: each stack is a folder under `references/`, so breadth grows without adding skills or spending a trigger per stack. ## When to use - Starting or extending a project in a stack listed below — read that stack's `references/<stack>/` files for its layering, build, tests, formatting and release flow. - For a **failure** in one of these stacks → `eskills:stack-gotchas` (it carries the diagnose-and-recover recipes). ## How it's organized `references/<stack>/` holds the concrete, copy-ready conventions for that stack, each pattern traced to a real repo. Read the folder for the stack you're in. | Stack | Folder | Status | | --------------------- | --------------------- | ----------------------------------------------------------- | | Flipper Zero FAP (C) | `references/flipper/` | architecture · build-and-test · formatting · release-please | | Docker / Compose | `references/docker/` | toolchain-images · services · dev-environments | | ML training (PyTorch) | `references/ml/` | iteration-loop · metrics · pitfalls | | Django | `references/django/` | _planned_