Loading...
Loading...
Found 245 Skills
Migrates Honcho TypeScript SDK code from v1.6.0 to v2.0.0. Use when upgrading @honcho-ai/sdk, fixing breaking changes after upgrade, or when errors mention removed APIs like .core, getConfig, observations, or snake_case properties.
Complex migration strategies for LangChain applications. Use when migrating from legacy LLM frameworks, refactoring large codebases, or implementing phased migration approaches. Trigger with phrases like "langchain migration strategy", "migrate to langchain", "langchain refactor", "legacy LLM migration", "langchain transition".
Simplify and clean code
Manage advanced Cursor Composer techniques for complex edits. Triggers on "advanced composer", "composer patterns", "multi-file generation", "composer refactoring". Use when working with cursor advanced composer functionality. Trigger with phrases like "cursor advanced composer", "cursor composer", "cursor".
Use when architecture feels component-based but ownership is split across technical buckets (tables/init/debug), causing god files, duplicate paths, and hidden dependency flow.
Transform code into clean, testable architecture using SOLID principles, Clean Architecture, and proven design patterns
Specific rules for Starknet React projects, focusing on blockchain integration.
Remove dead code and duplication pragmatically with a 5-phase systematic approach
Test-driven development using the RED-GREEN-refactor cycle. Suitable for users who want to build new features or fix bugs with TDD, mention "red-green-refactor", want to use integration testing, or ask about "test-first development".
Java Web dead code cleanup and refactoring expert. It safely identifies and removes dead code, with testing and verification performed at every step. Trigger conditions: User requests for dead code cleanup, refactoring optimization, and unused code removal.
ReactLynx best practices covering dual-thread architecture and React patterns. Provides rules reference for writing, static analysis for reviewing, and auto-fix for refactoring.
Use when multiple workflows duplicate the same operational logic, when deciding what belongs in actions vs shared services, or when refactoring repeated operational blocks across domain flows. Use when adding new features that share mechanics with existing ones.