Skip to content
Contact DA
Published

AGENTS.md and CLAUDE.md for Thailand projects

If you keep telling AI coding tools the same things, those reminders belong in the repository.

For Codex, that usually means AGENTS.md. For Claude Code, that usually means CLAUDE.md. The exact file is less important than the habit: put stable project rules where the tool can find them, keep them short, and update them when the project changes.

Shared AI coding instruction files connected to codebase modules, tests, deployment checks, and Thailand business website rules

What the files should do

Instruction files are not marketing copy and they are not a full manual. They should help the coding agent make better local decisions.

Useful instructions include:

  • Project structure and ownership boundaries
  • Package manager and build commands
  • Test, lint, type-check, and deploy commands
  • Framework conventions
  • Content rules
  • Accessibility and SEO rules
  • Security-sensitive areas
  • What not to change without asking
  • How to summarize validation at the end

For a Thailand business website, that might include preserving /contact/ links, keeping local-market examples in English content, not changing published slugs, and checking booking or lead forms after edits.

Make instructions operational

Bad instruction:

“Write clean, scalable, high-quality code.”

Better instruction:

“Use existing components before creating new ones. Do not add dependencies without approval. Run pnpm check-types after TypeScript changes. Preserve public routes unless a redirect is added.”

The second version is useful because the tool can act on it and the developer can verify it.

Keep shared rules in one place

If a project uses both Claude Code and Codex, duplicated instructions drift quickly. A practical setup is to keep the shared rules in one base file and keep tool-specific guidance small.

That base can describe the project, commands, review expectations, and business context. Tool-specific files can then add only the parts that are unique to that tool.

This is especially useful in monorepos, multilingual websites, and long-running client projects where the same rules apply across several apps or packages.

Instructions do not replace review

Good instructions reduce repeated prompting. They do not guarantee correct code.

An AI coding tool can still misunderstand business logic, remove an edge case, skip a validation step, or produce a change that looks plausible but fails in production. The instruction file moves the default behavior in the right direction; the developer still owns the result.

That is why I combine instruction files with the workflow in Codex CLI for repository work in Thailand and Claude Code for existing codebases in Thailand.

When I can help

I can help set up practical AI coding instructions for existing Thailand business websites, WordPress themes, Laravel applications, Astro sites, and API-heavy projects.

If your project is starting to use Claude Code, Codex, or both, send me the repository context and I can help write the first useful instruction set in THB.

More articles