Product Page Scaffolder
Registry-first artifact boundary
When .styleseed/project.json and .styleseed/artifacts/index.json exist, resolve the requested artifact ID first, then read only .styleseed/bundles/<artifact-id>.md and .styleseed/manifests/<artifact-id>.json. Never fall back to the global legacy bundle for a registry project. Legacy projects may use .styleseed/effective-rules.md only when no registry exists.
When NOT to use
- For a single composed pattern within an existing page → use
/ss-pattern
- 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
Resolve and read the active design method:
.styleseed/effective-rules.md and .styleseed/manifest.json
- If missing or stale, invoke
/ss-resolve or $ss-resolve from STYLESEED.md
components/patterns/page-shell.tsx for page layout
components/patterns/top-bar.tsx for header pattern
components/patterns/bottom-nav.tsx for 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 recipe="enterprise-workbench">
<TopBar
logo={/* logo or page title */}
subtitle={/* optional subtitle */}
actions={/* optional action buttons */}
/>
<PageContent>
{/* Compose the grammar's focal point and recipe-fit sections */}
</PageContent>
<BottomNav items={[/* nav items */]} activeIndex={0} />
</PageShell>
)
}
Apply the selected adapter and recipe:
- Set
recipe="<manifest selection.recipe>" on PageShell, or
data-styleseed-recipe="<id>" on a custom artifact root.
- Use the lock's viewports and the adapter's responsive contract. Do not assume 430px mobile.
- Use
ss-page-padding, ss-page-gutter, ss-pattern-stack, ss-pattern-surface,
ss-pattern-inset, ss-pattern-control, and ss-pattern-icon where bundled patterns fit.
- Select components by recipe: aligned panels/rows for workbenches, flat steps for public
service, reading flow for editorial, focused canvas/tool groups for creative tools, and
soft grouping only when the recipe calls for it.
- A page may contain cards, panels, rules, whitespace, rows, tables, or a canvas. Never force
every content block into a 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):
Run /ss-score then /ss-verify. Confirm:
1---
2name: ss-page
3description: Scaffold a new product page or screen from the compiled StyleSeed output grammar, surface adapter, brand recipe, and project lock.
4argument-hint: "[page-name] [description]"
5allowed-tools: Read, Write, Edit, Grep, Glob, Bash
6metadata:
7 source: https://skillmd.com/skills/bitjaru/ss-page
8---
9
10# Product Page Scaffolder
11## Registry-first artifact boundary
12
13When `.styleseed/project.json` and `.styleseed/artifacts/index.json` exist, resolve the requested artifact ID first, then read only `.styleseed/bundles/<artifact-id>.md` and `.styleseed/manifests/<artifact-id>.json`. Never fall back to the global legacy bundle for a registry project. Legacy projects may use `.styleseed/effective-rules.md` only when no registry exists.
14
15## When NOT to use
16
17- For a single composed pattern within an existing page → use `/ss-pattern`
18- For multi-page navigation structure → use `/ss-flow` first
19- For tweaking an existing page — edit the file directly
20
21Create a new page: **$0**
22Description: $ARGUMENTS
23
24## Instructions
25
261. Resolve and read the active design method:
27 - `.styleseed/effective-rules.md` and `.styleseed/manifest.json`
28 - If missing or stale, invoke `/ss-resolve` or `$ss-resolve` from `STYLESEED.md`
29 - `components/patterns/page-shell.tsx` for page layout
30 - `components/patterns/top-bar.tsx` for header pattern
31 - `components/patterns/bottom-nav.tsx` for navigation
32
332. Page structure template:
34```tsx
35import { PageShell, PageContent } from "@/components/patterns/page-shell"
36import { TopBar, TopBarAction } from "@/components/patterns/top-bar"
37import { BottomNav } from "@/components/patterns/bottom-nav"
38
39export default function PageName() {
40 return (
41 <PageShell recipe="enterprise-workbench">
42 <TopBar
43 logo={/* logo or page title */}
44 subtitle={/* optional subtitle */}
45 actions={/* optional action buttons */}
46 />
47 <PageContent>
48 {/* Compose the grammar's focal point and recipe-fit sections */}
49 </PageContent>
50 <BottomNav items={[/* nav items */]} activeIndex={0} />
51 </PageShell>
52 )
53}
54```
55
563. Apply the selected adapter and recipe:
57 - Set `recipe="<manifest selection.recipe>"` on `PageShell`, or
58 `data-styleseed-recipe="<id>"` on a custom artifact root.
59 - Use the lock's viewports and the adapter's responsive contract. Do not assume 430px mobile.
60 - Use `ss-page-padding`, `ss-page-gutter`, `ss-pattern-stack`, `ss-pattern-surface`,
61 `ss-pattern-inset`, `ss-pattern-control`, and `ss-pattern-icon` where bundled patterns fit.
62 - Select components by recipe: aligned panels/rows for workbenches, flat steps for public
63 service, reading flow for editorial, focused canvas/tool groups for creative tools, and
64 soft grouping only when the recipe calls for it.
65 - A page may contain cards, panels, rules, whitespace, rows, tables, or a canvas. Never force
66 every content block into a card.
67
684. Use semantic tokens for all colors — never hardcode hex values.
69
705. Compose the page from existing components (ui/ and patterns/) wherever possible.
71
726. Safe area: include `env(safe-area-inset-*)` padding for modern devices.
73
747. **Post-generation verification (MANDATORY):**
75 Run `/ss-score` then `/ss-verify`. Confirm:
76 - [ ] The first viewport exposes the grammar's user job and one focal point
77 - [ ] Containment, geometry, controls, collections, density, and navigation fit the recipe
78 - [ ] Only `--brand` color used for accents (no other accent colors)
79 - [ ] No hardcoded hex values (all semantic tokens)
80 - [ ] Section types alternate (no two identical types in a row)
81 - [ ] Spacing uses one repeatable recipe-fit rhythm
82 - [ ] Touch targets ≥ 44px on all interactive elements
83 If any violation is found, fix it before presenting the page to the user.