Claude Code - lesson 3 | HackIndia Skills

Claude Code - lesson 3 | HackIndia Skills | HackIndia

Tip

Use Plan first

Plan mode lets Claude read files and propose a plan without editing source files until you approve.

Use it for multi-file changes, unfamiliar code, auth, database work, payment flows, deployment config, or anything that can break your demo.

claude --permission-mode plan

# Or toggle during a session with Shift+Tab
# until the status bar shows plan mode on.

Example

Block env reads

Example: your campus food app has a frontend, backend, and local .env with database URLs or test keys. Claude does not need real secrets to build features.

Add shared settings from the repo root. This protects root .env and files like .env.local, .env.production, and .env.test.

pwd
# /Users/you/hackindia-campus-food

mkdir -p .claude
cat > .claude/settings.json <<'EOF'
{
  "permissions": {
    "deny": [
      "Read(./.env)",
      "Read(./.env.*)"
    ]
  }
}
EOF

git diff -- .claude/settings.json

git add .claude/settings.json
git commit -m "Add Claude Code safety settings"

Your to-do

Do this now

Do each one yourself, then tap it to tick it off. The ticks are only a checklist for you: they are not marked or scored.

Run Claude Code only from your project root.
Add .claude/settings.json denying Read(./.env) and Read(./.env.*).
Check the diff, then commit only the shared settings file.
Open Claude Code and run /status to confirm settings loaded.
Run claude doctor if settings do not load or Claude reports an error.

0 of 5 done

# From the repo root
claude

# Inside Claude Code
/status

# In your terminal, if settings look wrong
claude doctor

Set permissions before coding

One guardrail

Pick a mode

Use Plan first

Settings files

Deny wins

Block env reads

Avoid broad trust

Do this now

Quick check