openspec-bulk-archive-change
Archive multiple completed changes at once. Use when archiving several parallel changes.
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-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-onboard
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
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.
jira
|
opencode-authoring
|
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.
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.
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.
blueprint
>-
AllRecursiveReposClean
Check if all git repositories in subdirectories are fully committed to main/master with no pending changes or worktrees.
RemoteFactory
|
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.
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.
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.
knockoff
>-
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
issue-management
Use when tasked with working on an issue from an issues/ directory, especially when asked to "work on an issue", "work on the next issue", or "continue working"
go-style-guide
Google Go Style Guide for writing clear, idiomatic, and maintainable Go code. Use this skill when writing, reviewing, or refactoring Go code to ensure adherence to Google's best practices. Triggers on tasks involving Go packages, functions, error handling, naming, or performance optimization.
development-workflow
Use when starting work on features, bugs, or significant changes requiring multiple commits and coordination of design, implementation, testing, and documentation
ticket-breakdown
Use when asked to break down a ticket or feature specification into smaller implementable issues for independent completion by agents
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
product-vision-document
Use when creating product vision documents, product strategy docs, or communicating product ideas to non-technical stakeholders like investors, executives, or cross-functional teams
technical-design-document
Use when designing complex technical features requiring cross-team coordination, system architecture decisions, data model changes, API definitions, or when stakeholders need comprehensive technical documentation before implementation
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
design-compare
Use when comparing a frontend implementation against a reference design (Figma, mockup, screenshot). Performs pixel-level and structural analysis to identify discrepancies.
design-audit
Use when reviewing frontend design quality without a reference. Identifies UX issues, accessibility problems, and visual inconsistencies with actionable fix suggestions.
design-report
Use when conducting comprehensive design review before launch, for stakeholder presentation, or when user requests expert-level design analysis. Produces detailed report from senior Apple product designer perspective.
test-execution-manager
Use when running tests via test-runner subagents - delegates test execution to background agents with incremental timeout escalation
frontend-styleguide
Use when asked to create or edit style guides, design systems, component libraries, or update existing frontend components for web projects
plone-frontend-developer
Senior Plone Volto frontend engineering for debugging Volto add-ons, fixing UI bugs, adjusting blocks/components, and handling all Plone 6.1 + Volto 17 frontend tasks (theme, routing, tokens, build/test issues). Use when the request involves Volto/Plone frontend behavior, add-on code, or UI fixes.
plone-backend-developer
Senior Plone backend development for the EEA website. Use when working on Plone 6.1 server behavior, backend add-ons, Python code, configuration in `backend/develop/`, or when debugging backend bugs and tests.
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.
test-writer
|
topic-manager
Expert assistant for managing biblical topics in the KR92 Bible Voice project. Use when (1) creating/editing topics and their Finnish translations, (2) managing topic relations (related, opposite, broader, narrower), (3) validating Finnish translations and pronunciations with Voikko/Omorfi, (4) reviewing topics marked with qa_status='unchecked', (5) bulk updating topic translations, (6) managing topic aliases and synonyms, or (7) fixing incorrectly translated Finnish topic names.
translation-sync
Expert assistant for managing Finnish/English content translations in the KR92 Bible Voice project. Use when syncing topic translations, managing translation cache, validating translation completeness, or importing/exporting CSV translations.
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
widget-tester
Expert assistant for testing the embeddable Bible widget functionality in the KR92 Bible Voice project. Use when creating widget tests, validating embed API responses, testing reference formats, checking audio integration, or creating regression test cases.
monorepo-guide
Guide for working with the Raamattu Nyt monorepo structure. Use when creating new packages, adding apps, managing workspace dependencies, understanding import patterns, or troubleshooting monorepo issues. Covers npm workspaces, shared packages, cross-app code sharing, and Lovable Cloud deployment.
onboarding-architect
>
opi
|
performance-auditor
Expert assistant for monitoring and optimizing performance in the KR92 Bible Voice project. Use when analyzing query performance, optimizing database indexes, reviewing React Query caching, monitoring AI call costs, or identifying N+1 queries. Helps diagnose slow operations across database, frontend, and AI systems.
practice-gamification
>
product-manager-toolkit
Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.
questions-answers
Expert assistant for the Questions & Answers (Q&A) system in Raamattu Nyt. Develop, debug, and extend the full pipeline from search query classification through question upsert, AI answer generation, community answers, voting, admin moderation, and anchor questions. Use when (1) adding features to Q&A search results, (2) modifying question classification logic, (3) working on community answer forms or moderation, (4) changing AI answer generation or prompts, (5) editing admin Q&A management pages, (6) working with anchor questions or similar questions, (7) modifying votes/upvotes/downvotes, (8) fixing Q&A-related bugs, (9) extending answer types or display, (10) working on QuestionPage, QuestionsSearchSection, or AdminQuestionsPage.
react-package-builder
|
reading-plan-designer
|
Page 1473 of 1487 · 74319 results
