Welcome to the team! Your challenge is to shape and build a web app that helps people create Pokemon teams and understand what those teams are capable of.

This repository is a starting point, not a specification. We care about the product decisions you make as much as the code you write.

A successful experience should let someone:

• Find and select Pokemon for a team.
• Create and manage multiple distinct teams over time.
• Add and remove team members while understanding the effect of each change.
• Understand a team's combined base stats, including HP, attack, defense, special attack, special defense, and speed.
• See which Pokemon types are represented across the team.

A team should feel like more than a list of names. Beyond these core outcomes, decide which strengths, gaps, or patterns would be useful to surface.

How you turn the outcomes into a useful product is up to you. Decide what information matters, how people move through the experience, and which problems deserve the most attention.

These are questions to consider, not a feature checklist:

• How does someone find the right Pokemon without the experience feeling like a catalog?
• How do they create, identify, switch between, and update their teams?
• How should team-level stats and type composition be presented so they are meaningful rather than just numbers?
• What feedback helps someone understand the effect of adding or removing a Pokemon?
• What should happen when a team is empty, incomplete, unusually large, or contains the same Pokemon more than once?
• Which choices should persist when someone returns?
• What details make the experience feel responsive, accessible, and complete?

Make reasonable assumptions and prioritize. You are welcome to improve the interface, information architecture, data model, and technical foundations wherever they support your product direction.

The project uses React, React Router, TypeScript, and Tailwind CSS. It includes helper functions for interacting with the PokeAPI in app/services.

Install the dependencies and start the local development server:

npm install
npm run dev

The app will be available at http://localhost:5173.

Use whatever workflow and tools help you do your best work. AI tools are explicitly welcome, as are documentation, libraries, and any other resources you would normally use.

We are not testing whether you can do everything from memory or without assistance. Choose approaches because they help solve the product problem, not because you think they will impress us.

The goal is to understand how you work: how you frame ambiguity, prioritize, use tools, evaluate their output, validate the result, and communicate your decisions. Whatever workflow you choose, you should be able to explain it and stand behind the finished product.

When you finish, briefly explain:

• The user needs you prioritized and why.
• The product and technical decisions you made.
• The assumptions and tradeoffs that shaped the result.
• How your workflow and tools, including AI where relevant, supported your work.
• What you would explore next with more time or user feedback.