>-

hologres-query-optimizer

Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.

'Use this when: (1) Creating a new project-specific skill to document project patterns, (2) Improving or updating an existing project skill, (3) Writing skill descriptions that will trigger other agents, (4) Organizing skill content for progressive disclosure, or (5) Learning what project-specific skills exist in .claude/skills/. Ensures skills follow project conventions and provide effective progressive disclosure.'

A multi-stage validation pipeline that turns unreliable LLM code generation into reliable, compilable code.

Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.

Create a layered CSS progressive blur (top or bottom) using multiple backdrop-filter masks for depth and softness. Use when asked for “progressive blur”, “gradient blur overlay”, or stepped blur masks that fade from an edge of the viewport.

Autonomously diagnose Magento 2 indexer issues, fix invalid or stuck indexers, and scaffold custom indexers from a spec — reads indexer state, mview changelog, and DB schema to produce a concrete fix or implementation plan.

Improve skills and workflows by analyzing run artifacts and execution logs (events.jsonl/state.json) under runs/ (or OpenSpec changes/). Use when you want to iterate on skills based on real runs: find failure modes, bottlenecks, unclear prompts, missing I/O contracts, and propose concrete edits.

Run accessibility and visual design review

Introspection & Querying: describe/list commands, config filtering, workspace introspection, dependency graphs, YQ integration

Autonomously diagnose Magento 2 cache issues — FPC bypass, Redis pressure, stale blocks, and invalidation failures — and scaffold custom cache types. Produces a Cache Report with root cause and fix.

Database operations for Supabase: query/write/migration/logs/type generation. Triggers: query/statistics/export/insert/update/delete/fix/backfill/migrate/logs/alerts/type generation. Does not trigger for: pure architecture discussion or code planning. Write operations require confirmation; UPDATE/DELETE without WHERE is refused. MCP is optional — works with CLI/Console too.

Create or refactor Ship Faster-style skills (SKILL.md + references/ + scripts/). Use when adding a new skill, tightening trigger descriptions, splitting long docs into references, defining artifact-first I/O contracts, or packaging/validating a skill.

Conduct structured implementation postmortems to gather feedback on architecture conformance, library friction, and tooling effectiveness. Use when reviewing completed implementations, PRs, or development phases to surface design gaps, boundary violations, and improvement opportunities. Triggers on requests for code review feedback, implementation retrospectives, architecture audits, or library/tooling evaluations.

<!--

go-test-coverage

Skill for ALL joke requests

Connect your local machine to a Kubernetes cluster for local development with Signadot — local connect, proxy, traffic override, and traffic recording/inspection. Use when a developer wants to run services locally that participate in cluster traffic, or record/inspect sandbox traffic.

>

Autonomously review Magento 2 module code against coding standards, architectural rules, and security requirements. Produces a severity-rated findings report.

**Purpose:** Execute multi-step workflows in a single transaction.

Use when deciding the next sparse-ir-rs release version or checking whether a change set should be patch, minor, or major under Semantic Versioning

GH CLI workflow: (1) snapshot zmian z PR/brancha, (2) review PR z mapą ryzyk bez publikowania komentarzy, (3) inteligentny port zmian na inny branch (bez cherry-pick jako default).

Comprehensive guide for creating high-quality specialized agents following v2 architecture patterns. Use this skill when users need to design and implement new agents, understand agent architecture, or learn best practices for agent creation.

Writing mirror. Run terminal commands to launch, then reflect.

Use the Moneta CLI to recall project knowledge and remember

Evaluate cross-framework parity for generated components and accessibility metadata. Use when emitter behavior changes or parity regressions are suspected.

Run the reviewer sub-agent for code review

Build and review frontend with accessibility, design constraints, and Vercel guidelines

Write commit messages to a temporary file and commit with `git commit -F`. Never use `git commit -m`.

Review UI code for Vercel Web Interface Guidelines compliance

Automate browser interactions via the Playwright CLI. Use for web testing, form filling, screenshots, UI verification, and data extraction.

Code reviews of git changes without creating actual PR.

Project configuration: atmos.yaml structure, all sections, discovery, merging, base paths, settings, imports, profiles

Component architecture: Terraform root modules, abstract components, component inheritance, versioning, mixins, catalog patterns

Packer orchestration: init/build/validate/inspect/output, machine image building, template management, source management

>

Unified codebase quality review: merge readiness verdict + maintainability (Clean Code) + docs-vs-code consistency. Use for code review, quality check, refactor check, outdated docs check, or merge/production readiness.

Global evolution system for ship-faster skills. Uses hooks to capture context, failures, and session summaries, then generates patch suggestions (no auto edits) via skill-improver. Use when you want the skills to self-improve safely and continuously.

Create workflow-* skills by composing existing skills into end-to-end chains. Turns a user idea into a workflow_spec.md SSOT (via workflow-brainstorm), discovers available skills locally + from skills.sh, and generates a new workflow-<slug>/ skill package. Use when you want to design a new workflow, chain multiple skills into a flow, or turn scattered atomic skills into a resumable plan-then-confirm workflow.

Enforces ESLint, Prettier, and TypeScript compiler checks from the frontend package.json for JavaScript and TypeScript source. Use when creating or editing .js, .jsx, .ts, or .tsx files under fe/, when generating React or Vite frontend code in this repo, or when the user asks for lint-, format-, or tsc-compliant frontend changes.

Workflow orchestration, sub-agent architecture, and task management patterns

Execute framework-specific implementation jobs from job bundles (`prompt.md`, `ir.json`, `artifact.json`) and validate outputs package-by-package.

Generate pull request summaries and open GitHub PRs from the current branch’s git changes.

This skill follows the principle of **progressive disclosure**:

Build or modify a Pi extension. Use this whenever the user wants a custom slash command, extension tool, lifecycle hook, context filtering, session persistence, UI prompt, model/provider integration, or anything placed in ~/.pi/agent/extensions/. This skill is especially relevant when the user says “create a pi extension”, mentions /reload, wants custom command behavior, or needs extension code that uses Pi APIs rather than app code.

>

>

Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.