Create or reformat a GitHub issue on kymostudio/kymostudio via the `gh` CLI. Picks the matching `.github/ISSUE_TEMPLATE` form (bug_report / feature_request), mirrors its fields into the body, sets the org Issue Type (Feature for feature_request) and auto-applies `#`-prefixed area labels from the existing repo labels. Use when the user says "tạo issue", "create issue", "mở issue", "open issue", "report bug", or asks to reformat an existing issue for this repo.
Fix a red "Format & clippy" (rust.yml) CI job on kymostudio — auto-apply cargo fmt, verify the exact CI lint gate goes green, and ship the fix. Use when a Rust core CI run fails on the rustfmt or clippy step, or to pre-empt one before pushing Rust changes. Formatting is deterministic and non-semantic, so the fmt fix is safe to auto-apply; clippy failures are surfaced, not blindly rewritten.
Reconcile kymostudio's golden/baseline fixtures after an INTENTIONAL renderer, layout, or grammar change — classify each failing gate as intended vs a real regression, regenerate only the right tier, then prove parity held. Use when golden SVG tests, the BPMN corpus baseline, or the conformance suite fail because you deliberately changed output. Do NOT use to silence an unexplained red test.
Check or close Python↔JS feature parity in kymostudio via the conformance suite. Use when adding a feature to one impl (Python or JS) that the other needs, when a JS conformance test diverges from Python's golden, or to confirm a new behavior is locked in both languages. Encodes the rule that Python is the reference impl and JS reconciles toward it.
Run kymostudio's verifiable stop condition — Python pytest + JS conformance parity — and report a clear PASS/FAIL with the failing output. Use as the goal check for any /loop or /goal on this repo, or to confirm a change is green before committing. Trigger phrases - "is it green", "verify the build", "check parity", "did the change break anything".
Design an autonomous agent loop for the kymostudio repo — pick a verifiable goal contract, wire trigger/actions/verification/memory, and pick a safe maturity level. Use when the user wants to automate recurring work here ("automate X", "set up a loop", "run this nightly", "keep checking Y"), or before writing a /loop, /goal, or .claude/workflows script. Loop engineering = designing the system that prompts the agent, not prompting by hand.