yvanvds

Use after an issue's PR has been merged to wrap up the issue branch — close the issue, switch back to dev, fast-forward, and delete the local and remote feature branches. Triggers on phrases like "cleanup", "cleanup issue N", "wrap up <branch>", "post-merge cleanup", "I just merged the PR, clean up". Do NOT trigger before the PR is merged, on the `dev` or `master` branches themselves, or for cleanup of branches that were never linked to an issue (release-prep, sync PRs, etc.).

Use when fixing compiler warnings, static analyzer findings (clang-tidy, etc.), or runtime errors/crashes in the libYSE codebase. Enforces the project's performance-first stance: never trade audio-thread speed for stylistic cleanliness, never modify vendored dependencies, never broaden scope beyond the reported issues.

Use when the user asks to cut a new release of libYSE — phrases like "release a new version", "cut a patch/minor/major release", "publish a new release", "ship X.Y.Z". Orchestrates version bump, doc refresh, C API drift audit, dev→master promotion, and tag-driven publication via the existing release.yml workflow. Do NOT use for branch-management tasks unrelated to a release, or for republishing an already-tagged version (that's a workflow_dispatch on release.yml, not this skill).

Use when extending the C API at YseEngine/c_api/ — wrapping a new engine class, method, enum, or callback — or when auditing the C API for drift from the engine's public surface. Applies the project's RT-safety, ownership, and ABI conventions established in PRs

GitHub issue-driven workflow for this repo. Use it to (a) file a new issue as bug/feature/enhancement/question, (b) break an agreed implementation plan into a list of issues, (c) start work on an existing issue by creating a branch from dev, or (d) open a PR back to dev when the work is ready. Invoke proactively when you encounter work that is out-of-scope for the current task and should be tracked, or when the user agrees to a multi-step implementation plan. Also user-invocable as /issue.

Author and edit pedagogically sound curriculum goals for the AI Tutor (ai_tutor_python). Use this skill whenever the teacher wants to design a new goal, add subgoals or learning objectives (LOs), or revise an existing goal — including phrases like "let's design a goal on X", "add a goal for Y", "edit the loops goal", "draft LOs for this subgoal", or anything involving the JSON files under `goals/`. The skill enforces the curriculum data model, runs an LO authoring rubric, blocks prerequisite leakage, preserves LO id stability on edits, and regenerates the curriculum overview after every change.

Use this skill whenever an interactive component (quiz, timed viewer, comparator, annotator, or any other stateful widget) needs to be added to a course chapter in this Cursus Esthetica project. Triggers on phrases like "voeg een interactieve oefening toe", "integreer dit artifact", "bouw een widget voor hoofdstuk X", "maak hier een interactief element van voor de site", or when the user pastes a React/JSX prototype and asks for it to be integrated into a chapter. Also triggers when building a new interactive component from scratch for a chapter. Covers the two primary workflows (integrating a prototype and building from scratch), file structure, React-island setup, styling conventions, and MDX integration.