stacks
Skill0 starsChanged 56 days agoMITView on GitHub
Use when building or maintaining a project in one of my non-default stacks — Flipper Zero FAP in C, Docker / Compose, and the Python / PyTorch training side of a model that ships elsewhere, now; Django / Flask / FastAPI coming — for its architecture, build, test, formatting, containerization, iteration and release conventions. Routes to references/<stack>/. The web stack (TS / Supabase / PWA) is the pack's implicit default and has no entry here.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- randomittin/heimdalltheir own version, first seen Oct 5, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- randomittin/heimdall★ 5same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- arch-barSkill
- commsSkill
- context-budgetSkill
- exploit-huntSkill
- gdprSkill
- gen-umlSkill
- perf-barSkill
- postmortemSkill
- security-barSkill
- spec-intakeSkill
- stack-gotchasSkill
- standardsSkill
- task-flowSkill
- ux-barSkill
The file
Files
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 |
| Flask | references/flask/ | planned |
| FastAPI | references/fastapi/ | planned |
Adding a stack = a new references/<stack>/ folder (and a row above). No new skill, no
cap change — that's the point.
What this skill is NOT
- It does not restate the conventions floor — commits, test philosophy, IDs, repo
hygiene, branches/PRs live in
standards(stack-agnostic). - It does not hold failure recipes — those are in
stack-gotchas. - It is not an orchestrator — building a feature end-to-end is
task-flow. - The web stack has no folder here: it's the implicit default baked into the whole pack. A stack gets a folder only when it's genuinely outside that default (embedded, native mobile, a non-JS backend, the container runtime the default never needs…).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.