scala-expert
Use when implementing scala functionality with production-grade patterns and safeguards.
- License 许可
- MIT
- 最近更新
- 2026-04-11
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- scala-expert
- metadata
- { "hermes": { "tags": [ "codex-agent", "general" ], "source": "codex-field-kit/general" } }
- description
- Use when implementing scala functionality with production-grade patterns and safeguards.
03 SKILL.md 正文
Scala Expert
Focus Areas
- Advanced functional programming techniques in Scala
- Type safety and typesafe design patterns
- Immutable data structures and their advantages
- Concurrency and parallelism in Scala
- Efficient collection operations and transformations
- Pattern matching and case classes
- Using Scala's REPL for rapid prototyping
- Implicit classes and extension methods
- Scala's type system: variance, bounds, and constraints
- Utilizing Scala's built-in libraries and features
Approach
- Prioritize immutability and pure functions
- Emphasize clear and concise code using Scala's features
- Leverage pattern matching for clean conditional logic
- Utilize Scala's powerful type inference capabilities
- Implement tail-recursive solutions to optimize performance
- Employ higher-order functions and combinators effectively
- Explore functional error handling with Try, Option, Either
- Use lazy evaluation to optimize performance where suitable
- Regularly refactor code for clarity and maintainability
- Encourage the use of the latest Scala version to leverage new language features
Quality Checklist
- Ensure all functions have clear and explicit type signatures
- Validate that code adheres to Scala style guidelines
- Test concurrency implementations for race conditions and deadlocks
- Profile memory usage and optimize where necessary
- Confirm immutability of all data structures in critical code paths
- Ensure proper use of pattern matching without redundancies
- Avoid code smells and anti-patterns specific to Scala
- Ensure comprehensive test coverage with ScalaTest or similar
- Code must compile with no warnings or errors in strict mode
- Verify all custom operators or implicits have clear documentation
Output
- Idiomatic Scala code adhering to functional programming practices
- Scaladoc comments for all public classes and methods
- Unit tests using Scala's testing frameworks like ScalaTest
- Performance benchmarks for key features and methods
- Code examples demonstrating effective use of Scala features
- Sample applications showing best practices in Scala
- Recommendations for code improvement and optimization
- Reports on type hierarchy and variance effective use
- Scripts for automated building and testing using sbt
- Guidance on evolving existing codebases to Scala best practices
04 同仓库更多 Skills
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
swarm-planner
[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.
super-swarm-spark
Only to be triggered by explicit super-swarm-spark commands.
role-creator
Create and install Codex custom agent roles in ~/.codex/config.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).
read-github
Read and search GitHub repository documentation via gitmcp.io MCP service. **WHEN TO USE:** - User provides a GitHub URL - User mentions a specific repo in owner/repo format - User asks "what does this repo do?", "read the docs for X repo", or similar - User wants to search code or docs within a repo
planner
Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.