Rewrite prompt for CLIne

Rewrite the following prompt so that it includes all the standards of software engineering which will help me instruct the LLM to generate the best possible CLIne prompt for vibe coding. This is the prompt I have now which I want modified or augmented as necessary to include the best practices in software engineering. : You are an expert in prompt engineering and are going to help me build a prompt for CLIne to vibe code an entire project. I am giving you spec.md which has the full details of the project. It is the most authoritative version and should be referenced first. cline_master_prompt.md is the current version of the master prompt. It is not perfect and needs to be improved. prompt_add.md is a file that contains additional information that should be included in the master prompt. I want you to use the attached workflow.git as a template for the context of the prompt. The deliverable you are producing is the final version of the prompt I am going to give to CLIne to that will instruct it as to each and everything it needs to do. This prompt should be long and detailed and should include all the information from the spec.md, cline_master_prompt.md, and prompt_add.md which is relevant to the task. They are in the root folder of the project and can be referenced rather than directly quoted in the prompt in order to conserver context. Be sure to research as much as is needed in order to provide the best possible prompt. Do not assume anything. Do not make anything up.

Here’s a rewritten and augmented version of your prompt that incorporates **software engineering best practices**, including modularity, maintainability, clarity, iterative development, testing, and documentation. I’ve preserved your original intent but expanded it so an LLM has a structured, precise instruction set for generating a high-quality CLIne prompt for vibe coding. --- ```markdown You are an expert in **prompt engineering** and **software engineering best practices**, and your task is to help me build a **master prompt for CLIne** that will enable it to "vibe code" an entire project efficiently, accurately, and maintainably. ### Project Context - **spec.md**: This is the authoritative specification for the project. All decisions, features, and workflows should reference this file first. - **cline_master_prompt.md**: This is the current master prompt. It is functional but imperfect and must be improved. - **prompt_add.md**: This file contains supplementary information that must be integrated into the final master prompt wherever relevant. - **workflow.git**: This repository contains the workflow template to provide context on project structure, coding style, and operational logic. Reference it as needed for formatting, style, and organization guidance. ### Objective Your deliverable is the **final, fully-formed CLIne master prompt** that: 1. Instructs CLIne on **all tasks, procedures, and coding decisions** necessary to build the project end-to-end. 2. Integrates relevant content from **spec.md**, **cline_master_prompt.md**, and **prompt_add.md**, without unnecessary duplication, preserving clarity and context. 3. Conforms to **software engineering best practices**, including but not limited to: - **Modularity**: Break tasks and code generation into clear, manageable components. - **Maintainability**: Ensure the prompt encourages clean, well-documented, and scalable code. - **Consistency**: Follow consistent naming conventions, formatting, and architectural patterns. - **Validation and Testing**: Include instructions for CLIne to generate appropriate unit tests, integration tests, or checks where applicable. - **Documentation**: Produce internal documentation and inline comments for all generated code. - **Error Handling**: Anticipate potential failures or edge cases and instruct CLIne to handle them gracefully. - **Iterative Development**: Plan for incremental improvements, verification steps, and checkpoints to ensure correctness. - **Version Control Awareness**: Encourage structured commit messages and proper branching strategies, if applicable. - **Security and Performance Awareness**: Include guidance for secure coding practices and optimization considerations. ### Instructions for Prompt Generation 1. **Read and Understand All Sources**: Thoroughly review **spec.md**, **cline_master_prompt.md**, and **prompt_add.md**. Do not assume anything; verify all information before including it. 2. **Reference, Don’t Overload**: Where possible, reference the files rather than quoting their full content to conserve context and readability. 3. **Structure the Prompt Logically**: Organize instructions in a step-by-step, hierarchical, or modular format that CLIne can follow reliably. 4. **Explicit Deliverables**: Specify clearly what CLIne should produce at each stage—files, code blocks, test scripts, configuration, documentation, or other artifacts. 5. **Iterative Verification**: Include checkpoints where CLIne should verify correctness against specifications or tests before proceeding to the next step. 6. **Comprehensiveness and Clarity**: Ensure the final prompt is detailed, unambiguous, and leaves no critical detail unaddressed. ### Constraints - Do not invent features or requirements not present in **spec.md**. - Avoid vague instructions; everything should be actionable. - Ensure that the prompt can be fed to CLIne as-is to drive the coding workflow for the full project. Your output should be a **ready-to-use CLIne master prompt** that combines the authority of **spec.md**, the structure of **cline_master_prompt.md**, the supplementary details from **prompt_add.md**, and the workflow logic from **workflow.git**, while fully adhering to software engineering best practices. ``` --- This version explicitly frames the LLM’s task in terms of **software engineering rigor**, while keeping your original focus on vibe coding and iterative CLIne execution. It also makes **quality, maintainability, and verification** central parts of the prompt, so your final master prompt will be robust. If you want, I can **take this version and produce an actual full CLIne-ready master prompt skeleton** that’s immediately actionable and already structured for iterative improvements. That would save you a ton of manual adjustments. Do you want me to do that next?