Connect Claude Code to your website project

Prepare a clean local project

• Use a Git repository with a clean working tree before the first AI-assisted task.
• Include the dependency lock file and the real build and test commands.
• Exclude .env files, SSH keys, database exports, uploaded customer data and production logs.
• Create an example environment file containing variable names and safe placeholder values only.

Install and open Claude Code

1. Install Claude Code using the current official Anthropic instructions for your operating system.
2. On Windows, use a supported WSL environment or Git for Windows configuration.
3. Open a terminal in the repository root and start Claude Code.
4. Complete authentication using the account or provider approved for your organisation.
5. Ask Claude to explain the repository and proposed deployment workflow before requesting changes.

Give Claude durable project instructions

• State which framework and runtime the project uses.
• List the install, development, test and production-build commands.
• Identify generated folders and files that must not be edited.
• Require a diff review and production build before any deployment.
• State that passwords, private keys and production environment values must never be printed or committed.

Keep permissions narrow

Claude Code can request permission to run tools and commands. Approve the specific operation needed for the task instead of disabling permission checks globally.

• Allow edits only inside the intended project directories.
• Review shell commands before they upload, delete or change production data.
• Do not use permission-bypass options for a live deployment workflow.
• Use a dedicated deployment credential rather than your personal root or hosting-panel account.

Deploy the reviewed release

1. Run the complete local test and production-build sequence.
2. Review the Git diff and commit the exact version being released.
3. Create a backup or release snapshot on the destination.
4. Upload or pull the committed release using the restricted deployment connection.
5. Verify the application health, important pages, forms and logs before removing the previous release.