Loading...
Loading...
Found 73 Skills
Refactor Flutter/Dart code to improve maintainability, readability, and performance. This skill applies Dart 3 features like records, patterns, and sealed classes, implements proper state management with Riverpod or BLoC, and uses Freezed for immutable models. It addresses monolithic widgets, missing const constructors, improper BuildContext usage, and deep nesting. Apply when you notice widgets doing too much, performance issues from unnecessary rebuilds, or legacy Dart 2 patterns.
Refactor ASP.NET Core/C# code to improve maintainability, readability, and adherence to best practices. Transforms fat controllers, duplicate code, and outdated patterns into clean, modern .NET code. Applies C# 12 features like primary constructors and collection expressions, SOLID principles, Clean Architecture patterns, and proper dependency injection. Identifies and fixes anti-patterns including service locator, captive dependencies, and missing async/await patterns.
Generate Flutter applications using Clean Architecture with feature-first structure, Riverpod state management, Dio + Retrofit for networking, and fpdart error handling. Use this skill when creating Flutter apps, implementing features with clean architecture patterns, setting up Riverpod providers, handling data with Either type for functional error handling, making HTTP requests with type-safe API clients, or structuring projects with domain/data/presentation layers. Triggers include "Flutter app", "clean architecture", "Riverpod", "feature-first", "state management", "API client", "Retrofit", "Dio", "REST API", or requests to build Flutter features with separation of concerns.
PROACTIVELY build backend APIs with Node.js/TypeScript and Go. Use when designing APIs, implementing auth, or building microservices. Applies Clean Architecture, SOLID, DRY, YAGNI, KISS principles.
Flutter开发完整指南：Clean Architecture架构规范、TDD测试工作流、BLoC状态管理、故障排除与代码生成
Transform code into clean, testable architecture using SOLID principles, Clean Architecture, and proven design patterns
Hexagonal architecture layering for Java services with strict boundaries. Trigger: When structuring Java apps by Domain/Application/Infrastructure, or refactoring toward clean architecture.
Clean Architecture, Data Models, Tech Stack, Error Handling & Platform Channels
Clean Architecture, Data Models, Tech Stack, Error Handling & Platform Channels
Architecture audit that maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books. Triggers when: user asks to audit architecture, review folder/module structure, check for circular imports, understand how the codebase is organized, or asks "does this follow clean architecture?", "why does everything depend on everything?", "are our layers correct?", "where should this code live?". Also triggers for onboarding requests: "explain this codebase to a new developer" or "give me a codebase tour" (use onboarding mode). Also triggers when user mentions: dependency inversion / hexagonal architecture / bounded contexts / circular imports / tangled dependencies / module coupling / package structure / spaghetti code / directory layout. Use this skill proactively when project structure, module boundaries, or architectural decisions are discussed — even without the word "audit". Do NOT trigger for: PR-level code review (use brooks-review) or line-level refactoring questions — this skill analyzes structural/module-level concerns, not individual functions.
The Essentialist. Ruthlessly simplifying code, removing dead features, and enforcing Clean Architecture.
Flutter-Architektur - Clean Architecture & Best Practices. Use when designing architecture or reviewing code structure.