| name | Sleeper Draft Assistant | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| description | A focused, local-first AI fantasy football draft and team-management workspace. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| colors |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| typography |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| rounded |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| spacing |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| components |
|
Creative North Star: "The Focused Draft Room"
This is an operational tool used while a manager is making time-sensitive decisions. The interface should feel like a quiet, well-organized draft room: the current state is easy to scan, the next useful action is obvious, and deeper reasoning is available without competing with the decision itself.
The system is dark, restrained, and information-dense. Tonal surfaces, compact borders, semantic status colors, and progressive disclosure create hierarchy without decorative noise. AI features may feel distinct through the indigo information accent, but they remain part of the same working environment rather than a separate chat product.
Key Characteristics:
- Focused and scan-friendly
- Dark operational surfaces with restrained elevation
- Green readiness and primary-action accent
- Indigo AI and informational emphasis
- Progressive disclosure for evidence, strategy, and history
The palette uses a near-black foundation with neutral charcoal surfaces and a small set of semantic accents. Green means ready or primary action, indigo means AI or informational context, amber means caution, and red means a blocking or destructive state.
- Readiness Green (#34d399): Primary actions, successful setup state, user picks, and confirmed readiness.
- Strong Readiness Green (#10b981): Hover and pressed emphasis for primary actions.
- AI Indigo (#8b9bf8): AI provider state, informational highlights, and neutral assistant emphasis.
- Warning Amber (#f5b544): Stale data, considerations, sync degradation, and attention-required states.
- Danger Red (#f87171): Errors, exclusions, and destructive actions.
- Near-black Background (#0b0d10): Global page foundation.
- Panel Surface (#14171c): Primary application panels.
- Raised Surface (#1b1f26): Secondary controls and elevated content.
- Sunken Surface (#0e1013): Inputs, board cells, and recessed content.
- Primary Text (#f2f4f6): Headings and high-priority values.
- Secondary Text (#aab0ba): Explanations and supporting content.
- Muted Text (#929aa6): Labels, metadata, and low-priority status text. This is the shipped value; 6.3:1 on the panel surface.
- Strong Border (#454c58): Secondary buttons, pills, callouts, and scrollbars. Structural, not a contrast target.
- Input Border (#626c7c): Field edges. At least 3:1 against the panel, raised, and sunken surfaces (WCAG 1.4.11).
Six --pos-* tokens (QB amber, RB green, WR sky, TE violet, K pink, DEF slate) drive the draft-board stripe and position chips, and nothing else.
--board-head, --board-cell, --board-user, --board-user-pick, and --board-current are the board-only surfaces for headers, cells, the user's column, the user's picks, and the cell on the clock.
The Semantic Accent Rule. Accent colors communicate state or action. Do not use them as decoration or apply them uniformly to every surface. Green only for actions and "ready"; numeric data is primary text; missing data is muted text with a reason; amber for anything that changes a lineup decision; red only for out, IR, and destructive actions.
The Token Rule. Literal hex colors live only in apps/web/src/lib/theme.css. Component styles reference tokens; apps/web/src/styles.test.ts fails the build otherwise.
Display Font: Inter (with ui-sans-serif, system-ui, sans-serif fallbacks)
Body Font: Inter (with ui-sans-serif, system-ui, sans-serif fallbacks)
Character: Compact, neutral, and highly legible at small sizes. Weight and color carry hierarchy more often than oversized type.
Tokens live in theme.css. Weights are 400, 500, 600, and 700 only; nothing heavier ships.
| Token | Size / line | Weight | Use |
|---|---|---|---|
--text-xs |
11px / 1.3 | 600, 0.06em, uppercase | Eyebrows and column heads only |
--text-sm |
12px / 1.4 | 500 (600 in chips and pills) | Metadata, chips, pills, legends, field labels |
--text-md |
13px / 1.45 | 400 | Secondary copy and table cells |
--text-base |
14px / 1.5 | 400 (600 in buttons) | Body, inputs, buttons |
--text-lg |
16px / 1.4 | 600 | Panel titles and player names in cards |
--text-xl |
18px / 1.35 | 600 | Drawer and dialog titles |
--text-2xl |
22px / 1.2 | 700, -0.01em | Page title in the top bar |
--text-3xl |
28px / 1.15 | 700, -0.015em | The decision headline only |
The uppercase label style is reserved for section eyebrows and table column heads. Chips, pills, tags, status text, and buttons are sentence case. Use tabular numerals on pick numbers, projections, ranks, and counts.
The Decision-First Type Rule. Use the largest weight and contrast for the current decision or state, not for secondary evidence or settings chrome.
The application uses a centered responsive shell with a constrained content column. Connected workflows are top-anchored so the board and working panels remain immediately available. The pre-connect state may use a narrower centered column to keep the entry task deliberate. The Setup strip appears only while choosing a league and draft, and the logo stacks above the title at the 520px phone breakpoint. Draft preparation carries readiness in its own checklist.
The draft room has one derived mode, draftRoomMode in apps/web/src/lib/draft-room.ts: on the clock, approaching (one or two picks away, the same threshold as automatic analysis, and also before the draft starts), waiting (everything else while drafting, including unknown pick timing), complete, and emergency.
On the clock and approaching, the room is one 880px column: the pick strip, the shortlist, the needs line, and the composer with its Board toggle, which opens the two-round board below at full width. Waiting, the strip and board lead at full width, followed by a Watching line, the needs line, and the composer. Emergency board-only mode and a completed draft put the board directly under their note, with recent picks and the roster below it. Recent picks and the roster are one quiet Picks and roster drawer in every live mode, because the drawer keeps the path identical across modes and competes with nothing. The board scrolls horizontally when team count exceeds the viewport, and it keeps the round column and team header legible.
Spacing follows the 4px base scale: --space-N is 4N pixels, with tokens for 4, 8, 12, 16, 20, 24, 32, and 40. Panel padding is 20px on desktop and 16px at the compact breakpoint. List rows are 44px. Group related controls tightly and use a full divider or larger gap before a separate workflow.
Breakpoints are literal in media queries because custom properties cannot drive them: two-column collapse at 1100px, compact at 760px, and phone at 520px. The style guard rejects any other width.
Depth is primarily tonal: near-black backgrounds, sunken inputs, raised controls, and panel surfaces establish the hierarchy. Small neutral shadows support panels and popovers without making the interface feel glossy. Borders are structural and remain subtle at rest.
- Low panel shadow (
0 1px 2px rgba(0, 0, 0, 0.45)): Default application panels. - Medium shadow (
0 10px 28px -12px rgba(0, 0, 0, 0.55)): Popovers and meaningful raised surfaces. - Large shadow (
0 28px 56px -20px rgba(0, 0, 0, 0.65)): Modal or dialog surfaces only.
The Tonal Layering Rule. Prefer surface and border changes over ornamental glow. Elevation should explain containment or focus.
The form language is restrained rounded rectangles with 6px controls, 10px fields and buttons, and 16px primary panels. Pills are reserved for compact status and confidence labels. Borders are 1px and semantic; avoid nested card shells and excessive rounded containers.
- Shape: 10px radius for standard buttons; 6px for compact controls.
- Primary: Readiness green with dark text, 10px 16px padding, used for the next clear action.
- Secondary: Raised charcoal surface with a strong neutral border.
- Ghost / text: Transparent, muted text for disclosures, alternate paths, and low-frequency actions.
- Hover / Focus: Small surface or border shift; use the shared green focus ring and preserve keyboard visibility.
- Disabled primary: Raised surface, subtle border, and muted text at 5.8:1, never faded green. A disabled primary does not count as a screen's one primary action.
- One primary: A screen or panel shows at most one live primary. Draft preparation is one list that gives it to the next unmet step in page order, then to Enter draft room; every other upload stays secondary and done rows collapse to one line of facts.
- Style: Small pill with semantic border and soft tint, 12px at weight 600, sentence case.
- State: Use for confidence, setup readiness, warnings, AI provider state, and compact counts. Do not use long sentences inside chips.
- Corner Style: 16px for primary panels, 10px for nested working surfaces.
- Background: Panel surface for working regions, raised surface for subordinate content, sunken surface for inputs and board cells.
- Shadow Strategy: Low structural shadow by default; medium or large shadow only for popovers and dialogs.
- Border: 1px neutral border at rest, semantic border for active or warning state.
- Internal Padding: 16px to 20px depending on panel importance.
- Shell: Every side panel uses
Drawer.svelte, which owns the scrim, enter motion, header, close button, and scrolling body. The modal rules inmodal.tsapply unchanged. - Size:
min(560px, 94vw)and full height, anchored right. At the 520px phone breakpoint it becomes a full-width bottom sheet,min(92vh, 840px)tall with 16px top corners. - Header: Optional eyebrow, 18px title with optional icon and status pill, one-line subtitle, and a 32px close button at the top right. The header stays visible while the body scrolls.
- Motion: The drawer slides in and the scrim fades in over
--transition-base, which is 0ms under reduced motion. Closing is immediate, so focus returns to the opener without delay.
- Style: Sunken surface, 1px input border (
--border-input), 10px radius, 10px 12px padding. - Focus: Green border and a restrained green focus ring.
- File inputs:
FileInput.sveltekeeps the native input visually hidden, focusable, and named by its label, and draws the label as a button. Focus shows the shared ring on the button; Enter or Space opens the system chooser. The selected file name or "No file selected" sits beside it. - Error / Disabled: Semantic red or amber callout for errors; disabled controls retain layout and use reduced opacity without losing their label.
- Style: Compact top bar with the product mark and active league/draft name. Settings is a quiet icon control. Draft switching is a disclosure menu attached to the active league name.
- Workspace controls: Use one labelled toggle for view ranges such as live rounds versus full board, and keep it visually distinct from connection or sync status.
- Mobile: Stack controls when necessary; preserve the active state and keep overflow intentional rather than clipping text.
One slim line, the only place the room says "On the clock": the state (amber on an amber tint when on the clock, otherwise "N picks away"), small pick facts, a quiet "Updating call…" status, and Find player and Plan on the right. Find player and Plan appear in every live mode, whether or not a strategy exists, and never in board-only mode. The status has its own grid track, so a refresh moves nothing. Sync status lives in the top bar. The strip shows no pick clock because the draft payload has none. Round direction lives on the board's rows.
The live view shows the current and next round in 72px cells, with the legend and Full board in the board header. The board is a dense, structured grid. Round direction, pick number, team ownership, current pick, user picks, and traded picks must remain distinguishable through layout plus semantic color. Team headers are interactive roster entry points and should retain accessible names and hover/focus states. A round runs the way the Sleeper pick order says, so linear and third-round-reversal drafts lay out and point correctly, and a format with no modeled order shows no direction. An unpicked cell names the pick's actual owner, a traded one says "Traded", the current pick says "Now", the user's next pick says "Your pick", and no cell is current outside a live draft. The grid is exposed as one table of column and row headers and cells through display: contents wrappers, so the sticky header and round column still belong to the grid. The room's single polite live region, not the board, announces a pick or call change once and stays silent on a sync that changes nothing.
One 880px column, the same measure as the focused draft room, and the top bar aligns to it. Top to bottom: the attention box, the lineup table, the composer, and the market activity line.
Attention box. A pure model in apps/web/src/lib/team-attention.ts builds it from tables of rules. It has three states. Needs a look is an amber box headed "N things need a look" with a labelled list of underlined buttons. A starter item moves focus to that row, and a data item opens Manage data at the relevant control. All clear is one quiet line with a green dot, "Lineup looks set", and the fact that supports it. Note is one neutral line for preseason, postseason, a week other than Sleeper's active one, or a failed refresh. Copy states facts and quotes Sleeper's status verbatim as "listed". It never says a player is playing, and it never recommends a player. Only starters count.
Lineup table. One semantic table: Slot, Player (position chip, name, team), Week (@ JAX, vs MIN, or the amber BYE chip), Proj when any exists, and Status. Rows are 44px. Proj is right-aligned in tabular figures; a missing value is a muted dash whose reason is in its title and for assistive technology, and the attention box states the gap. A flagged row has a tint, a 3px edge (red only for out and IR), and a small Ask control that fills the composer with a question naming the player and the fact, focused and unsent. Ask hides when the Assistant is unavailable. Bench, injured reserve, and taxi sit behind one row that starts closed on every mount and is not persisted, and they are never flagged. At the 520px phone breakpoint Status moves under the player's name with its Ask and a Status details disclosure; Week and Proj stay at every width. The chip wraps above the name at the narrowest widths. The table shows only what the payload contains and never ranks or compares players.
Composer. One quiet line, with Lineup, Waivers, and Plan on the right (Depth replaces Lineup outside the season). These chips send immediately. Enter sends and Shift+Enter adds a line; the field grows with its text. The thread opens above the composer at a fixed height of clamp(240px, 42vh, 460px) and scrolls inside itself. The lineup stays first on the page and one scroll away; asking scrolls once to bring the thread and composer into view, and an arriving answer never moves the page. A Conversation toggle hides the thread.
Market activity. One quiet line, only when there is real activity, with View details opening the existing market signals. With none it renders nothing.
A drawer with one lead block and one line each below it. A pure model in apps/web/src/lib/team-data-lead.ts builds the lead from a table of rules over the readiness payload. The lead states what the selected week is missing in one sentence, with position chips (a loaded chip is colored, a missing one is dashed), at most one primary action, and FantasyPros source links. Amber means something needs doing. A green dot means the week's files are loaded on Sleeper's active week and nothing has failed, and it comes with no primary button. A neutral lead makes no claim: preseason, postseason, a load in progress, or a pinned week, which also shows a callout with Back to Week N. The lead's file control imports into the week it names, not a week typed below it, and an accepted import or week change retires the chosen files.
Lines. Weekly projections, Season value rankings, and Coverage, in that order; preseason puts Season value rankings first and has no Coverage line. Each is DataLine.svelte: a heading button with a title and a one-line summary that turns amber when it needs attention, over a body that stays mounted while hidden, so typed values and chosen files survive closing it and its controls leave the tab order. Each attention item opens the line holding its control. The weekly-files item lands on the lead's file control when the lead has one.
Call the strategist "Assistant" in copy. Say "Codex" only for the external program the user installs, signs in to, or configures. Separate metadata with " · ", show statuses as sentence-case labels rather than API values, and write errors as what happened, then what to do next.
Assistant recommendation, strategy, evidence, and conversation are progressively disclosed. The shortlist's top row and its one reason line lead; analysis, evidence, history, and user guidance open on demand. AI status, confidence, stale context, and provider availability must be explicit.
The shortlist is one table: rank, position chip, name and team, ADP, Proj, with one heading that says "Assistant's shortlist" on the clock and "Targets if available" before it. Row 1 is emphasised with a larger name, a tint, an accent edge, and the reason line. Nothing else on the screen is bright, so the live draft room carries no primary button while a shortlist shows. It never shows a computed score, and placeholder ranks and rank-derived estimates count as no value. Availability comes from state.picks: a taken player is struck through with "Taken by ", and the next player moves up in the Assistant's own order, labelled as its next choice while a new call loads. The list stays on screen through a refresh, the heading names the pick an older list came from, and an empty list points at Find player. Promotion never re-ranks; it only removes unavailable players from the Assistant's order.
Why this call opens reasons, evidence, risks, turn timing, confidence, contingencies, and news sources in place. Plan holds next-turn and can-wait priorities. Find player holds Clear for saved preferences. The composer is one quiet line with the Board toggle inside it; Ask appears once there is text, suggestion chips appear on keyboard focus, and asking expands the thread in place.
- Do show the current draft state and next useful action before secondary detail.
- Do use semantic colors consistently for readiness, AI/info, warning, and danger.
- Do keep controls keyboard-accessible with meaningful labels and visible focus.
- Do preserve the existing token system in
apps/web/src/lib/theme.cssand prefer shared primitives. - Do use progressive disclosure for evidence, settings, and history.
- Do keep draft-board horizontal scrolling explicit and usable on narrow screens.
- Don't turn every evidence item or explanation into an equally weighted card or button.
- Don't expose a deterministic local ranking as if it were AI advice or projection certainty.
- Don't overload the live draft surface with every tool at once.
- Don't use decorative gradients, glows, or color without a state or hierarchy purpose.
- Don't hide errors, stale data, provider state, or important uncertainty behind ambiguous copy.
- Don't introduce another visual language for Team Manager; extend the draft-room system.