Loading...
Loading...
Found 918 Skills
Guides usage of @aptos-labs/ts-sdk for interacting with the Aptos blockchain from TypeScript/JavaScript applications. Covers client setup, account management, transaction building & submission, view functions, event queries, coin/token operations, wallet adapter integration, and error handling. Triggers on: 'typescript sdk', 'ts-sdk', 'aptos sdk', 'aptos client', 'sdk setup', 'interact with contract', 'call aptos', 'aptos javascript', 'frontend integration', 'wallet adapter', 'connect wallet'.
Set up the Commerce Engine TypeScript SDK in any project. Framework detection, token storage selection, environment variables, and migration guidance.
State management with Zustand for Remix/React applications. Covers store creation, TypeScript patterns, persistence, and Shopify-specific state patterns.
Guide for Mongoose ODM (2025-2026 Edition), covering Mongoose 8.x/9.x, TypeScript integration, and performance best practices.
Skill for creating custom lint rules by leveraging the existing linter ecosystems of various programming languages. This is a linter designed for AI Agents rather than humans, and its error messages function as correction instruction prompts for AI. Create custom rules in the `lints/` directory using standard methods for each language, including Rust (dylint), TypeScript/JavaScript (ESLint), Python (pylint), Go (golangci-lint), etc. Use this skill in the following scenarios: (1) When you want AI to enforce project-specific coding rules; (2) When you want to create lint rules that output AI-readable correction instructions when violations occur; (3) When you want to enforce naming conventions, structural patterns, and consistency rules through AI-driven linting. Triggers: "Create a linter rule", "Add a lint rule", "Enforce this pattern", "AI linter", "Custom lint", "Code rules", "Naming rules", "Structural rules", "create a linter rule", "add a lint rule", "enforce this pattern", "AI linter".
SOLID principles for object-oriented design — Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion. Covers motivation, violations, fixes, and multi-language examples (PHP, Java, Python, TypeScript, C++) for building maintainable, extensible software.
Coding conventions enforcement agent. Auto-invoked when writing new code, reviewing code quality, adding headers, or checking documentation compliance across Python, TypeScript/JavaScript, and C#/.NET.
Guide for exposing PostHog product endpoints as MCP tools. Use when creating new or updating API endpoints, adding MCP tool definitions, scaffolding YAML configs, or writing serializers with good descriptions. Covers the full pipeline from Django serializer to generated TypeScript tool handler.
Biome linter and formatter for JavaScript/TypeScript. Covers configuration, rules, and integration patterns. Replaces ESLint + Prettier for faster development experience. USE WHEN: user mentions "biome", "linting", "formatting", "code style", "biome.json", asks about "setup linter", "format code", "migrate from ESLint", "migrate from Prettier", "biome rules", "biome configuration" DO NOT USE FOR: ESLint configuration - Biome is an ESLint replacement, Prettier configuration - Biome is a Prettier replacement, TypeScript compilation - use TypeScript compiler, Code quality principles - use `clean-code` skill
Set up, develop, test, and deploy Render Workflows. Covers first-time scaffolding (via CLI or manual), task patterns (retries, subtasks, fan-out), local development, Dashboard deployment, and troubleshooting. Use when a user wants to set up Render Workflows for the first time, install the Render Workflows SDK (Python or TypeScript), scaffold a workflow service, add or modify tasks, test locally, or deploy to Render.
Deep code simplification, refactoring, and quality refinement. Analyzes structural complexity, anti-patterns, and readability debt, then applies targeted refactoring preserving exact behavior. Language-agnostic: Python, Go, TypeScript/JavaScript, Rust. Use this skill when the goal is simplification and clarity rather than bug-finding. Triggers on: "simplify this code", "clean up my code", "refactor for clarity", "reduce complexity", "make this more readable", "code quality pass", "tech debt cleanup", "run the code refiner", "simplify recent changes", "this code is messy", "too much nesting", "this function is too long", "clean this up before I PR it", "tidy up my code", cyclomatic complexity, cognitive complexity, code smells.
Enforce Vertical Slice Architecture (VSA) when building applications in any language (Go, .NET/C#, Java, Kotlin, TypeScript, Python, etc.) and any type (web API, mobile backend, CLI, event-driven). Organize code by feature/use-case instead of technical layers. Each feature is a self-contained vertical slice with a single entry point that receives the router/framework handle and its dependencies. Use when the user says "vertical slice architecture", "VSA", "organizar por feature", "feature-based architecture", "slice architecture", or when building a new app or feature and the project already follows VSA conventions. Also use when reviewing or refactoring code to align with VSA principles.