Know which copy is authoritative
A terminal can be open inside an old export while the editor and preview use a different folder. Confirm the working directory and repository status before asking for a change. Test one small edit to establish that source, build, and browser are connected.
The Cursor CLI overview describes its terminal coding workflows. Use the current provider documentation for setup and available controls. This guide explains a static-site process; it does not imply that CliCMS supplies a Cursor CMS plugin.
Keep permanent conventions near the source
Document the route format, shared component locations, style conventions, and known build process. Include a representative completed page. That repository context helps keep a new session from treating the site as a greenfield application that needs a different framework.
Separate stable conventions from the current task. The rule that public routes are extensionless belongs in the project notes. The instruction to add one article belongs in the session brief.
Inspect before editing
Ask the agent to identify how the affected page is generated. For article content, it should find the source entry and the rendering layout. For a menu change, it should identify the shared navigation rather than assume every page needs a separate patch.
Coordinate manual and agent changes
Avoid concurrent rewrites of the same files by several tools. Finish a coherent change, inspect it, and then continue, or use clearly separated work areas for independent tasks. Tell the agent when you have made a manual correction so it does not work from an outdated assumption.
Separate layout changes from article drafting when possible. A shared component edit deserves a broad regression review; a paragraph correction deserves focused editorial attention. Combining them makes the patch harder to understand.
Establish the process before automating it
Start interactively with explicit inputs and acceptance criteria. Once a review task behaves predictably, define a consistent report format before considering repeated execution. A navigation audit should name the affected page, destination, and failure rather than return an unstructured general critique.
Keep recommendations, file edits, and publication as distinct stages. An automated review should not silently become permission to deploy whatever repair it suggests.
Verify the rendered result
Run the project's build and preview the public directory. Check the changed route and a representative unchanged one. Test nested assets, keyboard focus, mobile navigation, and long headings.
The Cursor CLI content workflow article expands these steps into a complete working session. Use the prompt library for a bounded brief, and the complete-site workflow for the checks that belong after implementation. A useful session ends with a change another maintainer can understand and verify.
