UI Page

UI Page

Overview

Part of StyleSeed, this skill scaffolds a complete page or screen using the Toss seed's mobile-first composition rules. It keeps page structure consistent by building on the existing shell, top bar, bottom navigation, and card rhythm instead of producing disconnected sections.

When to Use

• Use when you need a new page in a Toss-seed app
• Use when you want a consistent page shell, spacing, and navigation structure
• Use when you are adding a new product flow and need a solid starting layout
• Use when you want to stay mobile-first even if the project later expands to larger breakpoints

How It Works

Step 1: Inspect the Existing Shell

Read the current page scaffolding patterns first, especially:

• page shell
• top bar
• bottom navigation
• representative pages using the same route family

Step 2: Define the Page Purpose

Clarify:

• the page name
• the primary user question the screen answers
• the top one or two actions the user should take

Every screen should have one dominant purpose.

Step 3: Use the Information Pyramid

Lay out the page from highest importance to lowest:

1. Hero or top summary
2. KPI or key actions
3. detail cards or supporting modules
4. lists, history, or secondary content

Avoid repeating the same section type mechanically from top to bottom.

Step 4: Apply the Toss Layout Rules

Default layout choices:

• mobile viewport width around max-w-[430px]
• page background on bg-background
• horizontal padding around px-6
• section rhythm with space-y-6
• generous bottom padding if a bottom nav is present
• cards using semantic surface tokens, rounded corners, and light shadows

Step 5: Compose Instead of Rebuilding

Use existing ui/ and patterns/ components wherever possible. New pages should primarily orchestrate existing building blocks, not recreate them.

Step 6: Account for Real Device Constraints

• handle safe-area insets
• avoid horizontal overflow
• keep interactive clusters thumb-friendly
• ensure long content scrolls cleanly without clipping the bottom navigation

Output

Return:

1. The page scaffold
2. The chosen section structure
3. Reused components and any newly required components
4. Empty, loading, and error states that the page will need next

Best Practices

• Keep the first version structurally correct before adding decoration
• Use one strong hero instead of multiple competing highlights
• Preserve navigation consistency across sibling screens
• Prefer reusable section components when the page will likely repeat

Additional Resources

• StyleSeed repository
• Source skill

Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for enprojectnment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.