agneloze/epilepsure-extension/ui-pattern

Claude Code and agent skill by agneloze/epilepsure-extension

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Generate reusable UI patterns such as card sections, grids, lists, forms, and chart wrappers using StyleSeed Toss primitives.

Install

npx vskill@latest install agneloze/epilepsure-extension/ui-pattern

SKILL.md

The same SKILL.md was published earlier as ignvvcio254/jarvis-254-agent/ui-pattern.

UI Pattern

Overview

Part of StyleSeed, this skill builds reusable composed patterns from the seed's primitives. It is intended for sections like card lists, grids, form blocks, ranking lists, and chart wrappers that appear across multiple pages and need to look deliberate rather than ad hoc.

When to Use

  • Use when you need a reusable layout pattern rather than a one-off page section
  • Use when a page repeats the same arrangement of cards, rows, filters, or data blocks
  • Use when you want to build from existing StyleSeed primitives instead of copying markup
  • Use when you want a pattern component with props for dynamic content

How It Works

Step 1: Identify the Pattern Type

Common pattern families include:

  • card section
  • two-column grid
  • horizontal scroller
  • list section
  • form section
  • stat grid
  • data table
  • detail card
  • chart card
  • filter bar
  • action sheet
Step 2: Read the Available Building Blocks

Inspect both:

  • components/ui/ for primitives
  • components/patterns/ for neighboring patterns that can be extended

The goal is composition, not duplication.

Step 3: Apply StyleSeed Layout Rules

Keep the Toss seed defaults intact:

  • card surfaces on semantic tokens
  • rounded corners from the system scale
  • shadow tokens instead of improvised shadow values
  • consistent internal padding
  • section wrappers that align with the page margin system
Step 4: Make the Pattern Dynamic

Expose data through props instead of hardcoding content. If a pattern has multiple variants, keep the API explicit and small.

Step 5: Keep the Pattern Reusable Across Pages

Avoid page-specific assumptions unless the user explicitly wants a one-off section. If the markup only works on one route, it probably belongs in a page component, not a shared pattern.

Output

Provide:

  1. The generated pattern component
  2. The target location
  3. Expected props and usage example
  4. Notes on which existing primitives were reused

Best Practices

  • Start from the smallest existing building block that solves the problem
  • Keep container, section, and item responsibilities separate
  • Use tokens and spacing rules consistently
  • Prefer extending a pattern over adding a near-duplicate sibling

Additional Resources

Security

  • Security scanPassed, 95 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
1
Repository forks
1
7-day trend score
8

Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/agneloze/epilepsure-extension/ui-pattern/badge)](https://verified-skill.com/skills/agneloze/epilepsure-extension/ui-pattern)

Something wrong with this skill or its page? Tell us.