pattern-matching
This skill should be used when the user asks about "Effect Match", "pattern matching", "Match.type", "Match.tag", "Match.when", "Schema.is()", "Schema.is with Match", "exhaustive matching", "discriminated unions", "Match.value", "converting switch to Match", "converting if/else to Match", "TaggedClass with Match", or needs to understand how Effect provides type-safe exhaustive pattern matching.
What this skill does
# Pattern Matching in Effect
## Overview
**Pattern matching replaces complex control flow in Effect code.** Simple `if/else` (no nesting, no `else if`) is allowed, but `else if` chains, nested conditionals, and ternary operators must use pattern matching.
Effect's `Match` module provides:
- **Exhaustive matching** - Compiler ensures all cases handled
- **Type narrowing** - Automatic type inference in each branch
- **Composable matchers** - Build complex patterns from simple ones
- **Predicate support** - Match on conditions, not just values
### What to Use Instead of Imperative Code
| Imperative Pattern | Effect Replacement |
| ----------------------------- | ----------------------------------------------------- |
| Simple `if/else` (no nesting) | Allowed as-is |
| `else if` chains | `Match.value` + `Match.when` |
| Nested `if` statements | `Match.value` + `Match.when` |
| `switch/case` statements | Prefer `Match.type` + `Match.tag` (switch acceptable) |
| Ternary operators (`? :`) | `Match.value` + `Match.when` or simple `if/else` |
| Single null check | `Option.match` |
| Chained optionals | `Option.flatMap` + `Option.getOrElse` |
| Error checks | `Either.match` or `Effect.match` |
| Type guards | `Match.when` with `Schema.is()` |
**When you encounter imperative control flow, refactor it to pattern matching immediately.**
## Basic Matching
### Match.value - Match a Value
```typescript
import { Match } from "effect";
const result = Match.value(input).pipe(
Match.when("admin", () => "Full access"),
Match.when("user", () => "Limited access"),
Match.when("guest", () => "Read only"),
Match.exhaustive,
);
```
### Match.type - Create Reusable Matcher
```typescript
const rolePermissions = Match.type<"admin" | "user" | "guest">().pipe(
Match.when("admin", () => "Full access"),
Match.when("user", () => "Limited access"),
Match.when("guest", () => "Read only"),
Match.exhaustive,
);
// Use multiple times
const perm1 = rolePermissions("admin");
const perm2 = rolePermissions("guest");
```
## Matching Discriminated Unions
### Match.tag - Match by \_tag
```typescript
type Shape =
| { _tag: "Circle"; radius: number }
| { _tag: "Rectangle"; width: number; height: number }
| { _tag: "Triangle"; base: number; height: number };
const area = Match.type<Shape>().pipe(
Match.tag("Circle", ({ radius }) => Math.PI * radius ** 2),
Match.tag("Rectangle", ({ width, height }) => width * height),
Match.tag("Triangle", ({ base, height }) => (base * height) / 2),
Match.exhaustive,
);
area({ _tag: "Circle", radius: 5 }); // 78.54...
```
### Handling Effect Errors
```typescript
type AppError =
| { _tag: "NetworkError"; url: string }
| { _tag: "ValidationError"; field: string; message: string }
| { _tag: "AuthError"; reason: string };
const handleError = Match.type<AppError>().pipe(
Match.tag("NetworkError", (e) => `Failed to fetch ${e.url}`),
Match.tag("ValidationError", (e) => `${e.field}: ${e.message}`),
Match.tag("AuthError", (e) => `Auth failed: ${e.reason}`),
Match.exhaustive,
);
```
## Conditional Matching
### Match.when - Match with Predicate
```typescript
const describeNumber = Match.type<number>().pipe(
Match.when(
(n) => n < 0,
() => "negative",
),
Match.when(
(n) => n === 0,
() => "zero",
),
Match.when(
(n) => n > 0 && n < 10,
() => "small positive",
),
Match.when(
(n) => n >= 10,
() => "large positive",
),
Match.exhaustive,
);
```
### Match.when with Refinement
```typescript
const processInput = Match.type<string | number | boolean>().pipe(
Match.when(
(x): x is string => typeof x === "string",
(s) => `String: ${s.toUpperCase()}`,
),
Match.when(
(x): x is number => typeof x === "number",
(n) => `Number: ${n * 2}`,
),
Match.when(
(x): x is boolean => typeof x === "boolean",
(b) => `Boolean: ${!b}`,
),
Match.exhaustive,
);
```
## Non-Exhaustive Matching
### Match.orElse - Provide Default
```typescript
const greet = Match.type<string>().pipe(
Match.when("morning", () => "Good morning!"),
Match.when("evening", () => "Good evening!"),
Match.orElse(() => "Hello!"),
);
greet("morning"); // "Good morning!"
greet("afternoon"); // "Hello!"
```
### Match.orElseAbsurd - Assert Exhaustive
```typescript
// Use when you believe all cases are covered
// Throws at runtime if unhandled case reached
const handle = Match.type<"a" | "b">().pipe(
Match.when("a", () => 1),
Match.when("b", () => 2),
Match.orElseAbsurd,
);
```
## Advanced Patterns
### Match.not - Negative Matching
```typescript
const classify = Match.type<number>().pipe(
Match.when(
(n) => n === 0,
() => "zero",
),
Match.not(
(n) => n > 0,
() => "negative",
), // Matches when NOT positive
Match.orElse(() => "positive"),
);
```
### Match.whenOr - Multiple Patterns
```typescript
const isWeekend = Match.type<string>().pipe(
Match.whenOr("Saturday", "Sunday", () => true),
Match.orElse(() => false),
);
```
### Match.whenAnd - Combined Conditions
```typescript
interface User {
role: "admin" | "user";
verified: boolean;
}
const canDelete = Match.type<User>().pipe(
Match.whenAnd(
{ role: "admin" },
(u) => u.verified,
() => true,
),
Match.orElse(() => false),
);
```
## Pattern Objects
### Matching Object Shapes
```typescript
const processEvent = Match.type<Event>().pipe(
Match.when({ type: "click" }, (e) => handleClick(e)),
Match.when({ type: "keydown" }, (e) => handleKeydown(e)),
Match.when({ type: "submit" }, (e) => handleSubmit(e)),
Match.orElse(() => {
/* unknown event */
}),
);
```
### Nested Pattern Matching
```typescript
interface Response {
status: number;
data: { type: string; value: unknown };
}
const handleResponse = Match.type<Response>().pipe(
Match.when({ status: 200, data: { type: "user" } }, (r) => `User: ${r.data.value}`),
Match.when({ status: 200, data: { type: "product" } }, (r) => `Product: ${r.data.value}`),
Match.when({ status: 404 }, () => "Not found"),
Match.when({ status: 500 }, () => "Server error"),
Match.orElse(() => "Unknown response"),
);
```
## Converting from if/else
### Before (if/else)
```typescript
function processStatus(status: Status): string {
if (status === "pending") {
return "Waiting...";
} else if (status === "active") {
return "In progress";
} else if (status === "completed") {
return "Done!";
} else if (status === "failed") {
return "Error occurred";
} else {
return "Unknown";
}
}
```
### After (Match)
```typescript
const processStatus = Match.type<Status>().pipe(
Match.when("pending", () => "Waiting..."),
Match.when("active", () => "In progress"),
Match.when("completed", () => "Done!"),
Match.when("failed", () => "Error occurred"),
Match.exhaustive, // Compile error if status type changes!
);
```
## Converting from switch
### Before (switch)
```typescript
function getDiscount(userType: UserType): number {
switch (userType) {
case "regular":
return 0;
case "premium":
return 10;
case "vip":
return 20;
default:
return 0;
}
}
```
### After (Match)
```typescript
const getDiscount = Match.type<UserType>().pipe(
Match.when("regular", () => 0),
Match.when("premium", () => 10),
Match.when("vip", () => 20),
Match.exhaustive,
);
```
## With Effects
```typescript
const handleError = (error: AppError) =>
Match.value(error).pipe(
Match.tag("NetworkError", (e) =>
Effect.gen(function* () {
yield* Effect.logError("Network failure", { url: e.url });
return yield* Effect.fail(e);
}),
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.