frontend-design-system
>
agent-coordination
Coordinate multiple agents for software development across any language. Use for parallel execution of independent tasks, sequential chains with dependencies, swarm analysis from multiple perspectives, or iterative refinement loops. Handles Python, JavaScript, Java, Go, Rust, C#, and other languages.
ecto-query-analysis
Analyzes Ecto queries for N+1 problems, missing preloads, and performance issues.
data-pipeline
GenStage, Broadway, and Flow for Elixir data pipelines
test-generation
Generates comprehensive Elixir tests using ExUnit following TDD principles.
security-patterns
Elixir-specific security patterns, OWASP mitigations, and compliance best practices
performance-profiling
Performance profiling and optimization for Elixir/BEAM applications
otp-patterns
Implements OTP design patterns including GenServer, Supervisor, and Application behaviors.
observability
Telemetry, metrics, tracing, and observability for Elixir/BEAM applications
git-workflow
Git and GitHub workflow automation skills for OpenCode agents
nx-patterns
Nx and Livebook patterns for machine learning in Elixir
elixir-architect
Use when designing or architecting Elixir/Phoenix applications, creating comprehensive project documentation, planning OTP supervision trees, defining domain models with Ash Framework, structuring multi-app projects with path-based dependencies, or preparing handoff documentation for Director/Implementor AI collaboration
graphql-patterns
GraphQL patterns with Absinthe framework for Elixir/Phoenix applications
elixir-scribe
Single Responsibility Code in Self-Documented Folder Structure
nerves-patterns
Nerves embedded development patterns for Elixir/Nerves systems
liveview-patterns
Phoenix LiveView UI and real-time feature patterns
migration-patterns
Zero-downtime Elixir/Phoenix database migrations and rollback strategies
distributed-systems
Distributed systems patterns for BEAM/OTP including clustering, supervision, and multi-region deployment
ai-orchestration
LLM keyring management, multi-provider support, and AI agent orchestration
containerization
Docker and Kubernetes deployment patterns for Elixir/Phoenix applications
api-design
REST vs GraphQL, API versioning, rate limiting, and documentation for Elixir/BEAM APIs
elixir-guidelines
Official Elixir community standards, naming conventions, and best practices
api-versioning
API versioning strategies including URL-based, header-based, and breaking change management
resilience-patterns
Resilience and error recovery patterns including circuit breaker, retry strategies, and graceful degradation
measuring-pr-performance-impact
Measures GraphQL resolver latency changes before/after a PR merge using Datadog metrics. Use when analyzing PR performance impact, measuring latency changes, or comparing resolver performance before and after a code change.
openspec-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
openspec-verify-change
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
openspec-sync-specs
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
openspec-onboard
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
openspec-new-change
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
openspec-ff-change
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
openspec-continue-change
Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.
openspec-bulk-archive-change
Archive multiple completed changes at once. Use when archiving several parallel changes.
jira-cli
Interactive command-line tool for Atlassian Jira. This skill should be used when users want to interact with Jira issues, epics, sprints, or when they mention Jira workflows, issue management, or need help with jira-cli commands and workflows.
invoicing
Interact with the Eenvoudig Factureren API to manage clients, invoices, quotes, orders, and more. Use me when dealing with invoicing, clients, quotes, orders, deliveries, receipts, payments, stock items, or subscriptions.
skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
shell-scripting
Guide for writing robust shell scripts following best practices to use bash with proper options, quote variables, use modern syntax, include debugging support, and provide help.
opencode-authoring
|
jira
|
blueprint
>-
knockoff
>-
project-todos
This skill should be used when the user asks to "create a todo", "add a plan", "plan this work", "track this work", "document this task", "complete a todo", "verify the implementation", "run architect verification", "hand off to the developer", "start the implementation", "update docs for this feature", "what's the next step", "what's the plan status", "resume the todo", "what's blocked", "pick up where we left off", "design this feature", "check business requirements", "review requirements", "review against requirements", "check for requirement conflicts", or mentions managing project todos, plans, and multi-agent workflows. Provides the structured workflow for creating, managing, and linking todo/plan files, and orchestrating agent collaboration through the full design-review-implement-verify-document lifecycle.
RemoteFactory
|
AllRecursiveReposClean
Check if all git repositories in subdirectories are fully committed to main/master with no pending changes or worktrees.
ui-todos
This skill should be used when the user asks to "create a ui todo", "add a ui task", "track ui work", "ui change needed", "fix the UI layout", "match the legacy screen", "build a UI component", "ui implementation workflow", "visual fix", "CSS fix", "fix the page layout", "style the page", "make it look like the legacy screen", "ui what's next", "resume ui work", "launch ui agent", "delegate UI work to agent", or describes UI/visual/layout changes that need structured agent-driven tracking. Manages the full lifecycle of UI work items where all source code changes are made exclusively by agents. Use this skill instead of project-todos when work is primarily visual. When ambiguous, prefer this skill if the work centers on page presentation, components, or CSS.
Neatoo
This skill should be used when working with Neatoo domain models, ValidateBase, EntityBase, ValidateListBase, EntityListBase, partial properties, property change tracking, validation rules, business rules, aggregate roots, entities, value objects, lazy loading, LazyLoad, ILazyLoadFactory, or any .NET DDD domain model framework work. Also triggers for IsValid, IsSelfValid, IsSavable, IsModified, IsNew, IsDeleted, RuleManager, AddActionAsync, AddValidationAsync, AddAction, AddValidation, IsBusy, WaitForTasks, IsLoaded, IsLoading, and base class behavior. This skill also provides guidance on where business logic belongs -- computed properties, conditional visibility, reactive behavior, and validation should live in the domain model (not the UI). Consult this skill when writing .razor files that bind to Neatoo entities to ensure logic stays in the domain layer. For factory attributes ([Factory], [Create], [Fetch], [Remote], [Service], [AuthorizeFactory]) see the RemoteFactory skill.
development-workflow
Use when starting work on features, bugs, or significant changes requiring multiple commits and coordination of design, implementation, testing, and documentation
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Page 1529 of 1543 · 77148 results
