Loading...
Loading...
Found 13 Skills
Perform comprehensive Rust code quality reviews against best practices for async Rust, error handling, testing, and project structure
TypeScript standards and best practices with modern tooling. Use when working with TypeScript or TypeScript React files.
TypeScript-specific coding conventions and type system patterns. Always load this skill when writing or reviewing TypeScript code.
General software development best practices covering code quality, testing, security, performance, and maintainability across technology stacks
Expertise in Go programming according to the Google Go Best Practices. Focuses on actionable advice for naming, error handling, performance, testing, and general idiomatic Go to ensure high-quality, maintainable, and efficient codebases.
Rails code patterns and conventions following rubocop-rails-omakase style.
Use when symfony test doubles mocking
React 18 patterns for LlamaFarm Designer. Covers components, hooks, TanStack Query, and testing.
Comprehensive Flutter development guidelines covering architecture, state management, performance optimization, testing, and cross-platform best practices. Use when building, refactoring, or reviewing Flutter applications for mobile, web, and desktop platforms. Covers widget patterns, Riverpod/BLoC state management, navigation with go_router, Firebase integration, platform channels, custom painting, animations, CI/CD, and production deployment.
RED-GREEN-REFACTOR cycle with strict phase gates. Write failing test first, implement minimum code to pass, then refactor while keeping tests green. Use when implementing new features, fixing bugs with test-first approach, improving test coverage, or when user mentions TDD. Use for "TDD", "test first", "red green refactor", "write tests", or "implement with tests". Do NOT use for debugging existing failures (use systematic-debugging) or for refactoring without new tests (use systematic-refactoring).
This skill should be used when the user asks to "implement a feature in Elixir", "refactor this module", "should I use a GenServer here?", "how should I structure this?", "use the pipe operator", "add error handling", "make this concurrent", or mentions protocols, behaviours, pattern matching, with statements, comprehensions, structs, or coming from an OOP background. Contains paradigm-shifting insights.
Permission test. Use for testing.