Functional Patterns
Higher-order functions, composition, monads, immutability, and functional programming idioms.
Install
/plugin marketplace add sethdford/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sethdford/claude-skills --skill functional-patternsgit clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/engineer/implementation-patterns/skills/functional-patterns ~/.claude/skills/functional-patternsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Functional Patterns Using functional programming principles for clearer, more maintainable code. ## Context You are using functional patterns. Understand functional principles and idioms. ## Domain Context - **Pure Functions**: No side effects; same input → same output - **Composition**: Build complex functions from simple ones - **Higher-Order**: Functions taking/returning functions - **Immutability**: Data doesn't change; create new versions instead - **Monads**: Pattern for handling effects (Maybe, Either, IO) ## Instructions 1. **Prefer Pure Functions**: Write functions without side effects 2. **Compose Functions**: Chain simple functions together 3. **Use Higher-Order**: Map, filter, fold; powerful abstractions 4. **Embrace Immutability**: Don't mutate; create new values 5. **Handle Effects**: Use monads or similar for side effects 6. **Test Easily**: Pure functions are trivial to test ## Anti-Patterns - Treating FP as dogma; some problems need mutation - Immutability everywhere killing performance; profile before pessimizing - Monads without understanding; they're useful but not required - Chaining operations so deeply it's unreadable; readability matters - Avoiding mutation for simple local data; FP isn't a religion ## Further Reading - Richard Bird & Philip Wadler, _Introduction to Functional Programming_ - Evan Czaplicki, _Elm guide_ (great FP introduction) - Brian Lonsdorf, _Mostly Adequate Guide to FP_
Details
- Skill name
functional-patterns- Repository
- sethdford/claude-skills
- Path
engineer/implementation-patterns/skills/functional-patterns/SKILL.md- License
- MIT
- Repo updated
- 11 March 2026
FAQ
What does the Functional Patterns skill do?
Higher-order functions, composition, monads, immutability, and functional programming idioms.
How do I install the Functional Patterns skill?
Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Functional Patterns popular?
It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.
Related skills
A B Test Design
48sethdford/claude-skills
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
A B Test Design Pm
48sethdford/claude-skills
Analytics and experimentation skill for product managers.
Abuse Case Design
48sethdford/claude-skills
Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.
Go to Market Strategy
48sethdford/claude-skills
Launch and go-to-market skill for product managers.
Event Driven Architecture
48sethdford/claude-skills
Design systems that communicate through events instead of direct service calls. Use when building loosely-coupled, scalable, and resilient architectures.
Handoff Spec
48sethdford/claude-skills
Create developer handoff specifications with measurements, behaviors, assets, and edge cases.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.