monad-transformer
Skill17 starsChanged 9 months agoApache-2.0View on GitHub
Implements monad transformers for composing monads in functional languages.
In this repository98 other files it gives its agents.
- abstract-interpretation-engineSkill
- abstract-machineSkill
- acsl-annotation-assistantSkill
- actor-model-implementerSkill
- algebraic-effectsSkill
- alias-and-points-to-analysisSkill
- axiomatic-semanticsSkill
- bidirectional-type-checkingSkill
- bisimulation-checkerSkill
- capability-systemSkill
- closure-converterSkill
- common-subexpression-eliminatorSkill
- concurrency-verifierSkill
- constant-propagation-passSkill
- contextual-equivalenceSkill
- control-flow-analysisSkill
- coq-proof-assistantSkill
- cps-transformerSkill
- dafny-verifierSkill
- dataflow-analysis-frameworkSkill
- dead-code-eliminatorSkill
- defunctionalizationSkill
- denotational-semantics-builderSkill
- dependent-type-implementerSkill
- dsl-embeddingSkill
- effect-handlers-implementerSkill
- effect-systemSkill
- effect-type-systemSkill
- escape-analysisSkill
- existential-typesSkill
- ffi-designerSkill
- fuzzer-generatorSkill
- gadt-implementerSkill
- garbage-collector-implementerSkill
- graalvm-truffle-implementerSkill
- gradual-typing-implementerSkill
- higher-order-abstract-syntaxSkill
- hoare-logic-verifierSkill
- incremental-computationSkill
- information-flow-analyzerSkill
- inline-expanderSkill
- interprocedural-analysisSkill
- invariant-generatorSkill
- jit-compiler-builderSkill
- lambda-calculus-interpreterSkill
- language-server-protocolSkill
- lean-proverSkill
- lexer-generatorSkill
- linear-type-implementerSkill
- liveness-analysisSkill
- llvm-backend-generatorSkill
- lock-free-data-structureSkill
- loop-optimizerSkill
- loop-termination-proverSkill
- macro-expanderSkill
- memory-allocatorSkill
- message-passing-systemSkill
- mlir-dialect-designerSkill
- model-checkerSkill
- module-systemSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 40
Start with simple stacks (Reader + IO)
- Distinctive: line 41
Use mtL for lifting operations
- Distinctive: line 42
Consider monad-unlift for better ergonomics
≈ “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
Monad Transformer
Implements monad transformers - reusable layers that add capabilities to monads, enabling composition of multiple effects in functional programs.
When to Use This Skill
- Combining state, error handling, IO, and other effects
- Building layered monadic interfaces
- Creating custom monad stacks for applications
- Implementing embedded DSLs with multiple effects
What This Skill Does
- Transformer Library: Provides standard transformers (Reader, Writer, State, Error, IO)
- Stack Construction: Builds monad stacks from transformer layers
- Lift/Unlift: Implements monad lifting between transformer layers
- Typeclass Instances: Derives Functor, Applicative, Monad for transformer stacks
Key Concepts
| Concept | Description |
| Monad Transformer | Type constructor that adds capabilities to a monad |
| Monad Stack | Composition of multiple transformers |
| Lifting | Running actions from inner monads in outer context |
| MonadIO | Interface for IO actions in transformer stacks |
Tips
- Start with simple stacks (Reader + IO)
- Use mtL for lifting operations
- Consider monad-unlift for better ergonomics
- Order matters: inner monad first
Related Skills
effect-system- Effect trackingalgebraic-effects- Alternative effect compositiontype-class-implementer- Type class implementation
Canonical References
| Reference | Why It Matters |
| Grabmüller, "Monad Transformers: Step by Step" (2010) | Comprehensive tutorial on building monad transformers |
| Elliott, Marlow, et al., "The Haskell Transformers Library" | Standard library design for composable monad transformers |
| Kiselyov, "Eff: Functional Effects and Monads in OCaml" (2013+) | Alternative approach to algebraic effects |
Tradeoffs and Limitations
| Approach | Pros | Cons |
| Transformers | Composable, reusable | Type complexity, lift fatigue |
| Algebraic Effects | Simpler effect syntax | Less mature tooling |
| Free Monads | Pure, testable | Performance overhead |
Assessment Criteria
| Criterion | What to Look For |
| Correctness | All typeclass laws satisfied |
| Lifting | Proper lift implementation |
| Composability | Transformers stack correctly |
| Performance | Minimal overhead |
Quality Indicators
✅ Good: Typeclass laws satisfied, proper lifting, stacks compose ⚠️ Warning: Partial typeclass support, some lift issues ❌ Bad: Type errors, incorrect behavior
Research Tools & Artifacts
Monad transformer implementations:
| Tool | Language | What to Learn |
| mtl | Haskell | Standard transformers |
| transformers | Haskell | Alternative |
| Cats | Scala | Scala integration |
| Purescript | Purescript | Eff alternative |
Research Frontiers
1. Effect Systems
- Goal: Replace transformers with effects
- Approach: Row polymorphism, effect handlers
Implementation Pitfalls
| Pitfall | Real Consequence | Solution |
| Lift cascade | Too many lifts | Use monad-freer |
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.

