Tailwind CSS - lesson 7 | HackIndia Skills

Key point

Submit the proof

A polished repo is not just a good-looking page. It is a public project that someone else can open, run, and judge in two minutes.

Your proof should show three things clearly: a finished responsive page, dark mode styling, and readable Tailwind classes.

Think like a reviewer

A hackathon judge, senior student, or recruiter will not inspect every class. They will scan the live page, README, commit history, and folder structure.

Make the first screen count. Your page should not look like a raw Vite starter. It should have real spacing, type, layout, and dark mode states.

Your to-do

Final repo check

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 the app locally and test the main page on mobile and laptop widths.
Toggle dark mode or switch your system theme, depending on how your app handles it.
Open your main components and remove duplicate or messy class strings.
Check that Tailwind v4 is imported from your CSS entry with the current v4 style.
Commit only useful files, not local caches, build folders, or screenshots you do not use.

0 of 5 done

Example

README checklist

Your README does not need to be long. It needs to answer the questions a reviewer has before they run your app.

Use plain language. Mention what you built, how to run it, and where the Tailwind finish is visible.

# Campus Expense Splitter

A responsive Vite app for tracking shared college expenses.

## What is finished
- Responsive dashboard for mobile and desktop
- Dark mode styling for cards, text, borders, and buttons
- Tailwind CSS v4 utility classes kept readable
- Main page styled for a hackathon demo

## Run locally
npm install
npm run dev

## Tech used
- Vite
- Tailwind CSS v4

## Demo notes
Open the dashboard page and resize the browser.
Check dark mode using your system theme or the app toggle.

Common mistake

Do not hide setup

Beginners often submit a good screenshot but a confusing repo. That weakens trust.

If someone has to guess the install command, app route, or dark mode behaviour, the repo does not feel finished.

Tip

Use AI carefully

Ask AI to review your README and repo checklist, not to invent features. Paste your actual file tree and README draft.

Check every suggestion. Remove false claims like fake deployment links, unused libraries, or features your app does not have.

Prompt:
Review this hackathon repo README for clarity.
Do not add features that are not listed.
Tell me what a recruiter may not understand in 2 minutes.

Project summary:
[write your real project summary]

README:
[paste your README]

File tree:
[paste your file tree]