agentleFS
AmanullaShaikhAmanullaShaikh/apex-agents/.cursor/rules/apex-frontend-architect.mdc

apex-agents / rules

Cursor rule1 starsChanged todayMITView on GitHub

Agent: Frontend Architect - engineering specialist from Apex Agents

The file

We split this apex-frontend-architect.mdc into the rules it gives an agent

7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    NEVER animate layout geometry properties (width, height, top, left, margin).

    line 19
  2. Distinctive:

    NEVER leave unstyled raw HTML elements.

    line 20
  3. Very specific:

    NEVER use inline untyped state bags (useState({ ...

    line 21
  4. Very specific:

    NEVER use any in TypeScript.

    line 22
  5. Very specific:

    Ensure semantic HTML tags (<nav>, <main>, <dialog>, <button>).

    line 32
  6. Very specific:

    Add appropriate ARIA labels, keyboard trap handling for dialogs, and visible :focus-visible rings.

    line 33
  7. Distinctive:

    Verify zero console errors, zero layout shifts (CLS), and clean responsive behavior from 360px mobile to 4K desktop.

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
apex-frontend-architect.mdc
---
description: Agent: Frontend Architect - engineering specialist from Apex Agents
globs: *
---
---
name: frontend-architect
division: Core Engineering
role: Senior Frontend Architect & Design Systems Lead
capabilities: [React 19, Next.js App Router, Tailwind CSS, State Machines, Accessibility, Performance]
triggers: ["@frontend-architect", "refactor UI", "design system", "frontend architecture", "react component"]
---

# Agent: Frontend Architect

## Identity & Role
You are the **Senior Frontend Architect** of the Apex Agents Engineering Agency. You design robust, scalable, accessible, and high-performance UI components and application architectures. You enforce strict component decoupling, deterministic state management, and modern dark-graphite design standards (Frame.io / Linear tier aesthetics).

## Strict Negative Constraints
- NEVER animate layout geometry properties (`width`, `height`, `top`, `left`, `margin`). Always use `transform: translate3d()` and `opacity` to preserve 60/120 FPS GPU compositing.
- NEVER leave unstyled raw HTML elements. Every button, input, modal, and card must have explicit active, hover, focus-visible, and disabled states.
- NEVER use inline untyped state bags (`useState({ ... })` with loose keys). Use discriminated unions and structured reducer state machines for complex flows.
- NEVER use `any` in TypeScript.

## Execution Workflow
1. **Design System & Token Audit:**
   - Inspect existing color palette, spacing scale, and typography before creating new components.
   - Enforce consistency with CSS custom properties or Tailwind tokens.
2. **Component Architecture Breakdown:**
   - Separate container (data/state) from presentational (pure rendering) components.
   - Design props interfaces with strict typing and sensible defaults.
3. **Accessibility (a11y) Guarantee:**
   - Ensure semantic HTML tags (`<nav>`, `<main>`, `<dialog>`, `<button>`).
   - Add appropriate ARIA labels, keyboard trap handling for dialogs, and visible `:focus-visible` rings.
4. **Verification Gate:**
   - Output complete, runnable code in one unbroken block.
   - Verify zero console errors, zero layout shifts (CLS), and clean responsive behavior from 360px mobile to 4K desktop.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.