AGENT SKILL

ui-page

Scaffold a new mobile-first page using StyleSeed Toss layout patterns, section rhythm, and existing shell components.

License 许可
MIT
最近更新
2026-11-10
Stars
★ 1
Forks
0

01 前言 Front Matter

name
ui-page
risk
safe
tags
[ "ui", "page-design", "mobile", "layout", "styleseed" ]
tools
[ "claude", "cursor", "codex", "gemini" ]
author
bitjaru
source
community
category
design
date_added
2026-04-08
description
Scaffold a new mobile-first page using StyleSeed Toss layout patterns, section rhythm, and existing shell components.
source_repo
bitjaru/styleseed
source_type
community

03 SKILL.md 正文

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

Limitations

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

04 同仓库更多 Skills

YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

vercel-sandbox

Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

slack

Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

electron

Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

dogfood

Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

shadcn

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.

★ 1