Claude Code: Build Safely

Claude Code works inside a real folder.

What if a coding assistant could read the whole project—not just one pasted snippet? That is powerful precisely because the folder, permissions and final decisions still belong to you.

Claude Code is an AI-powered coding agent that runs in a terminal. It is not a programming language, framework or replacement for Git. It can inspect a codebase, explain files, propose edits and run commands you allow. Developers use it for careful debugging, repetitive changes, test writing and codebase research.

It needs internet access, a supported installation and currently eligible Anthropic access; use the free installation guide. Because it works inside real folders, you must choose the folder carefully, understand permissions and review what changed.

Before the first prompt

1. Follow the current official installation and authentication guide for your platform.
2. Open only the project folder you intend to work on—not your entire home directory.
3. Make a Git commit or recoverable backup.
4. Remove secrets from prompts and tracked files; use environment variables and ignored local files.
5. Know the command that proves the project still works.

Outcome: Add a filter to the resource list.

Scope:
- Work only in src/resources/ and its tests.
- Keep the existing visual design and data format.

Before editing:
1. Inspect the relevant files.
2. Explain the current data flow.
3. Propose a short plan and wait for approval.

Done means:
- Keyboard and pointer users can filter.
- Empty results are explained.
- Existing and new tests pass.

Use one repeatable loop.

1. Inspect: ask what files, behaviour and tests currently exist.
2. Plan: agree on a small change and its acceptance checks.
3. Change: let Claude implement only the approved scope.
4. Verify: run checks, inspect the diff and exercise the real user flow.
5. Record: commit a coherent change with the reason, not just the file list.

Inspect the form submission flow without editing anything.
Report:
- the entry point and data path,
- existing validation and tests,
- likely cause of the duplicate submission,
- the smallest safe fix,
- exact commands and browser steps that would verify it.

Stop after the plan.

What belongs in CLAUDE.md

• Short project purpose and architecture.
• Setup, formatting, test and build commands.
• Important conventions and directories.
• Actions that require approval.
• Definitions of done that apply repeatedly.

Do not put credentials, temporary task details or an enormous copy of general documentation there. Keep instructions specific enough to change decisions.

“Done” needs proof.

Read the diff. Run syntax, unit and build checks. For a UI change, open the real page at desktop and mobile sizes, exercise the interaction and check the console. A green build cannot prove that the button is readable or that the workflow makes sense.

Never delegate blindly

• Destructive file or database operations.
• Publishing, payments or messages to real people.
• Security, privacy or legal decisions.
• Handling secrets and production credentials.
• Claims that require current external evidence.