Skill UI

Transforms shorthand, quasi-code, or fuzzy natural-language notes into production-ready implementations, bridging collaborators with different expertise and ensuring robust, expert-quality output.

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.

Guides preserving React 18 concurrent patterns during migration to React 19 while outlining post-migration adoption of new APIs like use(), Actions, useOptimistic, and Suspense data fetching so concurrent behavior stays intact.

This guide serves as a comprehensive reference for source-file migration patterns required when upgrading to React 19. It details critical API changes, such as updating `ReactDOM.render` to `createRoot().render()`, modernizing ref handling, and adjusting legacy context usage. It is essential for developers migrating large, existing React applications to ensure compatibility with the latest React standards.

Analyzes Copilot guidance files and repository docs to craft structured README.md content, detailing the project purpose, architecture, technology stack, workflows, coding standards, testing approach, and contributing advice for fellow developers.

Automate Reddit workflows via Rube MCP and Composio: search subreddits, create posts, manage comments, browse top content, and edit or delete submissions through authenticated Reddit connections.

This skill provides comprehensive guidelines and techniques for safe code refactoring. It focuses on improving code structure, readability, and maintainability without altering the external behavior or functionality of the system. Learn to address common code smells, such as long methods, duplicated logic, god objects, and primitive obsession, using established design patterns and best practices. It emphasizes that refactoring should be gradual, test-driven, and methodical.

Refactors a specified method into smaller helper routines so the cognitive complexity stays below a given threshold while keeping validation, error handling, and behavior intact.

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.

This micro-prompt guides AI agents to adopt the mindset of an interactive programmer. It emphasizes using the REPL (Read-Eval-Print Loop) for systematic system exploration and modification, treating the system state as the ultimate source of truth. It also reminds the agent to utilize structural editing tools and maintain todo lists, significantly improving the accuracy and efficiency of the development workflow in live coding environments.

Transforms repo structure and commit history into two actionable markdowns—an architecture summary and a narrative story—so analysts can trace system intent, data flow, and team evolution.

Maintains a project-specific research knowledge base that accumulates papers, ideas, experiments, and claims plus their typed relationships, enabling ingestion, queries, updates, and analytics with a compact query pack.