
Ss Page
- 229 installs
- 868 repo stars
- Updated August 3, 2026
- bitjaru/styleseed
ss-page is a Claude Code skill that scaffolds a new mobile page or screen using StyleSeed layout patterns.
About
ss-page is a StyleSeed skill that scaffolds a new mobile page or screen using the design system's layout patterns. A developer uses it to create a full screen composed from PageShell, TopBar, and BottomNav with the correct container width, spacing, cards, and safe-area padding. After generating the page it verifies the result against the Golden Rules and fixes any violation before presenting it.
- Scaffolds a new mobile page using StyleSeed layout patterns
- Composes PageShell, TopBar, and BottomNav with semantic tokens
- Runs a mandatory Golden Rules verification before presenting the page
Ss Page by the numbers
- 229 all-time installs (skills.sh)
- Ranked #903 of 1,880 Design & UI/UX skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
ss-page capabilities & compatibility
- Capabilities
- page scaffold · mobile layout · screen generator · ui generation
- Use cases
- frontend · ui design
What ss-page says it does
Scaffold a new mobile page/screen using the StyleSeed layout patterns
Container: `max-w-[430px]` (mobile viewport)
**Post-generation verification (MANDATORY):**
npx skills add https://github.com/bitjaru/styleseed --skill ss-pageAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 229 |
|---|---|
| repo stars | ★ 868 |
| Last updated | August 3, 2026 |
| Repository | bitjaru/styleseed ↗ |
What it does
Scaffold a new mobile screen from StyleSeed layout patterns with Golden Rules verification.
Who is it for?
Creating a full mobile screen from StyleSeed shell and layout patterns
Skip if: A single composed pattern (use ss-pattern), desktop-only screens, multi-page navigation (use ss-flow first), or tweaking an existing page
When should I use this skill?
You need a new mobile screen scaffolded with correct layout and safe areas
What you get
A new mobile page composed from design-system patterns and verified against the Golden Rules
- A new mobile page file composed from design-system patterns
By the numbers
- Uses a max-w-[430px] mobile viewport
- Runs a mandatory Golden Rules verification checklist
Files
Mobile Page Scaffolder
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
1. 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
2. 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>
)
}3. 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)]
4. Use semantic tokens for all colors — never hardcode hex values.
5. Compose the page from existing components (ui/ and patterns/) wherever possible.
6. Safe area: include env(safe-area-inset-*) padding for modern devices.
7. 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.
Related skills
FAQ
What does ss-page compose a screen from?
PageShell, TopBar, and BottomNav patterns, with existing ui and pattern components, correct spacing, cards, and safe-area padding.
Does it verify the result?
Yes. It runs a mandatory Golden Rules check for cards, colors, spacing, and touch targets, and fixes violations before presenting.