89 skills · sorted by relevance
Review code changes for unnecessary complexity, including unused flexibility, avoidable dependencies, and abstractions with little purpose. Receive concise findings that name what to remove, what can replace it, and how many lines could be cut.
Kubernetes is the operating system for the cloud. It schedules containers, handles networking, manages storage, and keeps your apps running. But K8s has a steep learning curve - abstractions on abstractions on abstractions. This skill covers the core concepts (Pods, Deployments, Services), production patterns (health checks, resource limits, HPA), and the gotchas that catch everyone (namespace confusion, service discovery, secret management). 2025 reality: You probably don't need to run your own cluster. Use managed K8s (EKS, GKE, AKS) unless you have a very good reason not to. Focus on writing good manifests, not managing etcd. Use when "kubernetes, k8s, kubectl, deployment manifest, helm chart, kustomize, pod, service yaml, ingress, horizontal pod autoscaler, hpa, kubernetes, k8s, containers, orchestration, devops, cloud-native, helm, kustomize" mentioned.
The English summary is being prepared. Showing the original description.
Specialized skill for testing file system operations using System.IO.Abstractions. Use when you need to test File, Directory, Path operations, or simulate file system. Covers IFileSystem, MockFileSystem, file read/write testing, directory operation testing, etc. Keywords: file testing, filesystem, file testing, file system testing, IFileSystem, MockFileSystem, System.IO.Abstractions, File.ReadAllText, File.WriteAllText, Directory.CreateDirectory, Path.Combine, mock file system, file abstraction
The English summary is being prepared. Showing the original description.
Keep implementation small by checking whether work is needed, then considering existing code, standard libraries, platform features, and installed dependencies. Helps avoid unnecessary packages, helper classes, and boilerplate before writing new code.
Write, review, and debug Rust applications, including ownership and borrowing rules that govern memory use. Covers trait-based APIs, explicit error handling, asynchronous work with tokio, and tests with Cargo validation.
You are an expert in @react-three/drei, the companion library for React Three Fiber that provides 100+ ready-made components and hooks for common 3D patterns. You help developers add orbit controls, environment maps, text rendering, HTML overlays, loaders, performance utilities, shaders, and abstractions — eliminating boilerplate and letting teams focus on creative work instead of Three.js plumbing.
The English summary is being prepared. Showing the original description.
Writes, reviews, and debugs idiomatic Rust code with memory safety and zero-cost abstractions. Implements ownership patterns, manages lifetimes, designs trait hierarchies, builds async applications with tokio, and structures error handling with Result/Option. Use when building Rust applications, solving ownership or borrowing issues, designing trait-based APIs, implementing async/await concurrency, creating FFI bindings, or optimizing for performance and memory safety. Invoke for Rust, Cargo, ownership, borrowing, lifetimes, async Rust, tokio, zero-cost abstractions, memory safety, systems programming.
The English summary is being prepared. Showing the original description.
Cross-platform desktop development for macOS and Windows -- platform abstractions, UI convention differences, and multi-platform CI/CD. Activate on: cross-platform app, macOS and Windows, platform differences, DMG installer, MSI installer, NSIS installer, Cmd vs Ctrl, platform abstractions, menu bar differences, native conventions. NOT for: mobile apps, web-only apps, Tauri-specific internals (use rust-tauri-development).
The English summary is being prepared. Showing the original description.
Cross-platform desktop development for macOS and Windows -- platform abstractions, UI convention differences, and multi-platform CI/CD. Activate on: cross-platform app, macOS and Windows, platform differences, DMG installer, MSI installer, NSIS installer, Cmd vs Ctrl, platform abstractions, menu bar differences, native conventions. NOT for: mobile apps, web-only apps, Tauri-specific internals (use rust-tauri-development).
The English summary is being prepared. Showing the original description.
Detects leaky abstractions in PHP code. Identifies implementation details exposed in interfaces, concrete returns from abstract methods, framework leakage into domain, and infrastructure concerns in application layer.
The English summary is being prepared. Showing the original description.
Guide coding tasks toward the smallest complete change by checking affected code, reusing existing features, and avoiding unnecessary additions. It also calls for relevant checks and concise explanations of what changed, what remains unchecked, and any risks.
Migrate code and API calls from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5. Update platform-specific model identifiers and address reported prompt behavior issues, such as excessive tool use or unnecessary code complexity.
Make working code easier to read and maintain while preserving its behavior. The skill identifies tangled conditions, unclear names, duplication, and unnecessary abstractions, then guides small refactoring steps checked against existing tests and project conventions.
Audit a codebase for unnecessary complexity, including dead code, duplicated state, redundant interfaces, and obsolete compatibility paths. Receive evidence-backed simplification candidates, or authorize changes that remove justified targets and validate the behavior that must remain.
Evaluate substantial software changes against the actual problem, current system, and concrete users or components that need them. Choose a sufficient scope, assess consequences, and, when implementation is requested, make the change and verify its behavior.
Simplify Rust code in RTK by replacing verbose loops, unnecessary copies, and excessive abstractions with common Rust patterns. Preserve behavior and project requirements, including error context, fallback handling, exit codes, and existing test modules.
Choose Rust design patterns for RTK modules that process command output. Use concrete examples to structure configuration, prevent type mixups, manage parser states, and select abstractions suited to the task without adding unnecessary architectural complexity.
Investigate Cherry Studio code to identify unused behavior, duplicated state, and unnecessary abstractions. Turn a few well-supported findings into cleanup proposals that document current consumers, removal scope, risks, and observable acceptance criteria.
Design and refactor Python components with clear responsibilities and simple structure. Assess when to split large classes, combine objects instead of extending them, and extract shared code without introducing unnecessary abstractions.
Set up model training with torchforge for reinforcement learning, where rewards guide improvement. Covers training configurations, custom reward and loss functions, and distributed execution with Monarch and TorchTitan, keeping algorithm experiments separate from infrastructure concerns.
Audit an entire codebase for unnecessary complexity and dependencies. Receive a ranked list of code to delete, simplify, or replace with standard library and platform features, with file paths and estimated reductions.
Review code changes for correctness, readable names, clear interfaces, and design problems. Examine duplication, hidden assumptions, and unnecessary abstractions, then report actionable findings with file locations, explanations, and concrete suggestions for fixes.
Review and simplify the ego-lite codebase by finding unused code, duplicated state, and unnecessary layers. The skill checks real callers and API requirements, explains behavior changes, and coordinates implementation, tests, and documentation updates.
Guides reinforcement learning, where models learn from rewards, using torchforge and PyTorch. Covers reward design, custom loss functions, and distributed training so researchers can experiment with algorithms while keeping infrastructure concerns separate.