JPEGtheDev

Use when adding new classes, refactoring code, or reviewing PRs for Particle-Viewer.

Use when a task needs design exploration before any implementation begins. Required for any task with unclear approach, significant architecture impact, or multiple valid solutions.

Use when building, adding dependencies, configuring CMake options, troubleshooting build failures, or managing Flatpak packaging for Particle-Viewer.

Use when writing or reviewing C++ code, running pre-commit checks, or addressing formatting, naming, or static analysis violations.

Use when writing tests for any interface, abstract base class, or type with multiple implementations.

Use when implementing C++ code for Particle-Viewer, handling GL resources, working with SDL3, or applying DRY/deprecation/docs-commit patterns.

Use when writing or reviewing any C++ class that owns resources, has a destructor, or acquires in a constructor.

Use when multiple independent read-only research tasks can run simultaneously, or when you need to fan out investigation across many files or hypotheses.

Use when multiple independent read-only research tasks can run simultaneously, or when you need to fan out investigation across many files or hypotheses.

Use when communication quality or trust is in question. Always active -- applies to every session, every turn, every task.

Use when completing any session.

Use when a completed session needs behavioral retrospective analysis.

Use when delegating implementation tasks, confirming theories, running parallel research, or reviewing completed work.

Use when running parallel agent work, testing an approach in isolation, or keeping the main branch clean while a subagent operates on a separate branch.

Use when a feature has new or unclear acceptance criteria, a plan has 2+ todos and Discovery ran, or an implementer signals BLOCKED or DONE_WITH_CONCERNS.

Use when creating or refining Independent, Negotiable, Valuable, Estimable, Small, Testable (INVEST)-aligned user stories.

How to format and structure a recipe YAML file in the OpenCookbook repository. Use this skill when writing, editing, or reviewing any recipe file. Covers every field, unit rule, and file convention.

How to read, write, and extend GitHub Actions workflows in OpenCookbook. Covers the existing deploy-pages workflow, conventions for new workflows, and patterns for dotnet builds, PR checks, and preview deployments.

Autonomous execution protocol for implementing tasks. Governs planning, iteration, subagent use, verification, and self-correction. Use when executing any non-trivial implementation work — recipe edits, code changes, CI/CD updates, or multi-step tasks.

End-of-session self-evaluation for continuous improvement. Run before finalizing any session to capture lessons learned, identify skill updates, and improve agent effectiveness. Use when completing a task, reviewing work quality, or improving project skills.

Checklist for validating an OpenCookbook recipe. Use when reviewing a recipe before promotion, after edits, or for quality checking. Fix everything you can. Only flag issues that need the author's judgment.

Data model and layout specification for rendering OpenCookbook recipes on a webpage or as a PDF. Defines how YAML recipe data maps to visual output. Language-agnostic - covers data structure and layout intent, not implementation.

How to fill in the PULL_REQUEST_TEMPLATE.md when creating or updating a PR in OpenCookbook. Covers the PR Title Check, description, type of change, checklist generation, and related issues.

Versioning rules for OpenCookbook recipes using conventional commits. Defines when and how to bump the version field in a recipe YAML file, and how to format commit messages for recipe changes.