Prompt Engineering - lesson 8 | HackIndia Skills

Prompt Engineering - lesson 8 | HackIndia Skills | HackIndia

Example

README proof block

Add a short test evidence section. It helps someone review your work fast, even on mobile.

Project: Campus Helpdesk Ticket Router

User task:
Students paste a complaint. The app returns a category, priority, and next action for the admin team.

Demo flow:
1. Open the app.
2. Paste a student complaint.
3. Click Classify.
4. Check the returned JSON.
5. Admin can copy the result into the ticket system.

Model use:
The language model classifies the complaint into fixed categories only.
It does not make final admin decisions.

Prompt tests:
- tests/prompt-cases.json contains 12 real-style student complaints.
- Cases include short text, mixed Hindi-English, angry tone, missing details, and unrelated requests.
- 10 of 12 cases matched the expected category.
- 2 failures are listed in tests/failures.md with planned fixes.

Known limits:
The app does not verify documents.
The app should not be used for emergencies.

Example

Test cases file

Keep test cases in a file, not only in your memory. This makes your prompt work visible.

[
  {
    "id": "case_01",
    "input": "WiFi in Block C is not working since morning. Online class at 2 pm.",
    "expected": {
      "category": "network",
      "priority": "high"
    },
    "actual": {
      "category": "network",
      "priority": "high"
    },
    "status": "pass"
  },
  {
    "id": "case_02",
    "input": "Mess food was cold again. Please do something.",
    "expected": {
      "category": "food",
      "priority": "medium"
    },
    "actual": {
      "category": "hostel",
      "priority": "medium"
    },
    "status": "fail",
    "note": "Prompt confuses mess complaints with general hostel issues."
  }
]

Submit Your AI Project

Ship the proof

What judges need

Submission checklist

Avoid demo theatre

README proof block

Use AI carefully

Test cases file

Do this now

Quick check