Explore skills
Showing 29671–29700 of 71536 skills
Configuration module patterns for LlamaFarm. Covers Pydantic v2 models, JSONSchema generation, YAML processing, and validation.
llama-farm/llamafarm
Stars: 838Claude CodeCodexDesigner subsystem patterns for LlamaFarm. Covers React 18, TanStack Query, TailwindCSS, and Radix UI.
llama-farm/llamafarm
Stars: 838Claude CodeCodexElectron patterns for LlamaFarm Desktop. Covers main/renderer processes, IPC, security, and packaging.
llama-farm/llamafarm
Stars: 838Claude CodeCodexFetch GitHub CI failure information, analyze root causes, reproduce locally, and propose a fix plan. Use `/fix-ci` for current branch or `/fix-ci <run-id>` for a specific run.
llama-farm/llamafarm
Stars: 838Claude CodeCodexGenerate specialized skills for each subsystem in the monorepo. Creates shared language skills and subsystem-specific checklists for high-quality AI code generation.
llama-farm/llamafarm
Stars: 838Claude CodeCodexShared Go best practices for LlamaFarm CLI. Covers idiomatic patterns, error handling, and testing.
llama-farm/llamafarm
Stars: 838Claude CodeCodexShared Python best practices for LlamaFarm. Covers patterns, async, typing, testing, error handling, and security.
llama-farm/llamafarm
Stars: 838Claude CodeCodexRAG-specific best practices for LlamaIndex, ChromaDB, and Celery workers. Covers ingestion, retrieval, embeddings, and performance.
llama-farm/llamafarm
Stars: 838Claude CodeCodexReact 18 patterns for LlamaFarm Designer. Covers components, hooks, TanStack Query, and testing.
llama-farm/llamafarm
Stars: 838Claude CodeCodexAnalyze the current session and propose improvements to skills. **Proactively invoke this skill** when you notice user corrections after skill usage, or at the end of skill-heavy sessions. Also use when user says "reflect", "improve skill", or "learn from this".
llama-farm/llamafarm
Stars: 838Claude CodeCodexUniversal Runtime best practices for PyTorch inference, Transformers models, and FastAPI serving. Covers device management, model loading, memory optimization, and performance tuning.
llama-farm/llamafarm
Stars: 838Claude CodeCodexServer-specific best practices for FastAPI, Celery, and Pydantic. Extends python-skills with framework-specific patterns.
llama-farm/llamafarm
Stars: 838Claude CodeCodexGuidelines for creating temporary files in system temp directory. Use when agents need to create reports, logs, or progress files without cluttering the repository.
llama-farm/llamafarm
Stars: 838Claude CodeCodexShared TypeScript best practices for Designer and Electron subsystems.
llama-farm/llamafarm
Stars: 838Claude CodeCodexManage LlamaFarm worktrees for isolated parallel development. Create, start, stop, and clean up worktrees.
llama-farm/llamafarm
Stars: 838Claude CodeCodexSelect and start the next unblocked RIPDPI portfolio task.
po4yka/RIPDPI
Stars: 86Claude CodeCodexUse this skill when adding, restructuring, or validating the nuxt-ui-tools playground examples, shell, navigation, or route-level composition demos.
ChronicStone/nuxt-ui-tools
Stars: 2Claude CodeCodexMaster TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects.
ChronicStone/nuxt-ui-tools
Stars: 2Claude CodeCodexAn example user-invoked skill that demonstrates frontmatter options and the skills/<name>/SKILL.md layout
nota-america/forgecat-agent-profiles
Stars: 93Claude CodeCodexAn example user-invoked skill that demonstrates frontmatter options and the skills/<name>/SKILL.md layout
nota-america/forgecat-agent-profiles
Stars: 93Claude CodeCodexDesign test strategies and test plans. Trigger with "how should we test", "test strategy for", "write tests for", "test plan", "what tests do we need", or when the user needs help with testing approaches, coverage, or test architecture.
nota-america/forgecat-agent-profiles
Stars: 93Claude CodeCodexDesign test strategies and test plans. Trigger with "how should we test", "test strategy for", "write tests for", "test plan", "what tests do we need", or when the user needs help with testing approaches, coverage, or test architecture.
nota-america/forgecat-agent-profiles
Stars: 93Claude CodeCodexReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
jaem1n207/synchronize-tab-scrolling
Stars: 18Claude CodeCodexDeep competitive intelligence for any market. Analyzes competitors' products, pricing, customer sentiment, GTM strategy, and growth signals using real web data. Produces battle cards, pricing landscape, and feature matrix. Use when the user wants to understand their competitive landscape, analyze competitors, compare products in a market, or research who they're competing against. Triggers for "who are my competitors", "competitive analysis", "competitor research", "battle cards", "pricing comparison", "competitor pricing", "market players", "competitive intelligence", "competitive landscape", "who else is in this space", "competitive moat", or any request to profile, compare, or map competitors in a category. Works standalone — no prior startup-design session needed.
ferdinandobons/startup-skill
Stars: 1.2kClaude CodeCodexDesign, validate, and plan a startup from scratch. Covers market research, competitive analysis, business model, brand identity, product definition, financial projections, and validation experiments. Trigger when the user has a startup idea to explore, wants to validate a business concept, needs a business plan or lean canvas, asks for market sizing or competitive landscape, wants brand positioning or go-to-market strategy, or says anything like "I have an idea for..." or "is this idea worth pursuing". Also handles resuming from a previous checkpoint.
ferdinandobons/startup-skill
Stars: 1.2kClaude CodeCodexBuild investor-ready pitch scripts in multiple formats (10-min, 5-min, 2-min, 1-min elevator, investor email). Produces pitch narratives, Q&A preparation, pitch scoring rubric, and optional investor roleplay practice. Use when the user wants to create a pitch, prepare for investor meetings, craft a startup pitch, write a fundraising narrative, or practice their pitch. Triggers for "pitch deck", "investor pitch", "pitch my startup", "fundraising deck", "seed deck", "how to pitch", "investor meeting", "demo day", "prepare pitch", "pitch script", "elevator pitch for investors", "pitch practice", "practice my pitch", "investor roleplay", or any request to present a startup to investors, accelerators, or partners. Works standalone — no prior startup-design session needed, but leverages its output if available.
ferdinandobons/startup-skill
Stars: 1.2kClaude CodeCodexMarket positioning strategy using the April Dunford framework, enriched with JTBD discovery, Moore positioning statement, and Neumeier's Onliness Test. Produces a complete positioning document, positioning statement, competitive alternatives map, and market category analysis. Use when the user wants to define or refine their market positioning, find their unique position, differentiate from competitors, craft a positioning statement, choose a market category, or figure out "how should we position this product." Triggers for "positioning", "how to position", "market position", "differentiation strategy", "positioning statement", "competitive positioning", "category strategy", "where do we fit in the market", "how are we different", "unique value proposition", or any request to define, sharpen, or rethink positioning. Works standalone — no prior startup-design or startup-competitors session needed, but leverages their output if available.
ferdinandobons/startup-skill
Stars: 1.2kClaude CodeCodexUse when reviewing current branch for bugs before pushing or merging, when wanting a thorough multi-agent review of local changes, or when preparing work for human review. Not for codebase structure, not for code style, and not for fixing what it finds.
Ovid/paad
Stars: 154Claude CodeCodexUse when reviewing current branch for bugs before pushing or merging, when wanting a thorough multi-agent review of local changes, or when preparing work for human review. Not for codebase structure, not for code style, and not for fixing what it finds.
Ovid/paad
Stars: 154Claude CodeCodexUse when reviewing current branch for bugs before pushing or merging, when wanting a thorough multi-agent review of local changes, or when preparing work for human review. Not for codebase structure, not for code style, and not for fixing what it finds.
Ovid/paad
Stars: 154Claude CodeCodex