@kazani: Opus 4.5 + GLM 4.7 prompt for vibe-coding with plan-first workflow

This is a system-style prompt for coding assistants (shared as tuned for Opus 4.5 and GLM 4.7) that sets a plan-first workflow for vibe-coding. The assistant must give a detailed implementation plan covering steps, files, risks, testing and impact, and must not output code until the user explicitly approves. The prompt also requires modular, Domain-Driven Design structure, heavy documentation answering where, what, how and why, and a closing question asking whether any questions remain. It further asks for a self-review "deslop" pass after generating code, plus linting and type checks, and leaves project-specific details such as language, test framework and build commands as bracketed placeholders for the user to fill in.