Pokemon Champions Team Lab

Modes

Team Audit

Use when the user pastes one or more teams. Return:

• current format snapshot
• legality audit
• structural diagnosis
• keep/change decisions
• refined roster
• pilot notes
• threat checklist

Best-Fit Build

Use when the user gives locked picks or constraints. Build around:

• format
• regulation snapshot
• locked Pokémon
• style
• risk tolerance
• goal

Product Design Handoff

If the request drifts into builder architecture, recommend snapshot-driven design and hand off to:

• pokemon-champions-builder-architect
• pokemon-champions-builder-generator

Required snapshot fields

Always collect and report:

• date checked
• sources used
• active regulation or current public rules wording
• supported formats relevant to the request
• legality notes affecting the team
• key meta notes if available
• confidence level
• unresolved uncertainties

Output contract

For each team, return:

• Team name
• Format
• Final roster
• Set details for each Pokémon
• 3 biggest improvements
• 3 biggest remaining risks
• 1 easier or simpler alternative if needed

End with:

1. What changed from the original
2. How to rerun this next month
3. Reusable checklist for future Champions team reviews

Guardrails

• Do not invent legality.
• Do not assign Tera types unless current rules clearly support it.
• Do not blur official confirmation with secondary live signal.
• If a Mega, form, move, or mechanic is unsupported, say so plainly and replace it.

Optional references

• references/team-audit-template.md
• references/builder-product-spec.md
• references/example-teams.md
• references/structured-output-schema.json