campeonato-ux

Implements the standard two-column championship screen layout for the Primitivão React app.

Updated May 6, 2026
One-click install
npx skills add https://github.com/BanePlayss/primitivao --skill campeonato-ux-baneplayss
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: campeonato-ux
Source: https://github.com/BanePlayss/primitivao/tree/main/.claude/skills/campeonato-ux
Command: npx skills add https://github.com/BanePlayss/primitivao --skill campeonato-ux-baneplayss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Championship screens in the Primitivão app (LoL, Rocket League, CS, Valorant, TFT, FIFA and more) kept being built with inconsistent layouts — stacked single columns, missing round navigation, empty states with no guidance, and moderator controls scattered away from the matches they manage. This Skill encodes the closed, owner-approved standard structure so every new championship view ships with the same proven UX. ## Core Features & Use Cases - Standard two-column skeleton: Enforces the grid mk-grid layout with CLASSIFICAÇÃO (standings) on the left and RODADAS (rounds) plus the knockout bracket on the right, never stacked, with the champion banner outside the grid. - Complete component recipe: Specifies the standings table with colored position zones, per-player sub-lines, rules legend, round navigation rail with state pills, fixture cards with SEU JOGO pinned to top, and inline moderator result entry inside each match card. - Empty-state and checklist guidance: Every empty block must explain what unlocks it, and a 12-point checklist (including verifying getComputedStyle and both themes) validates any new championship view. - Use Case: When asked to create a new Valorant championship screen, apply this Skill to generate the full view reusing existing CSS classes like .mk-fx, .mk-rstrip, and .mk-std-table without inventing new wrappers. ## Quick Start Use the campeonato-ux skill to create the championship view for a new Valorant tournament following the standard two-column layout.

Frequently Asked Questions about campeonato-ux

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a championship screen in a React app?▼

Use a two-column grid with the standings table on the left and rounds plus the knockout bracket on the right, keeping the champion banner outside the grid. Reuse existing layout classes rather than inventing wrappers, and verify the computed grid style instead of only checking markup.

How should round navigation work in a tournament view?▼

Provide a numbered pill strip of all rounds grouped by phase, with state classes for finished, live, and future rounds plus a legend and match counter. Arrow-only navigation is discouraged because users cannot jump directly or see tournament progress.

Where should moderators enter match results in a tournament UI?▼

Moderators should enter results inline inside each fixture card, not in a separate admin panel. They are already looking at the match, so moving the action elsewhere adds friction.

What should an empty state show in a championship screen?▼

Every empty block must explain what unlocks it and show the action button if the viewer can unlock it, such as an enroll button when there are no participants or a publish bracket button for moderators after the group stage.

Why does my championship grid collapse into one column?▼

A common cause is inventing a new wrapper class instead of using the existing grid class, which breaks the two-column layout. Check the element's getComputedStyle rather than just the JSX markup to confirm the grid is applied.