Vibe Coding 最佳实践
Best practices Strong first use : Context and Prompts Clear prompting makes results more reliable A good default is to include four things in your prompt: Goal: What are you trying to change or build? Context: Which files, folders, docs, examples, or errors matter for this task? You can @ mention certain files as context. Constraints: What standards, architecture, safety requirements, or conventions should Codex follow? Done when: What should be true before the task is complete, such as tests passing, behavior changing, or a bug no longer reproducing? it is similar to Claude Code Best practices ...
Vibe Coding