Prompt Engineering - lesson 1 | HackIndia Skills

Start with reliability

A prompt is not a magic line of text. It is an instruction you expect a model to follow again and again, even when users type messy input.

For a hackathon project, your prompt must survive real demo use. A judge should see the same kind of useful output on different cases, not one lucky answer.

Key point

One idea

A prompt holds up when it makes the job testable. It says what to do, who it is for, what not to do, and how you will know the answer is good.

Your to-do

Use four parts

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.

Name the role only if it changes the output, such as tutor, support agent, or resume reviewer.
State the exact task in one sentence.
Add limits the model must follow, such as length, tone, language, or forbidden claims.
Define the success rule, so you can judge whether the output worked.

0 of 4 done

Example

Bad to usable

Here is a common college hackathon prompt. It may work once, but it is too open-ended to test.

The improved version is still simple. It gives the model a job and gives you something to check.

Bad prompt:
Help students choose projects.

Usable prompt:
You are a project mentor for Indian college hackathon teams.
Task: Suggest 3 project ideas for the user's skills and time.
Limits: Keep each idea under 60 words. Use low-cost or free tools. Do not suggest ideas that need paid datasets, paid APIs, or special hardware.
Success rule: Each idea must include the problem, target user, and one demo feature the team can build in 24 hours.

User input:
Skills: React, Node.js, basic Python
Time: 24 hours
Theme: public transport

Common mistake

Avoid vague success

Many prompts say “make it good”, “be creative”, or “give best output”. These words feel clear to you, but they do not give you a test.

Use visible checks instead. For example: “include 3 options”, “avoid medical advice”, “ask one follow-up question if input is missing”, or “write for a first-year student”.

Tip

Write prompts in files

Do not hide important prompts inside random code strings. Put them in a prompt file or a clearly named constant, so your team can review and edit them.

For your final HackIndia submission, this also shows judges that you treated the AI feature like real product logic, not a last-minute add-on.

Example

Prompt file starter

Create a small prompt file for one real user task. This example is for a resume bullet improver, but use your own project idea if you have one.

File: prompts/resume_bullet_improver.txt

You are a resume editor for Indian college students applying to internships.

Task:
Improve one resume bullet so it is clearer, more specific, and action-focused.

Limits:
- Keep it under 25 words.
- Do not invent numbers, company names, awards, or tools.
- Use simple professional English.
- If the input is too vague, ask one question instead of rewriting.

Success rule:
The output is acceptable only if it keeps the original meaning and does not add fake achievements.

User input:
{{resume_bullet}}