Skill · Design
Ui page
Scaffold a new mobile page/screen using the StyleSeed layout patterns
How to use it
- Start your plan and connect your AI once
- Ask for the task in your own words, or say it directly:
Use the Ui page skill to help me with this.Without a connection: copy the SKILL.md below into your AI's project instructions.
Mobile Page Scaffolder
When to Use
Use this skill when you need scaffold a new mobile page/screen using the StyleSeed layout patterns.
When NOT to use
- For a single composed pattern within an existing page → use
/ss-pattern - For desktop-only screens — this skill is mobile-first
- For multi-page navigation structure → use
/ss-flowfirst - For tweaking an existing page — edit the file directly
Create a new page: $0 Description: $ARGUMENTS
Instructions
- Read the design system reference:
CLAUDE.mdfor file structure and conventionscomponents/patterns/page-shell.tsxfor page layoutcomponents/patterns/top-bar.tsxfor header patterncomponents/patterns/bottom-nav.tsxfor navigation
- Page structure template:
import { PageShell, PageContent } from "@/components/patterns/page-shell"
import { TopBar, TopBarAction } from "@/components/patterns/top-bar"
import { BottomNav } from "@/components/patterns/bottom-nav"
export default function PageName() {
return (
<PageShell>
<TopBar
logo={/* logo or page title */}
subtitle={/* optional subtitle */}
actions={/* optional action buttons */}
/>
<PageContent>
{/* Page sections with space-y-6 */}
</PageContent>
<BottomNav items={[/* nav items */]} activeIndex={0} />
</PageShell>
)
}
- Layout rules:
- Container:
max-w-[430px](mobile viewport) - Page background:
bg-background - Section horizontal padding:
px-6 - Section vertical spacing:
space-y-6 - Bottom padding for nav:
pb-24 - Cards:
bg-card rounded-2xl p-6 shadow-[var(--shadow-card)]
- Use semantic tokens for all colors — never hardcode hex values.
- Compose the page from existing components (ui/ and patterns/) wherever possible.
- Safe area: include
env(safe-area-inset-*)padding for modern devices.
- Post-generation verification (MANDATORY):
After creating the page, verify against the Golden Rules:
- [ ] All content is inside cards (no bare background content)
- [ ] Only
--brandcolor used for accents (no other accent colors) - [ ] No hardcoded hex values (all semantic tokens)
- [ ] Section types alternate (no two identical types in a row)
- [ ] Numbers have 2:1 ratio with units
- [ ] Spacing uses 6px multiples (p-1.5, p-3, p-6)
- [ ]
mx-6for single cards,px-6for grids/carousels - [ ] Touch targets ≥ 44px on all interactive elements
If any violation is found, fix it before presenting the page to the user.
Limitations
- Use this skill only when the task clearly matches its upstream source and local project context.
- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.