ss-page
$
npx mdskill add bitjaru/styleseed/ss-pageScaffold mobile pages using StyleSeed patterns
- Creates new mobile screens from design system templates.
- Depends on file read/write tools and shell commands.
- Reads CLAUDE.md for structure before generating code.
- Outputs complete TypeScript files ready to import.
SKILL.md
.github/skills/ss-pageView on GitHub ↗
---
name: ss-page
description: Scaffold a new mobile page/screen using the StyleSeed layout patterns
argument-hint: [page-name] [description]
allowed-tools: Read, Write, Edit, Grep, Glob, Bash
---
# 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-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
2. Page structure template:
```tsx
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 `--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.
More from bitjaru/styleseed
- ss-a11yAudit a component or page for accessibility issues and fix them
- ss-auditAudit screens for UX issues using Nielsen's heuristics and modern mobile UX best practices
- ss-componentGenerate a new UI component following the StyleSeed design conventions
- ss-copyGenerate UX microcopy (button labels, error messages, empty states, toasts) following a casual-but-polite voice and tone
- ss-feedbackAdd appropriate user feedback states (loading, success, error, empty) to a component or page
- ss-flowDesign user flows and navigation structure following proven UX patterns
- ss-lintQuick automated lint — detects common design system violations in seconds
- ss-motionApply a named StyleSeed motion to a component — either one of the 5 personality seeds (Spring/Silk/Snap/Float/Pulse × entrance/exit/hover/press/layout) or a distinctive keyword move from the motion library (toggle-flip, toggle-curtain, reveal-blur, pop-in, shimmer, …). Translates vibe words into framer-motion code from one source of truth.
- ss-patternGenerate a composed UI pattern (card layout, list, form section, grid, etc.) using design system primitives
- ss-reviewReview UI code for design system compliance, accessibility, and best practices