gleam
Skill3 starsChanged 9 months agoMITView on GitHub
Core Gleam language skill. Use when writing pure Gleam functions, parsing or validating input (Parse, Don't Validate), decoding JSON, designing a library, or defining shared domain types — not backend (see gleam-backend) or frontend (see lustre).
In this repository7 other files it gives its agents.
- skills/pg-gleam/CLAUDE.mdCLAUDE.md
- api-gleamSkill
- frontend-testingSkill
- gleam-backendSkill
- lustreSkill
- pg-gleamSkill
- tddSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Start from git diff to scope work, Grep for patterns, and read targeted line ranges rather than whole files.
≈ “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 Core Fundamentals
Consolidated skill for pure Gleam development. Read the relevant reference before writing code.
Token Efficiency
Start from git diff to scope work, Grep for patterns, and read targeted line ranges rather than whole files. Full policy: the repo-root references/token-efficiency.md.
Reference routing — by task
| Task | References to read |
| New to Gleam syntax | fundamentals/language-basics.md + fundamentals/language-features.md |
| Input validation & Types | fundamentals/type-design.md + fundamentals/validation-valid.md |
| JSON Decoding / Encoding | fundamentals/decoding.md + fundamentals/decode-map-vs-then.md |
| Error handling & AppError | fundamentals/error-handling.md |
| Designing a Library | library/library-design.md + library/ffi.md |
Reference routing — by topic
| Topic | Reference |
| Official Conventions (C1-C10) | fundamentals/conventions.md |
| Common mistakes / pitfalls | fundamentals/common-pitfalls.md |
| Pattern Matching | fundamentals/case-patterns.md |
| Code Patterns (use, result.try) | fundamentals/code-patterns.md |
| Tooling (check, format, LSP) | fundamentals/tooling.md |
| Snapshot testing (birdie) | fundamentals/birdie-snapshot-testing.md |
| Stdlib functions | fundamentals/stdlib.md |
| Module name gotchas (regexp vs regex) | fundamentals/stdlib-module-names.md |
| Parser combinators (nibble) | fundamentals/parsing-nibble.md |
| Helper-first refactoring | fundamentals/helper-first-refactoring.md |
| Higher-order SQL helpers | fundamentals/higher-order-sql-helpers.md |
| String / character filtering | fundamentals/string-character-filtering.md |
Core Principles
- Parse, Don't Validate — opaque types for validated data (
fundamentals/type-design.md). - Errors as Values — one
AppErrortype,Resulteverywhere (fundamentals/error-handling.md).
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.