Gleam backend
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.From its SKILL.md
npx -y skills add aboio-labs/aboio-skills --skill gleam-backendAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.8 KB, as published. Nobody here has run it
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.