Index of every page on this site: llms.txt
All skills
dominiktobureto avatar

/frontend-ux-engineer

@9125e02
Run it yourself

Use for frontend features, Next.js/React/Vue/Svelte UI, accessibility, responsive layout, design polish, state handling, forms, visual QA, or product workflow improvements.

Use this Skill: https://skilld.dev/gh/dominiktobureto/awesome-grok-build/frontend-ux-engineer

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈49 tokens for metadata: the name and description. ≈397 when used: this file.

Description uses 2.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈195 characters, or 2.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Frontend UX Engineer

Build usable product screens, not decorative demos.

Grok Build Mode

  • Use Plan Mode for new screens, navigation changes, data-fetching patterns, or design-system changes.
  • Use subagents for larger UI work:
    • workflow: user task and states.
    • component: existing design system and reusable components.
    • accessibility: keyboard, labels, contrast, semantics.
    • visual: responsive layout, overflow, polish.
  • Arena-style design: compare 2-3 UI approaches and pick the one that best supports the target workflow.
  • Human-in-the-loop: ask before introducing UI libraries, animation systems, or design tokens.

Workflow

  1. Identify target user, primary task, and success state.
  2. Inspect existing components, styling, routing, and data layer.
  3. Build the actual usable experience as the first screen.
  4. Include loading, empty, error, and success states.
  5. Verify mobile and desktop layouts.
  6. Run lint/type/test/build checks when available.

UI Rules

  • Do not create a landing page unless requested.
  • Keep text inside containers at all viewport sizes.
  • Use semantic controls and accessible names.
  • Avoid fake metrics and placeholder dashboards.
  • Prefer existing component patterns.
  • Make forms resilient: validation, disabled states, error recovery.

Example Prompts

Use frontend-ux-engineer. Build this dashboard workflow with loading, empty, error, and success states. Verify responsive layout.
Review this UI with subagents for workflow, components, accessibility, and visual polish before editing.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts4mo3 checks · Risk SAFE
  • Gen Agent Trust Hub4mo

    No security issues detected. This skill contains purely instructional content for frontend development and user experience engineering with no executable code or dangerous patterns.

  • Socket4mo

    No alerts

  • Snyk4mo

    Risk: LOW · No issues

Signed by skilld at 9125e02. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated 6 months ago
version
1.0.0
author
awesome-grok-build

README badge

README badge for dominiktobureto/awesome-grok-build/frontend-ux-engineer