Claude Code - lesson 2 | HackIndia Skills

Claude Code - lesson 2 | HackIndia Skills | HackIndia

Your to-do

Start with init

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.

Open your repo at the project root.
Start Claude Code.
Run /init inside the Claude session.
Read the generated CLAUDE.md like a teammate would.
Remove wrong assumptions and commands that do not exist.

0 of 5 done

cd ~/projects/hackindia-campus-pay
claude

# Inside Claude Code
/init

Example

Useful CLAUDE.md

Keep it short and specific. Do not write a product pitch. Write what helps Claude make correct edits.

# CLAUDE.md

## Project goal
Campus Pay Split is a HackIndia hackathon project for college students in India.
The demo flow is: create a group, add members, add a shared expense in rupees, and show who should pay whom.
Prioritise a working demo over extra features.

## Stack
- Next.js app using the app directory.
- TypeScript for application code.
- Prisma for database models and queries.
- UI components live in `components/`.
- Shared helpers live in `lib/`.

## Commands
- Install dependencies: `npm install`
- Start local dev server: `npm run dev`
- Build for submission: `npm run build`
- Lint: `npm run lint`
- There is no test script yet. Do not claim tests passed unless a test command is added.

## Code conventions
- Use TypeScript types for props and data returned from helpers.
- Keep React components small and readable.
- Put expense calculation logic in `lib/settlement.ts`, not inside page components.
- Use rupees for displayed amounts. Format as `₹500`, not `$500`.
- Prefer clear variable names like `payerId`, `splitAmount`, and `settlements`.

## Git workflow
- Check git status before changing files.
- Keep changes focused on the requested task.
- Do not edit generated files unless the task requires it.

## Environment
- Environment variables are expected in `.env.local`.
- Never read, print, or commit real secrets.
- Use placeholder names when documentation needs to mention env vars.

Tip

If AGENTS.md exists

Claude Code reads CLAUDE.md, not AGENTS.md. If your repo already has AGENTS.md for another agent, import it instead of copying the same text into two files.

# CLAUDE.md

@AGENTS.md

## Claude-specific notes
- Use the commands in package.json.
- Ask before making broad architecture changes.
- Keep hackathon demo flow working: create group, add expense, view settlement.

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.

Create or edit ./CLAUDE.md in your hackathon repo.
Add the project goal, stack, real commands, folder rules, coding rules, and environment notes.
Import AGENTS.md with @AGENTS.md if your repo already has it.
Run git diff and read the file before committing.
Commit it with a clear message.

0 of 5 done

git status
git diff -- CLAUDE.md
git add CLAUDE.md
git commit -m "add Claude project context"

Give Claude project context

One idea

What Claude sees

Where context lives