gleam-backend
Skill3 starsChanged 9 months agoMITView on GitHub
Gleam backend development skill for the Erlang target. Covers Wisp, Mist, OTP actors, Supervision trees, Squirrel/Parrot SQL codegen integration, JWT auth, and HTTP runners. Use when building server-side logic in Kafka.
In this repository7 other files it gives its agents.
- skills/pg-gleam/CLAUDE.mdCLAUDE.md
- api-gleamSkill
- frontend-testingSkill
- gleamSkill
- lustreSkill
- pg-gleamSkill
- tddSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 44
After creating new actors or supervision trees.
- Distinctive: line 45
When experiencing timeouts, deadlocks, or memory leaks.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Gleam Backend Best Practices
Skill for Gleam server-side development on the Erlang target. Read the relevant reference before writing code.
Token Efficiency
All agents and commands using this skill MUST follow references/token-efficiency.md (from core). Use Read and Grep tools with targeted reads instead of reading entire files.
Reference routing — by task
| Task | References to read |
| Building Wisp HTTP handlers | wisp-framework.md + http-logging-middleware.md |
| SQL Database access | squirrel-guide.md or parrot-guide.md |
| Creating OTP Actors | otp.md + otp-advanced.md |
| OTP Supervision | otp-supervision.md |
| DB Migrations | cigogne.md |
| API Auth / JWT | jwt-ywt.md + auth.md |
| Making outbound HTTP calls | http-runner.md |
Reference routing — by topic
| Topic | Reference |
| HTTP Server config (mist) | mist-server.md |
| Error Handling (3-tier) | three-tier-error-handling.md |
| Decoder Defaults Anti-Pattern | decoder-defaults-anti-pattern.md |
| Storage (S3, Image, PDF) | bucket-s3.md + ansel-image.md + paddlefish-pdf.md |
| Midas algebraic effects | midas-effect-task.md |
Core Backend Principles
- Errors as Values — use 3-tier error handling (AppError), never exceptions.
- SQL is the Contract — never edit generated
sql.gleamfiles. Fix the.sqlsource. - No IO in Core — keep database access in handlers/services, separate from pure business logic.
Review Commands
When to use /otp-review:
- After creating new actors or supervision trees.
- When experiencing timeouts, deadlocks, or memory leaks.
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.