effect-review
This skill should be used when the user asks to "review code", "review my changes", "check effect patterns", "run effect review", "effect review", "review for effect best practices", or wants a comprehensive code review against Effect-TS conventions, branded types, observability, error handling, test coverage, and UI quality.
What this skill does
# Effect-TS Code Review Orchestrate a multi-agent review of code changes against Effect-TS best practices. ## Workflow ### Step 1: Discover Changed Files Run `git diff --name-only main...HEAD` to find all changed files on the current branch. If that fails (e.g., on main), fall back to `git diff --name-only HEAD~1` or `git diff --name-only` for unstaged changes. List the changed files for the user. ### Step 2: Categorize Files Split files into categories: - **Backend Effect files**: `.ts` files NOT ending in `.test.ts`, NOT config files (`.config.ts`, `tsconfig`, etc.), NOT UI component library directories - **Test files**: `.test.ts` files - **UI files**: `.tsx` files - **Skip**: `.md`, `.json`, `.yml`, `.css`, config files, generated files ### Step 3: Launch Sub-Agents in Parallel Based on which categories have files, launch the appropriate agents using the Agent tool. Launch all applicable agents in a **single message** for maximum parallelism. **If backend Effect files exist**, launch these 4 agents in parallel: - `effect-primitives-reviewer` — checks Effect primitives (Array, Match, Option, forEach, no try/catch, no async/await, Layer not Effect.provide) - `branded-types-reviewer` — checks branded type usage for all entity IDs - `otel-reviewer` — checks tracing setup (Effect.fn trace names, annotateCurrentSpan, structured logging) - `error-reviewer` — checks error definitions and handling (Schema.TaggedError, catchTag, rich context) - `typescript-reviewer` — checks TypeScript patterns (no `as any`, prefer `satisfies` over `as`, no manual type annotations on inferred types) **If test files exist**, launch: - `test-coverage-reviewer` — checks @effect/vitest patterns and assesses coverage gaps **If UI files exist**, launch: - `ui-reviewer` — checks component library usage, accessibility, layout, brand consistency For each agent, provide the prompt: > Review the following files for [agent's specialty]. Read each file and produce a structured report with Critical/Warning/Info findings. > > Files to review: > - [list of file paths] > > Also review the reference guide at `references/[relevant-reference].md` (relative to this skill) for the detailed checklist. ### Step 4: Unified Report After all agents complete, compile results into a single report: ``` # Effect Review Report ## Effect Primitives [agent output] ## Branded Types [agent output] ## OTEL / Observability [agent output] ## Error Handling [agent output] ## TypeScript Patterns [agent output] ## Test Coverage [agent output] ## UI Quality [agent output] --- ## Summary | Category | Critical | Warning | Info | |----------|----------|---------|------| | Primitives | X | Y | Z | | Branded Types | X | Y | Z | | OTEL | X | Y | Z | | Errors | X | Y | Z | | TypeScript | X | Y | Z | | Tests | X | Y | Z | | UI | X | Y | Z | | **Total** | **X** | **Y** | **Z** | **Verdict**: PASS / NEEDS WORK / FAIL **Score: X/10** ``` - **PASS**: 0 critical findings - **NEEDS WORK**: 1-3 critical findings - **FAIL**: 4+ critical findings ### Scoring (0-10) After compiling all findings, assign an overall score from 0 to 10: - **10**: Perfect — no findings at all, exemplary Effect-TS code - **9**: Excellent — only minor info-level suggestions - **8**: Great — a few warnings, no criticals - **7**: Good — several warnings but no criticals - **6**: Acceptable — 1 critical or many warnings - **5**: Needs work — 2-3 criticals - **4**: Below standard — 4-5 criticals - **3**: Poor — 6+ criticals or fundamental pattern violations - **2**: Very poor — majority of code ignores Effect patterns - **1**: Minimal compliance — almost no Effect patterns followed - **0**: No compliance — entirely non-Effect code submitted as Effect code Display the score prominently at the end of the report. ## Reference Files Detailed checklists with codebase-specific examples: - `references/effect-primitives.md` — Effect Array, Match, Option, forEach, Schema, Layer - `references/branded-types.md` — Branded type usage and known types list - `references/otel-patterns.md` — Tracing, span annotations, structured logging - `references/error-patterns.md` — Schema.TaggedError, catchTag, error context - `references/typescript-patterns.md` — No `as any`, prefer `satisfies` over `as`, no manual type annotations - `references/test-patterns.md` — @effect/vitest, it.layer, coverage assessment - `references/effect-atom-patterns.md` — Effect-Atom React patterns, queries, mutations, Result.builder
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.