Communicate
Share progress, blockers, absences, and changes in availability early.
New Member Guide
Your first week starts here.
TVT AI Startup Club helps students turn real problems into working digital products using AI and vibe coding. AI helps with the build; students still choose, test, understand, and explain the work.
First-week checklist
Get oriented before you start building.
Work through these steps in order. You do not need to arrive knowing how to code or with a finished idea.
- 01
Understand the club
Read what the club does, what members build, and what student responsibility looks like.
Read About - 02
Know the expectations
Review teamwork, contribution, responsible-AI, privacy, and security expectations.
Review expectations - 03
Find where you can contribute
Review all six team roles. Coding is only one of several meaningful ways to contribute.
Explore roles - 04
Learn the shared process
See how teams move from a specific problem to a working demo and documented handoff.
Open the workflow - 05
Begin the Vibe Coding path
Follow the curriculum from setup and product planning through deployment and demo.
Open Learn - 06
Make your work visible
Agree on a meaningful responsibility, save your progress, and document what you contribute.
Open the starter template
Recommended learning order
Seven stops, one complete onboarding path.
The sequence follows the official club knowledge base. Each step prepares you for the next.
Core expectations
Good teams make their work and needs visible.
Active membership is based on participation and responsibility, not prior technical ability.
Complete meaningful work
Take responsibility for agreed work connected to your role.
Document contributions
Save evidence of code, design, research, testing, planning, or presentation work.
Show unfinished work
Share incomplete or broken versions so the team can help before it is too late.
Accept feedback
Listen to specific, constructive feedback and apply what improves the work.
Ask when stuck
Try a focused approach, then ask your team or a club lead before the blocker grows.
Responsible AI & security
Use AI openly. Protect people and credentials.
You remain responsible for the result.
- Understand the important parts of your work.
- Test AI output, facts, citations, and the live product.
- Ask AI to explain changes you do not understand.
- Disclose AI use honestly when required.
- Follow school, class, and competition AI policies.
Never expose secrets or unnecessary student data.
- Keep API keys, passwords, tokens, and credentials out of public code.
- Do not put secrets in GitHub, screenshots, presentations, or public chats.
- Store secrets in environment variables and secure server-side code.
- Use fake or sample data during development whenever possible.
- Ask the Faculty Advisor or Club Lead before collecting sensitive information.
Meeting information
The weekly rhythm is set. Schedule details are not.
Undecided information stays clearly marked until the club confirms it.
Meeting frequencyOnce per weekConfirmed
Meeting dayNot yet finalizedPending
Meeting timeNot yet finalizedPending
Meeting roomNot yet finalizedPending
Meeting durationNot yet finalizedPending
Weekly time commitmentNot yet finalizedPending
Presentation coming soon
Not available yet
New Member PPT
The current deck is being regenerated from the approved club knowledge base. No stale presentation is published here.
New-member FAQ
Three useful answers before you begin.
Do I need a project idea before joining?
No. You may propose an idea, join another member’s project, help improve an existing idea, or contribute through a team role.
What should I do when I am stuck?
Try independently for up to 15 minutes: read the error, make the task smaller, check the relevant guide, and ask AI to explain the problem. Then ask your team or a club lead.
Can I use AI to write code?
Yes. AI-assisted building is part of the club method, but you must review, test, understand, and explain the important work and disclose AI use when required.
Choose your next step