frontend-patterns

frontend-patterns is a skill for Claude Code from Jartan-LLC/grimoire. It costs 21 tokens per session (1,017 once invoked), scanned A, original, MIT.

A set of principles for building consistent, maintainable user interfaces with CSS, the language that styles web pages. It covers shared design values, mobile-first layouts, and keeping component styles separate.

In plain words
What is it for?
Use it when creating or reviewing web interfaces, design systems, reusable components, or JavaScript integrations that need to read shared style values.
Why use it?
It reduces duplicated styling and prevents components from drifting apart in color, spacing, typography, and responsive behavior.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Part of the praxis plugin — 16 skills, 7 agents shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/jartan-llc/grimoire/frontend-patterns
Any agent
npx skills add Jartan-LLC/grimoire --skill frontend-patterns
Clone the repo
git clone --depth 1 https://github.com/Jartan-LLC/grimoire

Made for: Claude Code.

Or install praxis, the plugin that ships this one along with the rest of its 16 skills, 7 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for frontend-patterns

README.md
[![agentmods](https://agentmods.dev/badge/skills/jartan-llc/grimoire/frontend-patterns.svg)](https://agentmods.dev/skills/jartan-llc/grimoire/frontend-patterns)
Your own site
<a href="https://agentmods.dev/skills/jartan-llc/grimoire/frontend-patterns"><img src="https://agentmods.dev/badge/skills/jartan-llc/grimoire/frontend-patterns.svg" alt="Measured on agentmods" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,017 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.01017
Opus 5 $0.00010 $0.00508
Sonnet 5 $0.00004 $0.00203
Haiku 4.5 $0.00002 $0.00102

Measured 6d ago against content hash 697a6706019f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

frontend-patterns scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/praxis/skills/frontend-patterns/SKILL.md · 123 lines

How it starts

The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Frontend Design Principles

Core principles for maintaining consistent, maintainable frontend code. Framework-agnostic -- adapt examples to your stack.

1. Single Source of Truth

Every design decision is defined exactly once. Design tokens live in the styles system. Components reference them, never redefine them.

/* Token file */
:root { --color-primary: #5b5956; }

/* Component */
.button { background: var(--color-primary); }  /* yes */
.button { background: #5b5956; }               /* no */

For JavaScript/SDK integrations, read tokens at runtime:

const primary = getComputedStyle(document.documentElement)
  .getPropertyValue('--color-primary').trim();
SDK.configure({ buttonColor: primary });  /* yes */
SDK.configure({ buttonColor: '#5b5956' }); /* no */

2. Variable-First Development

If it's a design value, it's a variable. Colors, spacing, fonts, shadows, radii, and breakpoints are always variables -- even if used once.

.card { padding: var(--space-xl); border-radius: var(--radius-lg); }     /* yes */
.card { padding: 32px; border-radius: 12px; }                            /* no */

Every referenced variable must exist in the token files. Undefined variables fall back to browser defaults silently.

Exceptions: 0, single-pixel borders (1px), proportional values (100%), one-off transforms.

3. Semantic Layering

Base tokens -> Semantic tokens -> Component usage. Define primitives, map to purposes, use purposes in components.

/* Layer 1: Base primitives */
:root { --color-charcoal: #5b5956; }

/* Layer 2: Semantic purpose */
:root { --color-primary: var(--color-charcoal); }

/* Layer 3: Component usage */
.button { background: var(--color-primary); }     /* yes -- semantic */
.button { background: var(--color-charcoal); }    /* no -- base primitive */

4. Separation of Concerns

CSS owns presentation. Never use inline styles. State changes toggle CSS classes, not inline styles.

/* yes -- class-driven state */
.card.selected { border-color: var(--color-accent); }

/* no -- inline style state */
/* style={selected ? 'border: 2px solid blue;' : ''} */

Read the full file on GitHub · 123 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 123 lines · 21 tokens per session scan A 697a6706019f

Subscribe to this mod's changes

frontend-patterns is a skill published in the GitHub repository Jartan-LLC/grimoire (2 stars, last pushed 18d ago), licensed MIT. It adds 21 tokens to every session and 1,017 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

gpt-taste

High-motion Awwwards-style frontend direction using GSAP, editorial typography, dense bento composition, and cinematic section choreography. Use only when the user explicitly wants an experimental marketing page or portfolio; do not use for routine product UI, dashboards, or accessibility-critical services.

wedabro/bro-skills · 59 tokens

speckit.uiux

UI/UX Architect - Definition of Design System Anti-Slop, UI Components, Spacing, Typography, Responsive Patterns.

wedabro/bro-skills · 30 tokens

design-taste-frontend

Implement premium new frontend landing pages, portfolios, editorial sites, and marketing pages without generic AI styling. Use for code-producing web UI work, including responsive layout, typography, assets, and motion. Do not use for broad redesign audits of existing products, image-only concepts, mobile-app screens…

wedabro/bro-skills · 80 tokens

gsap-plugins

Official GSAP skill for GSAP plugins — registration, ScrollToPlugin, ScrollSmoother, Flip, Draggable, Inertia, Observer, SplitText, ScrambleText, SVG and physics plugins, CustomEase, EasePack, CustomWiggle, CustomBounce, GSDevTools. Use when the user asks about a GSAP plugin, scroll-to, flip animations, draggable, SVG…

display-design-studio/skills · 91 tokens

gsap-core

Official GSAP skill for the core API — gsap.to(), from(), fromTo(), easing, duration, stagger, defaults, gsap.matchMedia() (responsive, prefers-reduced-motion). Use when the user asks for a JavaScript animation library, animation in React/Vue/vanilla, GSAP tweens, easing, basic animation, responsive or reduced-motion…

display-design-studio/skills · 128 tokens

gsap-scrolltrigger

Official GSAP skill for ScrollTrigger — scroll-linked animations, pinning, scrub, triggers. Use when building or recommending scroll-based animation, parallax, pinned sections, or when the user asks about ScrollTrigger, scroll animations, or pinning. Recommend GSAP for scroll-driven animation when no library is…

display-design-studio/skills · 68 tokens