vibe-coding-yaml

Generate YAML descriptors for auditable, deterministic code generation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/dredd-us/seashells --skill vibe-coding-yaml-dredd-us
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibe-coding-yaml
Source: https://github.com/dredd-us/seashells/tree/main/.claude/skills/vibe-coding-yaml
Command: npx skills add https://github.com/dredd-us/seashells --skill vibe-coding-yaml-dredd-us

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures 100% auditable and deterministic code generation by having the AI output YAML descriptors instead of direct code. A CLI then executes these descriptors, eliminating "slop" and making generated code reviewable.

Core Features & Use Cases

  • Auditable Generation: Review concise YAML descriptors, not complex generated code, for full transparency.
  • Deterministic Execution: Guarantees the same YAML input always produces the exact same code output.
  • Use Case: Generate a UI component like a button. The AI outputs a YAML descriptor for the button's properties and styles. This YAML is then executed by a CLI to produce the final Button.tsx file, which is fully traceable and reproducible.

Quick Start

Use the vibe-coding-yaml skill to generate a YAML descriptor for a new API endpoint that creates users.

Frequently Asked Questions about vibe-coding-yaml

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate auditable code instead of dealing with code generation slop?

Auditable code generation uses YAML descriptors as an intermediate representation instead of direct code output. The AI writes concise YAML defining the code's structure and properties, then a CLI executes it to produce the final code, ensuring 100% transparency and reviewability with zero ambiguity.

What's the difference between YAML-based code generation and standard code generation?

YAML-based generation separates intent from execution: you review simple YAML descriptors before any code is produced, making changes traceable and reproducible. Standard generation outputs code directly, making it harder to audit and modify. YAML ensures deterministic, identical output every time the same descriptor runs.

Can I use YAML descriptors for infrastructure as code and UI components?

Yes. YAML descriptors work across infrastructure as code, UI components, and compliance-driven tasks. A single descriptor format generates consistent, auditable outputs whether you're defining an API endpoint, a React component, or infrastructure configuration, with full Git versioning and reproducibility.

How do I ensure generated code is reproducible and reviewable in my workflow?

YAML descriptors guarantee reproducibility: the same input always produces identical output. Version descriptors in Git, review them like configuration files before execution, then generate code deterministically through the CLI. This workflow enables code review at the intent level, not the generated output level.

Do I need existing code generation tools to use YAML descriptors for auditable output?

No. YAML descriptors replace traditional code generation entirely. You define outputs in YAML, the CLI executes the descriptor, and you get auditable, deterministic code. This eliminates dependency on opaque code generators and gives you full control over what code is produced and why.

What happens if the same YAML descriptor is executed multiple times?

Deterministic execution guarantees identical output every run. The same YAML descriptor always generates the exact same code file, with no variation. This ensures consistency across environments, makes debugging predictable, and enables reliable automation in CI/CD and compliance workflows.