Loading...
Loading...
Found 2,003 Skills
Collaboratively turn ambiguous ideas into implementation-ready designs before coding. Use when requests involve new features, behavior changes, architecture decisions, or prompts like "brainstorm", "design this", "plan this", or "think through options". Clarify intent via one-question-at-a-time dialogue, compare 2-3 approaches with trade-offs, and converge on a validated design spec.
Robyn backend scaffolding and architecture guidance for projects using robyn-config. Use when creating or evolving Robyn services, choosing DDD vs MVC, choosing SQLAlchemy vs Tortoise, adding new entities/routes/repositories with robyn-config add, auditing Robyn backend quality, or authoring and improving skill markdown for Robyn engineering workflows.
Analyze routes and recommend whether to use Server Actions or API routes based on use case patterns including authentication, revalidation, external API calls, and client requirements. Use this skill when deciding between Server Actions and API routes, optimizing Next.js data fetching, refactoring routes, analyzing route architecture, or choosing the right data mutation pattern. Trigger terms include Server Actions, API routes, route handler, data mutation, revalidation, authentication flow, external API, client-side fetch, route optimization, Next.js patterns.
Creates Source-of-Truth docs (Project Brief, Decisions, Glossary) for new app ideas. Use at the very start of a project to lock scope, stack, and terminology. Essential for preventing drift in downstream PRD, UI/UX, and Architecture phases.
Design and optimize a sales funnel for a solopreneur business. Use when mapping how customers move from first awareness to paying customer, identifying where leads drop off, building or improving any stage of the funnel (awareness, consideration, decision, retention), or optimizing conversion rates. Covers funnel architecture, stage-by-stage tactics, conversion benchmarks, solopreneur-specific funnel models (self-serve vs. high-touch), and funnel analytics. Trigger on "sales funnel", "design my funnel", "optimize my funnel", "conversion funnel", "why aren't people buying", "lead to customer", "funnel stages", "improve conversions".
Documentation architecture for this repository. Use when creating, updating, or reviewing README.md, CONTRIBUTING.md, or docs/ files. Covers separation of concerns, vendor documentation standards, cross-references, and validation.
Build native UIs in the style of Raph Levien, architect of Druid, Xilem, and Vello. Emphasizes declarative reactive architecture, synchronized tree transformations, GPU-accelerated rendering, and idiomatic Rust patterns. Use when designing responsive, beautiful native UIs or 2D graphics systems.
Official NestJS starter with modular architecture and Jest testing.
This skill helps users get started with existing (brownfield) projects by scanning the codebase, documenting structure and purpose, analyzing architecture and technical stack, identifying design flaws, suggesting improvements for testing and CI/CD pipelines, and generating AI agent constitution files (AGENTS.md) with project-specific context, coding principles, and UI/UX guidelines.
Create or update system design documents. Supports initial design and incremental design modes. Use when users need technical architecture, API design, data models, design changes, or impact analysis. Triggers on keywords like "system design", "architecture", "technical design", "API design", "design change", "impact analysis", "design change", "impact analysis".
Core guide for interacting with Euler Finance V2 protocol. This skill should be used when building DeFi integrations, managing lending positions, or understanding Euler architecture. Triggers on tasks involving lending, borrowing, collateral, liquidation, EVC, EVK, or core Euler operations. For specialized topics, see companion skills.
Write production-quality skills for Claude from scratch or improve existing ones. Use this skill whenever the user wants to author a SKILL.md, design a skill folder, write skill instructions, craft frontmatter descriptions, structure a multi-file skill, or get guidance on skill architecture and best practices. Also use when the user says "write a skill", "build a skill", "create a skill for X", "help me make a skill", "improve this skill", "review my skill", or asks about skill structure, trigger phrases, progressive disclosure, or skill design patterns. This skill focuses on the writing craft — producing well-structured, effective skill content — not on eval/benchmark workflows.