effect-system
Skill17 starsChanged 9 months agoApache-2.0View on GitHub
Implement effect systems to track and control side effects in programs.
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-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
- monad-transformerSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 26
Effect Checking: Verify effect constraints
- Distinctive: line 44
Start with coarse-grained effects (IO vs Pure)
- Distinctive: line 45
Use row polymorphism for flexibility
- Distinctive: line 85
When side effects are not a concern
≈ “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
Effect System
Effect systems track what computational effects a function may perform, enabling reasoning about purity, exceptions, I/O, and other side effects at the type level.
When to Use This Skill
- Building pure functional languages
- Reasoning about side effects
- Implementing effect handlers
- Security and sandboxing
- Optimization (pure code can be optimized more)
What This Skill Does
- Effect Annotation: Track effects in types
- Effect Checking: Verify effect constraints
- Effect Polymorphism: Generic effect handling
- Effect Row Types: Combine multiple effects
- Effect Masking: Hide effects from callers
Key Concepts
| Concept | Description |
| Effect | Computational side effect (IO, State, Throw) |
| Effect Set | Collection of effects |
| Effect Row | Extensible row of effects |
| Effect Polymorphism | Generic over effect sets |
| Effect Handler | Interpret effects |
| Pure | No effects |
Tips
- Start with coarse-grained effects (IO vs Pure)
- Use row polymorphism for flexibility
- Consider effect subtyping
- Effect handlers enable flexible interpretation
- Log effects for debugging
Common Use Cases
- Pure functional languages
- Effect tracking for optimization
- Sandboxing and security
- Effect-based testing
- Resource management
Related Skills
algebraic-effects- Algebraic effect handlerstype-class-implementer- Monad type classesmonad-transformer- Monad transformersinformation-flow-analyzer- Security effects
Canonical References
| Reference | Why It Matters |
| Lucassen & Gifford, "Polymorphic Effect Systems" (POPL 1988) | Original paper on effect systems |
| Talpin & Jouvelot, "The Type and Effect Discipline" (POPL 1992) | Effect polymorphism formalization |
| Leijen, "Koka: Programming with Row Polymorphic Effect Handlers" (2017) | Modern effect system design |
Tradeoffs and Limitations
Approach Tradeoffs
| Approach | Pros | Cons |
| Monads | Composable | Syntactic overhead |
| Effect systems | Cleaner syntax | Complex inference |
| Algebraic effects | Flexible | Runtime overhead |
When NOT to Use This Skill
- When side effects are not a concern
- Performance-critical code
- When exceptions suffice
Limitations
- Effect inference can be complex
- Higher-order effects are tricky
- Interaction with existing code
Assessment Criteria
A high-quality implementation should have:
| Criterion | What to Look For |
| Soundness | All effects tracked |
| Inference | Automatic effect inference |
| Polymorphism | Effect polymorphism |
| Handlers | Effect interpretation |
Quality Indicators
✅ Good: Sound, infers effects, supports polymorphism ⚠️ Warning: Manual annotations required ❌ Bad: Misses effects, no polymorphism
Research Tools & Artifacts
Effect system implementations:
| Tool | Language | What to Learn |
| Koka | Koka | Row-based effects |
| Frank | Frank | Handler calculus |
| Eff | Eff | Direct handlers |
| Multicore OCaml | OCaml | Effects in OCaml |
Research Frontiers
1. Effect Inference
- Goal: Automatic effect tracking
- Papers: "Effect Inference" (various)
Implementation Pitfalls
| Pitfall | Real Consequence | Solution |
| Effect inference | Complexity | Use bidirectional |
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.