gh-project-workflow
End-to-end GitHub execution workflow for project delivery: create project items, assign available single-select fields (such as Status and optional Area), convert draft items to issues when needed, create and check out development branches via `gh issue develop`, then commit, push, create/merge pull requests, and run deployment commands on request. Use when the user explicitly asks to operate GitHub issue/PR lifecycle, or when another repo workflow skill delegates the GitHub tracking and delivery steps to it.
learning-app-cdp
Inspect or debug the learning app in a real browser through the project-specific Windows Chrome CDP workflow. Prefer this skill for browser testing, browser debugging, console inspection, network capture, DOM/runtime inspection, and service-worker-aware refreshes against http://sprecha.localhost or https://sprecha.de. Commands: doctor, start-local/start-prod (launches Chrome with the debug port — use this when Chrome is down, never launch chrome.exe by hand), refresh-*, wait-* (--path/--selector), eval-* (--expression/--file), console-*, monitor-*, read, clear, stop.
learning-app-remote-inspect
Step-by-step debugging workflow for the learning app through a phone's Chrome remote-inspect target. Use when the user has `chrome://inspect/#devices` open and wants a copy-paste command loop for Console/Elements/Network instead of direct automation.
openspec-propose-change
Start a new OpenSpec change and create the first ready artifact for it. Use this when the user wants to propose a feature, fix, or structured change in this repository using the repo's OpenSpec workflow, or when a newly reported repo bug/feature is being translated into tracked work.
repo-task-delivery
Use this when the user reports any problem, regression, warning, bug, improvement, or proposed repo change that is likely to result in a committed repository edit. Default to the full repo workflow: GitHub issue/project tracking, OpenSpec change, implementation, verification, pull request, merge, and closeout.