frontend-ui-engineering

frontend-ui-engineering is a skill for Claude Code, Cursor from mamahoos/dot-files. It costs 58 tokens per session (2,748 once invoked), scanned A, a copy of frontend-ui-engineering, MIT.

A guide for building polished interfaces that people use directly, such as web pages, forms, and interactive components, across different screen sizes.

In plain words
What is it for?
Use it to create or change responsive layouts, UI components, interactions, accessibility features, and application state.
Why use it?
It helps prevent interfaces that are difficult to use, inaccessible, inconsistent, or unfinished-looking.

Skill for Claude CodeCursor

Written for Claude Code and Cursor: disable-model-invocation in frontmatter, but also installed under .cursor/.

Good fit Use it to create or change responsive layouts, UI components, interactions, accessibility features, and application state.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mamahoos/dot-files/frontend-ui-engineering
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.

Any agent
npx skills add mamahoos/dot-files --skill frontend-ui-engineering
Clone the repo
git clone --depth 1 https://github.com/mamahoos/dot-files

Made for: Claude Code, Cursor.

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-ui-engineering

README.md
[![agentmods](https://agentmods.dev/badge/skills/mamahoos/dot-files/frontend-ui-engineering/github.svg)](https://agentmods.dev/skills/mamahoos/dot-files/frontend-ui-engineering)
Your own site
<a href="https://agentmods.dev/skills/mamahoos/dot-files/frontend-ui-engineering"><img src="https://agentmods.dev/badge/skills/mamahoos/dot-files/frontend-ui-engineering/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for frontend-ui-engineering

Your own site · 80×15
<a href="https://agentmods.dev/skills/mamahoos/dot-files/frontend-ui-engineering"><img src="https://agentmods.dev/badge/skills/mamahoos/dot-files/frontend-ui-engineering.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,748 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 97% copy Near-identical to another mod 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.00058 $0.02748
Opus 5.5 $0.00023 $0.01099
Sonnet 5.5 $0.00012 $0.00550
Haiku 4.5 $0.00006 $0.00275

Measured 12d ago against content hash a79be10d11a6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

frontend-ui-engineering 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 12d 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.

Origin

This is a copy

97% identical to frontend-ui-engineering — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

home/.cursor/skills/frontend-ui-engineering/SKILL.md · 342 lines

How it starts

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

Frontend UI Engineering

Overview

Build production-quality user interfaces that are accessible, performant, and visually polished. The goal is UI that looks like it was built by a design-aware engineer at a top company — not like it was generated by an AI. This means real design system adherence, proper accessibility, thoughtful interaction patterns, and no generic "AI aesthetic."

When to Use

  • Building new UI components or pages
  • Modifying existing user-facing interfaces
  • Implementing responsive layouts
  • Adding interactivity or state management
  • Fixing visual or UX issues

Component Architecture

File Structure

Colocate everything related to a component:

src/components/
  TaskList/
    TaskList.tsx          # Component implementation
    TaskList.test.tsx     # Tests
    TaskList.stories.tsx  # Storybook stories (if using)
    use-task-list.ts      # Custom hook (if complex state)
    types.ts              # Component-specific types (if needed)

Component Patterns

Prefer composition over configuration:

// Good: Composable
<Card>
  <CardHeader>
    <CardTitle>Tasks</CardTitle>
  </CardHeader>
  <CardBody>
    <TaskList tasks={tasks} />
  </CardBody>
</Card>

// Avoid: Over-configured
<Card
  title="Tasks"
  headerVariant="large"
  bodyPadding="md"
  content={<TaskList tasks={tasks} />}
/>

Keep components focused:

// Good: Does one thing
export function TaskItem({ task, onToggle, onDelete }: TaskItemProps) {
  return (
    <li className="flex items-center gap-3 p-3">
      <Checkbox checked={task.done} onChange={() => onToggle(task.id)} />
      <span className={task.done ? 'line-through text-muted' : ''}>{task.title}</span>
      <Button variant="ghost" size="sm" onClick={() => onDelete(task.id)}>
        <TrashIcon />
      </Button>
    </li>
  );
}

Separate data fetching from presentation:

// Container: handles data
export function TaskListContainer() {
  const { tasks, isLoading, error, refetch } = useTasks();

  if (isLoading) return <TaskListSkeleton />;
  if (error) return <ErrorState message="Failed to load tasks" retry={refetch} />;
  if (tasks.length === 0) return <EmptyState message="No tasks yet" />;

  return <TaskList tasks={tasks} />;
}

// Presentation: handles rendering
export function TaskList({ tasks }: { tasks: Task[] }) {
  return (
    <ul role="list" className="divide-y">
      {tasks.map(task => <TaskItem key={task.id} task={task} />)}
    </ul>
  );
}

Read the full file on GitHub · 342 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. 12d ago Changed a79be10d11a6
  2. 1mo ago Changed · +12 lines b68ac4d7a207
  3. 1mo ago First seen · 330 lines · 58 tokens per session scan A 1277a46f6b00

Subscribe to this mod's changes

frontend-ui-engineering is a skill published in the GitHub repository mamahoos/dot-files (5 stars, last pushed 2d ago), licensed MIT. It adds 58 tokens to every session and 2,748 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to frontend-ui-engineering, differing in 1 line, and is treated as a copy.

Related

Other skills, from other repositories

ui-review-tahoe

Comprehensive UI/UX review for macOS Tahoe apps. Covers Liquid Glass design, HIG compliance, SwiftUI patterns, and accessibility. Use when reviewing macOS UI or checking HIG compliance.

freekmurze/dotfiles · 46 tokens

visual-design-system

Visual design principles, colour, typography, layout, and spatial composition for Cowboys & Beans projects. Use when: designing web pages or components, choosing colours, setting up type scales, composing layouts, writing CSS, building design tokens, creating fluid responsive designs, reviewing visual quality…

Mte90/dotfiles · 87 tokens

design-taste-frontend

Senior UI/UX Engineer. Architect digital interfaces overriding default LLM biases. Enforces metric-based rules, strict component architecture, CSS hardware acceleration, and balanced design engineering.

Mte90/dotfiles · 40 tokens

responsive-design

Implement modern responsive layouts using container queries, fluid typography, CSS Grid, and mobile-first breakpoint strategies. Use when building adaptive interfaces, implementing fluid layouts, or creating component-level responsive behavior.

Mte90/dotfiles · 40 tokens

design-system-patterns

Build scalable design systems with design tokens, theming infrastructure, and component architecture patterns. Use when creating design tokens, implementing theme switching, building component libraries, or establishing design system foundations.

Mte90/dotfiles · 42 tokens

high-end-visual-design

Teaches the AI to design like a high-end agency. Defines the exact fonts, spacing, shadows, card structures, and animations that make a website feel expensive. Blocks all the common defaults that make AI designs look cheap or generic.

Mte90/dotfiles · 53 tokens