skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
sickn33/agentic-awesome-skills79 installs

ui-page

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

How do I install this agent skill?

npx skills add https://github.com/sickn33/agentic-awesome-skills --skill ui-page
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill scaffolds mobile UI pages based on user-provided descriptions. It contains a surface for indirect prompt injection as it processes untrusted user input during code generation, but no active malicious behavior or exfiltration patterns were detected.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

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
  2. Illustrative page structure (replace every comment-only JSX prop with a real value before compiling):

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)]
  2. Use semantic tokens for all colors — never hardcode hex values.

  3. Compose the page from existing components (ui/ and patterns/) wherever possible.

  4. Safe area: include env(safe-area-inset-*) padding for modern devices.

  5. 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.

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.

Execution boundaries

This guide targets an existing StyleSeed project. The listed project paths, components, tokens and /ss-* commands are not bundled in this single-file entrypoint. Discover the actual project root and verify those prerequisites before edits; report absent resources instead of inventing them. Use host-supported invocation and existing project conventions. Layout numbers are design-system choices, not universal usability guarantees. Test keyboard access, responsive overflow and reduced motion on the actual interface.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/sickn33/agentic-awesome-skills/ui-page">View ui-page on skillZs</a>