AI Coding Tools - lesson 2 | HackIndia Skills

AI Coding Tools - lesson 2 | HackIndia Skills | HackIndia

Example

Repo-wide example

Start with a small file. You can improve it later. The goal is not to impress the AI. The goal is to reduce wrong assumptions.

File: .github/copilot-instructions.md

Project context:
This is a hackathon project for college students to split group expenses and settle using UPI outside the app.

Coding rules:
- Use TypeScript for new app code.
- Keep functions small and named by intent.
- Do not add new dependencies unless the README explains why.
- Do not hardcode API keys, tokens, phone numbers, or UPI IDs.

Review rules:
- Check for input validation in API handlers.
- Check for hardcoded secrets or test credentials.
- Check that generated code matches installed packages.
- If a change affects settlement logic, ask for or add a small test case.

Verification:
- Run the existing test command before saying work is complete.
- If tests are missing, write manual verification notes in the pull request or README.

Example

Path-specific example

Use path rules when one part of the repo needs extra care. Auth, payments, database migrations, and admin panels are common examples.

File: .github/instructions/backend.instructions.md

Apply to: backend/**

Backend rules:
- Validate request body fields before using them.
- Return safe error messages. Do not expose stack traces to users.
- Keep database writes inside clear service functions.
- For settlement or money-like amounts, use integer paise, not floating point rupees.
- Add a test or manual verification note for every API behavior change.

Add Repo Instructions

One idea

Why this matters

Pick instruction files

Repo-wide example

Path-specific example

Common mistake

Use AI to draft

Do this now

Quick check