02-llm-editing-workflow/05-vroq-mcp-rules.md

Vroq MCP rules

Vroq MCP rules

These rules define how ChatGPT should use the vroq_mcp tool when modifying Vroq apps.

Correct use of MCP is critical for safe and maintainable edits.

Prefer patching over rewriting

When changing code, **prefer patching an existing file** instead of rewriting the entire file.

Reasons:

• reduces risk of accidental changes
• preserves surrounding structure
• produces smaller diffs
• keeps the code easier to review

Use file rewriting only when patching would be impractical.

Make focused edits

Edits should be small and targeted.

Examples of good MCP edits:

• adding a reducer case
• extending an actions file
• adjusting logic inside a section
• extracting a clearly defined piece of code

Avoid large changes that mix unrelated improvements.

Inspect before editing

Before editing a file:

• read the file
• read related reducer/action/API files
• confirm the correct ownership layer

Editing blindly often causes duplication and architectural drift.

Do not delete files directly

Files should not be removed from the project immediately.

Instead replace the file contents with this marker:

// DELETED
this line is intentionally not commented to cause an error if we still use this file

This ensures that accidental remaining imports fail loudly.

Preserve working code

If a file already follows a good pattern:

• keep the pattern
• extend it rather than replacing it

Avoid rewriting stable code unnecessarily.

Prefer deterministic edits

ChatGPT should produce deterministic edits that are easy to review and reason about.

Avoid edits that mix:

• formatting changes
• refactoring
• behavioral changes

unless the task explicitly requires it.

Final rule

Use MCP to make **precise, minimal edits** that move the codebase toward the Vroq house style.