Build software with prompts as the durable source of truth. This extension provides first‑class editing for .prompt files—clear syntax highlighting and editor behaviors—so requirements stay human‑readable while code becomes a regenerable artifact.
Why this matters: AI agents can draft code in seconds, but teams often spend hours repairing breakage and drift. Instead of treating prompts as one‑off instructions, PDD formalizes the prompt as the canonical spec. You iterate on the prompt; the system regenerates code deterministically and safely.
Features
Syntax highlighting for .prompt files
Language configuration for predictable editing (comments, brackets)
Spec-driven aims for spec → code. PDD inserts an explicit engineering layer: spec → prompts → code. Developers refine the partitioning into a suite of precise, version-controlled prompts (easier to tune than partitioning code), then regenerate artifacts deterministically.
Vibe coding is ad‑hoc prompting and auto‑accepting of code patches. It is like throwing a grenade in the codebase: you never know what will be changed, deleted or duplicated. In contrast, PDD couples every prompt with automated validation; generated code is accepted only if tests pass. No surprise changes—reviewable diffs and test‑gated merges.
PDD is built for real projects: modular prompts, few‑shot context reuse, and regeneration that reduces drift. The whitepaper documents measurable benefits and benchmarks on non‑toy codebases.
