Complete AI Training
Sign inBecome a member

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Skill · Design

Ui page

Scaffold a new mobile page/screen using the StyleSeed layout patterns

Agentic Awesome SkillsLicense: MITAdded Sep 5, 2026
Use it in my AI

How to use it

  1. Start your plan and connect your AI once
  2. Add the skill to your AI, one time only: press Copy skill and paste it into your AI's instructions: a project in ChatGPT, Claude or Grok, a Gem in Gemini, an agent in Microsoft 365 Copilot, or a rule in Cursor. It stays there for every new chat. In Kimi, paste it at the start of a new chat.
  3. Ask for the task in your own words, or say it directly:
Use the Ui page skill to help me with this.
SKILL.md

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-flow first
  • For tweaking an existing page — edit the file directly

Create a new page: $0 Description: $ARGUMENTS

Instructions

  1. Read the design system reference:
  • CLAUDE.md for file structure and conventions
  • components/patterns/page-shell.tsx for page layout
  • components/patterns/top-bar.tsx for header pattern
  • components/patterns/bottom-nav.tsx for navigation
  1. 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>
  )
}
  1. 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)]
  1. Use semantic tokens for all colors — never hardcode hex values.
  1. Compose the page from existing components (ui/ and patterns/) wherever possible.
  1. Safe area: include env(safe-area-inset-*) padding for modern devices.
  1. Post-generation verification (MANDATORY):
  2. After creating the page, verify against the Golden Rules:

  • [ ] All content is inside cards (no bare background content)
  • [ ] Only --brand color 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-6 for single cards, px-6 for 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.