navigating-github-to-konflux-pipelines
Use when GitHub PR or branch has failing checks and you need to find Konflux pipeline information (cluster, namespace, PipelineRun name). Teaches gh CLI commands to identify Konflux checks (filter out Prow/SonarCloud), extract PipelineRun URLs from builds and integration tests, and parse URLs for kubectl debugging.
working-with-provenance
Use when tracing Konflux builds from image references, finding build logs from artifacts, or verifying source commits for container images - extracts provenance attestations to navigate from images back to builds and source code
debugging-pipeline-failures
Use when Konflux pipelines fail, are stuck, timeout, or show errors like ImagePullBackOff. Covers PipelineRun failures, TaskRun issues (Pending, Failed, stuck Running), build errors, and systematic debugging of Tekton pipeline problems using kubectl and logs.
understanding-konflux-resources
Use when user asks about Konflux resources, Custom Resources, Applications, Components, Snapshots, IntegrationTestScenarios, ReleasePlans, ReleasePlanAdmissions, or namespace placement. Provides quick reference for what Konflux resources are, who creates them, and where they belong (tenant vs managed namespace).
browser-automation
Enterprise-grade browser automation using WebDriver protocol. Use when the user needs to automate web browsers, perform web scraping, test web applications, fill forms, take screenshots, monitor performance, or execute multi-step browser workflows. Supports Chrome, Firefox, and Edge with connection pooling and health management.
creating-plugins
Scaffolds a new Claude Code plugin with proper structure. Use when creating a new plugin package with skills and manifests.
writing-subagents
Use when creating specialized Claude Code subagents in .claude/agents/. Use when user says "create agent", "add reviewer", "specialized agent", "isolated context task".
writing-skills
Use when creating new skills, modifying existing skills, or improving skill quality. Use when user says "create a skill", "write a skill", "add capability". Use when a repeated pattern should become reusable.
migrating-agent-systems
Use when setting up or migrating Claude Code agent system for a project. Use when user says "setup agent", "migrate agent system", "configure claude code", "add agent system".
writing-rules
Use when creating rule files in .claude/rules/, adding project conventions, or scoping guidelines to specific paths. Use when user says "add rule", "create convention", "scope guideline". NOT for laws (use <law> in CLAUDE.md).
writing-hooks
Use when creating Claude Code hooks for code quality, static analysis, or workflow automation. Use when user says "add hook", "enforce linting", "add pre-commit check", "block bad code".
initializing-projects
Use when bootstrapping a new project from scratch. Use when user says "create project", "new project", "initialize project", "start new app".
improving-skills
Use when optimizing an existing skill. Use when user says "improve skill", "optimize skill", "update skill", "skill needs work". Use when a skill is outdated or underperforming.
writing-claude-md
Use when creating CLAUDE.md, improving existing CLAUDE.md, or setting up project configuration. Use when user says "create CLAUDE.md", "setup project", "add laws", "configure agent".
reflecting
Use when completing significant work to extract learnings. Use when user says "reflect", "what did we learn", "capture learnings". Use after resolving complex problems or discovering patterns.
writing-plugins
Creates complete Claude Code plugin packages with manifests, agents, skills, hooks, and marketplaces following official schema. Use when creating new plugins, building marketplaces, or packaging skills for distribution.
refactoring-skills
Use when analyzing and refactoring skills in a project. Use when user says "refactor skills", "cleanup skills", "consolidate skills", "skill review". Use when skills are messy or overlapping.
c3-query
|
c3-sweep
|
c3-onboard
|
c3-ref
|
c3-change
|
c3-audit
|
debug-visual-regression
Analyze visual regression test failures in Vizzly. Use when the user mentions failing visual tests, screenshot differences, visual bugs, diffs, or asks to debug/investigate/analyze visual changes.
visual-testing-philosophy
Visual testing best practices and philosophy. Use when the user is adding visual tests, writing test code, deciding where to add screenshots, or asking about screenshot best practices.
vizzly-knowledge
Core knowledge about Vizzly visual testing - file structure, CLI commands, and how it works. Use when working with Vizzly, running visual tests, or helping with screenshot-related tasks.
check-visual-tests
Check the status of Vizzly visual regression tests. Use when the user asks about test status, test results, what's failing, how tests are doing, or wants a summary of visual tests.
vendure
Assiste au développement avec le framework e-commerce Vendure pour Node.js. Gère le commerce headless, les APIs GraphQL, la gestion des commandes, les catalogues produits, l'intégration des paiements et le développement TypeScript e-commerce. Utiliser lors du travail sur des projets Vendure, la création de plugins, ou l'intégration de storefronts.
dart-pub
To run Dart or Flutter pub commands like `pub get` or `pub add`, execute a pub command for the given roots.
dart-hover
To view hover details such as docs and types at a cursor position, get hover information for a file location.
dart-pub-dev-search
To search pub.dev for relevant Dart packages, query by keywords and return download counts, topics, license, and publisher.
dart-hot-reload
To apply latest code changes to a running Flutter app, trigger hot reload after connecting to the Dart Tooling Daemon.
dart-remove-roots
To remove previously registered Dart project roots, revoke tool access by removing those roots.
dart-resolve-workspace-symbol
To search for symbols across Dart workspaces, resolve a symbol name to find definitions or catch spelling errors.
dart-run-tests
To run Dart or Flutter tests with the agent-centric test runner, execute tests using this tool instead of shell `dart test` or `flutter test`.
dart-set-widget-selection-mode
To enable or disable widget selection mode in a running Flutter app, set selection mode after connecting to the Dart Tooling Daemon.
dart-signature-help
To see function or method signatures at a cursor position, get signature help for the API being called.
playwright-browser-click
To click a page element in the browser, perform a click on buttons, links, or controls during Playwright automation.
playwright-browser-close
To close the current Playwright page, close the page to end the session or free resources.
playwright-browser-console-messages
To read console logs from the current page, retrieve console messages for debugging JavaScript output.
playwright-browser-drag
To drag and drop between elements on a web page, perform a drag interaction from a source to a target.
playwright-browser-evaluate
To run JavaScript in the page context, evaluate an expression on the page or a specific element for inspection or manipulation.
dart-get-runtime-errors
To read recent runtime errors from a running Dart or Flutter app, fetch runtime errors after connecting to the Dart Tooling Daemon.
dart-get-selected-widget
To find the currently selected Flutter widget in the running app, get the selected widget after connecting to the Dart Tooling Daemon.
dart-get-widget-tree
To inspect the Flutter widget tree of the running app, retrieve the widget hierarchy after connecting to the Dart Tooling Daemon.
dev-swarm-stage-architecture
Design the complete system architecture including components, data flow, infrastructure, database schema, and API design. Use when starting stage 07 (architecture) or when user asks about system design, tech stack, or database schema.
dev-swarm-stage-tech-research
Validate technical feasibility through proof of concepts, technology spikes, and prototypes before committing to full development. Use when starting stage 04 (tech-research) or when user asks to validate technical assumptions or create PoCs.
dev-swarm-stage-archive
Archive the current project so the repo is ready for a brand-new project start from ideas.md. Use when user asks to archive the project or start a new project from ideas.md.
dev-swarm-stage-deployment
Deploy to production, configure infrastructure, set up monitoring, and prepare for launch. Use when starting stage 11 (deployment) or when user asks to deploy, go-live, or launch the product.
dev-swarm-stage-devops
Set up DevOps infrastructure including GitHub repositories, CI/CD pipelines, containerization, and cloud infrastructure (AWS, RunPod). Use when starting stage 09 (devops) or when user asks about CI/CD, Docker, or cloud setup.
Page 1147 of 1635 · 81729 results
