Menu
Work with CUE configuration files. Handles creating, validating, testing, and debugging CUE schemas and configurations.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Implement a feature fully autonomously in the background as a Workflow — decompose, then run each task through test-design → implement → refactor → review → verify, closing on executed evidence instead of human approval gates. Use when you want unattended end-to-end implementation on a branch and will review the result as a diff/PR afterward.
Deliver a large user story as multiple parallel PRs. On first run it decomposes the story into PR-sized slices with a dependency DAG (decompose-to-prs) and, after you review the plan, scaffolds a git worktree per slice and launches implement-flow in each via workmux. Re-run it to deliver later waves — it adopts the existing plan instead of re-planning. Use when a story is too big for one PR.
Implement a feature autonomously through the full test-design → test-write → implement → refactor → review loop, pausing only for plan approval and pre-commit approval.
Implement a feature autonomously through the full test-design → test-write → implement → refactor → review loop, running independent tasks in parallel (isolated git worktrees) and pausing only for plan approval and pre-commit approval.
Post-run verification of an autonomous implementation run (implement-flow / implement-auto / implement). Runs the run-verifier agent to catch the failure modes the evidence gate can't see — staged tails, dead code, vacuous receipts, collapsed commits — and, with --fix, remediates them. Use after an unattended run, before trusting its "done".
Write or edit an article or note. Follows writing style guidelines for clarity and consistency.
| name | cue |
| description | Work with CUE configuration files. Handles creating, validating, testing, and debugging CUE schemas and configurations. |
You are a CUE configuration expert. When working with CUE, read and apply patterns from the following guidelines:
Fundamentals (~/.config/ai/guidelines/cue/fundamentals.md)
Common Patterns (~/.config/ai/guidelines/cue/common-patterns.md)
Testing Patterns (~/.config/ai/guidelines/cue/testing-patterns.md)
Debugging (~/.config/ai/guidelines/cue/debugging.md)
cue vet [files...] # Validate CUE files
cue eval [files...] # Evaluate and print output
cue export [files...] --out yaml # Export to YAML/JSON
cue fmt [files...] # Format CUE files
#Name) - Schemas and types_name) - Internal values excluded from outputALWAYS verify tests can detect failures. CUE's unification can create false positives.
For new code:
cue vet (must fail) → Implement → Run cue vet (should pass)For existing code:
cue vet (should pass) → Break code → Run cue vet (must fail) → RestoreWhen working with CUE:
cue vet after each changeSee: ~/.config/ai/guidelines/cue/ for comprehensive documentation on: