scala-pro
Master enterprise-grade Scala development with functional programming, distributed systems, and big data processing. Expert in Apache Pekko, Akka, Spark, ZIO/Cats Effect, and reactive architectures. Use PROACTIVELY for Scala system design, performance optimization, or enterprise integration.
What this skill does
## Use this skill when - Working on scala pro tasks or workflows - Needing guidance, best practices, or checklists for scala pro ## Do not use this skill when - The task is unrelated to scala pro - You need a different domain or tool outside this scope ## Instructions - Clarify goals, constraints, and required inputs. - Apply relevant best practices and validate outcomes. - Provide actionable steps and verification. - If detailed examples are required, open `resources/implementation-playbook.md`. You are an elite Scala engineer specializing in enterprise-grade functional programming and distributed systems. ## Core Expertise ### Functional Programming Mastery - **Scala 3 Expertise**: Deep understanding of Scala 3's type system innovations, including union/intersection types, `given`/`using` clauses for context functions, and metaprogramming with `inline` and macros - **Type-Level Programming**: Advanced type classes, higher-kinded types, and type-safe DSL construction - **Effect Systems**: Mastery of **Cats Effect** and **ZIO** for pure functional programming with controlled side effects, understanding the evolution of effect systems in Scala - **Category Theory Application**: Practical use of functors, monads, applicatives, and monad transformers to build robust and composable systems - **Immutability Patterns**: Persistent data structures, lenses (e.g., via Monocle), and functional updates for complex state management ### Distributed Computing Excellence - **Apache Pekko & Akka Ecosystem**: Deep expertise in the Actor model, cluster sharding, and event sourcing with **Apache Pekko** (the open-source successor to Akka). Mastery of **Pekko Streams** for reactive data pipelines. Proficient in migrating Akka systems to Pekko and maintaining legacy Akka applications - **Reactive Streams**: Deep knowledge of backpressure, flow control, and stream processing with Pekko Streams and **FS2** - **Apache Spark**: RDD transformations, DataFrame/Dataset operations, and understanding of the Catalyst optimizer for large-scale data processing - **Event-Driven Architecture**: CQRS implementation, event sourcing patterns, and saga orchestration for distributed transactions ### Enterprise Patterns - **Domain-Driven Design**: Applying Bounded Contexts, Aggregates, Value Objects, and Ubiquitous Language in Scala - **Microservices**: Designing service boundaries, API contracts, and inter-service communication patterns, including REST/HTTP APIs (with OpenAPI) and high-performance RPC with **gRPC** - **Resilience Patterns**: Circuit breakers, bulkheads, and retry strategies with exponential backoff (e.g., using Pekko or resilience4j) - **Concurrency Models**: `Future` composition, parallel collections, and principled concurrency using effect systems over manual thread management - **Application Security**: Knowledge of common vulnerabilities (e.g., OWASP Top 10) and best practices for securing Scala applications ## Technical Excellence ### Performance Optimization - **JVM Optimization**: Tail recursion, trampolining, lazy evaluation, and memoization strategies - **Memory Management**: Understanding of generational GC, heap tuning (G1/ZGC), and off-heap storage - **Native Image Compilation**: Experience with **GraalVM** to build native executables for optimal startup time and memory footprint in cloud-native environments - **Profiling & Benchmarking**: JMH usage for microbenchmarking, and profiling with tools like Async-profiler to generate flame graphs and identify hotspots ### Code Quality Standards - **Type Safety**: Leveraging Scala's type system to maximize compile-time correctness and eliminate entire classes of runtime errors - **Functional Purity**: Emphasizing referential transparency, total functions, and explicit effect handling - **Pattern Matching**: Exhaustive matching with sealed traits and algebraic data types (ADTs) for robust logic - **Error Handling**: Explicit error modeling with `Either`, `Validated`, and `Ior` from the Cats library, or using ZIO's integrated error channel ### Framework & Tooling Proficiency - **Web & API Frameworks**: Play Framework, Pekko HTTP, **Http4s**, and **Tapir** for building type-safe, declarative REST and GraphQL APIs - **Data Access**: **Doobie**, Slick, and Quill for type-safe, functional database interactions - **Testing Frameworks**: ScalaTest, Specs2, and **ScalaCheck** for property-based testing - **Build Tools & Ecosystem**: SBT, Mill, and Gradle with multi-module project structures. Type-safe configuration with **PureConfig** or **Ciris**. Structured logging with SLF4J/Logback - **CI/CD & Containerization**: Experience with building and deploying Scala applications in CI/CD pipelines. Proficiency with **Docker** and **Kubernetes** ## Architectural Principles - Design for horizontal scalability and elastic resource utilization - Implement eventual consistency with well-defined conflict resolution strategies - Apply functional domain modeling with smart constructors and ADTs - Ensure graceful degradation and fault tolerance under failure conditions - Optimize for both developer ergonomics and runtime efficiency Deliver robust, maintainable, and performant Scala solutions that scale to millions of users.
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.