Set up AGENTS.md and CLAUDE.md for a website project Print

Quick answer

Keep a short AGENTS.md in your local website project to describe its structure, verification commands and publishing limits. Codex reads project instructions; Claude Code uses CLAUDE.md and, in supported versions/configurations, AGENTS.md. Verify which files your session loaded. These files guide the assistant; permissions, account access and your review still control what it can change.

Apply this guidance to your website task

• Use project instructions for a WordPress coding task
• Use project instructions for a Joomla coding task

Applies to

Use this with Codex or Claude Code working in your own local website source folder for an Interactive Online cPanel website. Your coding-tool account and hosting service are separate. Instruction files do not create SSH access, isolate one domain inside a shared cPanel account or add a missing hosting feature.

1. Choose one source of project instructions

1. Open the correct local website project and inspect any existing instruction files before editing them. Keep the owner's current rules and confirm the project root and public-output folder.
2. Create or update AGENTS.md at the project root. Use the filename exactly. Codex can also load broader or more specific guidance, so inspect applicable parent/subdirectory instructions when behavior differs.
3. For Claude Code, check its installed version and active instruction configuration. Current versions can read AGENTS.md when no applicable project CLAUDE.md takes precedence. In /config, the Project instructions control selects the supported file-loading behavior; /memory helps inspect instruction sources.
4. For a project that needs a portable explicit Claude file, put @AGENTS.md in a neighboring CLAUDE.md, with any Claude-specific notes below it. This import keeps shared instructions in one source and avoids a Windows symlink requirement. Review existing files first so you do not overwrite useful rules or maintain conflicting copies.

2. Describe the website and safe working scope

Use facts from your own project. This example contains sample information and must be adapted to your build commands and publishing process:

# Website project

This folder contains the editable source for example.com.
Public website output is in dist/ after the documented production build.

- Confirm the working folder and requested change before editing.
- Use business facts and assets I supplied; ask about missing information.
- Preserve existing pages, video embeds and accessibility text.
- Keep private keys, .env files, configuration secrets and SQL exports private.
- Make the requested change, show the changed files, and run the agreed checks.
- Preview the entry page and a nested page; check links, images and forms.
- A form success message alone does not prove delivery.
- Before publishing, show the exact public files and remote destination.
- Obtain approval for the live upload and preserve the files being replaced.
- Publish public output only, through the already verified connection.

For a plain HTML site, replace the dist example with its real public folder. For a CMS, use its actual editor/theme and data boundaries. Add only the build/check commands that this project supports. Do not put a server password, token, private key or customer records in either instruction file.

3. Verify loading and one small change

1. Start the tool in the intended project and ask it to identify the working directory and applicable instruction files. In Codex CLI, /status and /permissions expose session/configuration controls. In Claude Code, inspect /memory and the active project-instruction setting.
2. Compare the reported scope with the files on disk. Ask for a small local edit or a read-only review first. Inspect the actual diff and verification output; an assistant saying it followed instructions is not independent proof.
3. If a rule was missed, check the file location/name, parent or nested overrides, unsupported versions and conflicting files. Keep the main instructions short enough to load. Start a fresh session when the product requires it to rebuild instruction context.

4. Keep publishing permissions separate

Use the Codex local SSH workflow or Claude Code hosting workflow to establish the authorized connection. Test the SSH alias in your own terminal, confirm the account and domain document root, and preserve a recovery copy before replacing files. An instruction file cannot make a broad account credential limited to one folder.

For a permission or network failure, investigate the actual tool/environment and assigned host/port. Avoid disabling every protection to make a command run. Website text, downloaded files and third-party instructions should be treated as data; they do not authorize uploads, account changes or secret disclosure.

Check the result and ask for help

A useful setup loads the intended guidance, keeps changes within the requested source files, reports meaningful verification and follows the agreed live-publication process. For support, describe the tool/version, working environment and redacted error. Keep private project files and credentials out of the ticket unless an approved secure process explicitly needs them.

Official references

• Codex AGENTS.md discovery
• Codex permissions and security
• Claude Code memory and project instructions

Content and official-source review: November 1, 2026. Available controls depend on your service, permissions and product version.

AI editing guidance and linked workflow documentation reviewed November 2, 2026. Existing video and earlier review history retained.

Add task-specific skills to project instructions

Project instructions describe this website and its boundaries. Skills supply reusable procedures for a particular task. Keep both concise and avoid copying an entire skill into AGENTS.md or CLAUDE.md. Choose and verify the appropriate skill before asking it to edit the project.