发现 工具与集成 相关 Skills，比较来源仓库和用途，查看适合你工作流的技能说明。
Use when analyzing cognitive load, code complexity, onboarding difficulty, readability concerns, maintainability issues, or applying Ousterhout principles for deep modules, reducing complexity, and strategic pr...
Use when analyzing performance issues, creating benchmarks, or optimizing Elixir/Phoenix code
Use when working with distributed systems, clustering, consensus algorithms, network partitions, CAP tradeoffs, or distributed Erlang/Elixir patterns
Use when implementing or refactoring Elixir code, designing system architecture, working with functional programming patterns, OTP design patterns (GenServer, supervision trees), or needing idiomatic Elixir cod...
Use when working with Phoenix LiveView - streams, forms, authentication, hooks, real-time features, or encountering LiveView-specific issues
llms.txt標準を使用したLLM最適化ドキュメント取得。 外部ドキュメント、APIリファレンス、ライブラリドキュメントを取得する際、 またはユーザーがドキュメント参照、公式ドキュメント、API docs、library documentationに言...
LLM-optimized documentation fetching using llms.txt standard. Use when fetching external documentation, API references, library docs, or when user mentions ドキュメント参照, 公式ドキュメント, API docs, library...
Mycelia-specific scope for planning document audits
Best practices for using NixOS, Flakes, and direnv for reproducible development environments.
Use when preparing for production deployment, conducting code reviews, setting up precommit workflows, adding type specifications, implementing testing strategies, addressing security concerns, or ensuring docu...
JavaScript and TypeScript best practices covering naming conventions, control flow, state management, TypeScript patterns (avoid any/enum, prefer type over interface), safety (input validation, assertions, erro...
SLURM and HPC guidance for Mycelia benchmarks and large-scale analysis
Best practices for using Claude Code in team environments. Covers skill management, knowledge capture, version control, and collaborative workflows.
Best practices for organizing project folders, file naming conventions, and directory structure standards for research and development projects
Convert Erlang code to idiomatic Elixir. Use when migrating Erlang/OTP applications to Elixir, translating gen_server behaviors to GenServer, or refactoring BEAM VM code to leverage Elixir's modern syntax and t...
Bidirectional conversion between Elixir and Roc. Use when migrating projects between these languages in either direction. Extends meta-convert-dev with Elixir↔Roc specific patterns. Use when migrating Elixir pr...
How to check code by linting, building, and testing.
Engineering workflows for WordPress development including compound planning, code review, documentation generation, and git worktree strategies.
Bidirectional conversion between Elixir and Elm. Use when migrating projects between these languages in either direction. Extends meta-convert-dev with Elixir↔Elm specific patterns. Use when migrating server-si...
Panduan refactor khusus Backend (Laravel)
Review code changes for quality, security, and adherence to project conventions. Use after making code changes or when reviewing a pull request.
Read and manage GitHub PRs, issues, and notifications. Use when the user asks to check PRs, view code reviews, find review requests, or check CI status. Helps inform daily standups and code review workflows.
Convert Roc code to idiomatic F#. Use when migrating Roc projects to F#, translating Roc patterns to idiomatic F#, or refactoring Roc codebases. Extends meta-convert-dev with Roc-to-F# specific patterns.
Expert guide to detecting, categorizing, and prioritizing technical debt in Rails applications. Use when: (1) Auditing codebase health, (2) Planning refactoring sprints, (3) Estimating feature impact, (4) Ident...
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库，同一仓库的多个技能可能共享相同数值；它反映仓库关注度，不代表单个技能的安装量或质量评分。