Skill UI

Guides using ChangeNotifier with provider for Flutter state management, covering model creation, providing to the widget tree, consuming via Consumer and Provider.of, optimization practices, and testing notifications.

Diagnoses and explains fixes for Flutter runtime and layout errors such as RenderFlex overflow, unbounded constraints, scroll-controller conflicts, and inappropriate setState calls during build, helping developers resolve issues quickly.

This skill provides comprehensive guidelines for writing clean, idiomatic, and maintainable Go code. It covers critical best practices for variable declaration, control flow structuring (e.g., early returns, switch statements), function design (e.g., parameter limits, context usage), and ensuring correct data structure initialization. Use this skill when writing new Go features, reviewing existing code for clarity, or establishing team coding standards.

Build interconnected Excel financial models (income statement, balance sheet, cash flow, DCF, cap table, scenarios) driven by an assumptions sheet so each output updates automatically from provided inputs.

This skill provides a comprehensive guide on utilizing the `provider` package for state management and dependency injection in Flutter. It covers different provider types (e.g., `ChangeNotifierProvider`, `FutureProvider`, `StreamProvider`), best practices for setup using `MultiProvider`, and efficient ways to consume state using `context.watch`, `context.select`, and `Consumer` widgets. It is essential for building scalable and maintainable Flutter applications.

Guides Flutter/Dart developers through Riverpod setup and best practices for defining providers, using refs, handling lifecycles, combining async data, performing side effects, observing changes, and testing so app state stays consistent and leak-free.

This comprehensive guide outlines best practices for developing high-quality, idiomatic, and maintainable enterprise applications using Kotlin and Spring Boot. It covers architectural patterns, dependency injection using primary constructors, managing state with data classes, implementing robust RESTful APIs, handling transactions, and leveraging Kotlin features like null safety and Coroutines for asynchronous programming. It also provides guidance on modern testing strategies (Kotest, Testcontainers).

This guide provides comprehensive patterns for migrating Enzyme unit tests to React Testing Library (RTL), especially when upgrading to React 18. It emphasizes the crucial philosophical shift from testing internal implementation details (like state or props) to asserting visible user behavior. Learn best practices for rewriting shallow/mount/simulate calls into modern, accessible, and resilient RTL queries, ensuring your tests reflect how a user genuinely interacts with the component.

Provides a comprehensive reference for migrating deprecated and unsafe class component lifecycle methods (such as componentWillMount, componentWillReceiveProps, and componentWillUpdate) to modern, React 18 compliant patterns. This guide is essential when updating legacy codebases, helping developers correctly identify the semantic purpose of the method and choose the correct replacement hook (e.g., componentDidMount or getDerivedStateFromProps), thus preventing common migration errors.

This tool automates the entire workflow of creating a GitHub Pull Request (PR) directly from a structured specification file. It analyzes the template, extracts requirements, checks for existing PRs, creates the draft, updates the body and title with specification details, and finally transitions the PR state to 'Ready for Review'. This significantly streamlines the feature request submission process, ensuring all necessary documentation and metadata are included.

A comprehensive reference for diagnosing and fixing silent breaking changes in React 18 class components. This guide covers how React 18 automatically batches state updates in asynchronous contexts (e.g., setTimeout, Promises, async/await), providing patterns for handling state reads after awaiting, and offering guidance on when to correctly use `flushSync` versus refactoring.

A comprehensive template for planning large-scale, multi-file refactoring tasks. It enforces a systematic approach by requiring developers to map out the current state, target state, affected files, and execution phases (Types, Implementation, Tests). Crucially, it mandates detailed verification and a robust rollback plan to ensure code stability during major changes.