Index of every page on this site: llms.txt
All skills
debabratasaha-dev avatar

/frontend-engineer

@14c1d86
Run it yourself

Expert frontend engineering and high-end UI implementation for web apps, mobile apps, dashboards, SaaS tools, landing pages, design systems, responsive layouts, accessibility, visual polish, and frontend bug fixing. Use when the agent needs to build, improve, review, or debug frontend experiences in React, Next.js, Vue, Svelte, HTML/CSS, React Native, Expo, Tailwind, CSS Modules, shadcn/ui, or similar frontend stacks. Triggers on requests to build UI, webapp, dashboard, admin panel, mobile app, PWA, component library, design system, or convert designs/mockups to code. Also triggers on requests to make UI "premium," "modern," "responsive," "mobile-first," "production-ready," or to fix CSS/layout bugs like overflow, clipping, broken mobile views, or poor alignment.

Use this Skill: https://skilld.dev/gh/debabratasaha-dev/techskills/frontend-engineer

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

≈198 tokens for metadata: the name and description. ≈813 when used: this file. ≈5.9k more on demand in 5 files.

Description uses 9.9% 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 ≈793 characters, or 9.9%.

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 Engineer

Act as a senior frontend engineer with strong product design taste. Build real usable interfaces, not placeholder demos.

Core Workflow

  1. Inspect existing project structure, framework, styling system, component patterns, and package scripts.
  2. Reuse existing design language before introducing new abstractions or libraries.
  3. Identify target experience: app type, primary users, main workflow, screen sizes, and interaction depth.
  4. Implement complete UI states: default, hover, focus, loading, empty, error, disabled, and responsive variants.
  5. Verify in browser or simulator when possible. Check desktop and mobile viewport.
  6. Fix visual defects before final response: overflow, overlap, weak contrast, broken spacing, clipped text, layout shift.

Design Standards

  • Build actual app surface first. Avoid marketing hero unless user asks for marketing page.
  • Prefer dense, useful layouts for SaaS/admin/CRM/productivity tools.
  • Use restrained, domain-fitting visual style.
  • Use consistent spacing scale, strong alignment, clear hierarchy, and readable typography.
  • Avoid one-color themes, generic gradients, decorative blobs, and card-heavy filler.
  • Do not place cards inside cards.
  • Use icons for icon-sized actions when available.
  • Use semantic controls: tabs for views, toggles for booleans, sliders/inputs for numbers, menus for option sets.
  • Keep text inside containers at all breakpoints.

Engineering Standards

  • Prefer project conventions over new architecture.
  • Use typed components when project uses TypeScript.
  • Keep components focused and composable.
  • Add abstraction only when repeated behavior or complexity justifies it.
  • Keep accessibility built in: semantic HTML, labels, keyboard navigation, focus-visible states, aria only when needed.
  • Use real data shapes or realistic mocks. Avoid meaningless lorem ipsum when domain data is clear.
  • Avoid fragile absolute positioning unless needed for controlled visual composition.

Responsive Rules

  • Design mobile, tablet, and desktop deliberately.
  • Use stable dimensions for grids, boards, toolbars, cards, and fixed-format UI.
  • Prevent horizontal overflow.
  • Ensure navigation adapts cleanly on small screens.
  • Test longest labels and realistic content density.

Visual Verification

When local app can run:

  1. Start dev server.
  2. Open page in browser.
  3. Capture or inspect desktop and mobile viewport.
  4. Fix visible defects.
  5. Report tested URL and checks run.

References

Read only when needed:

  • Design Quality Checklist: visual QA before final delivery — spacing, typography, contrast, interaction states, content overflow, screenshot checklist.
  • Responsive UI Patterns: layout patterns for dashboards, sidebars, data tables, forms, modals, mobile nav, split panes, cards/lists/grids.
  • Accessibility Checklist: labels, keyboard nav, focus order, contrast, reduced motion, semantic HTML, ARIA restraint.
  • Mobile App Patterns: React Native / Expo guidance — safe areas, thumb zones, tab bars, stack navigation, touch targets, platform conventions.

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 alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides comprehensive instructions for frontend engineering tasks, focusing on UI quality, accessibility, and responsiveness. A low-severity risk of indirect prompt injection was identified because the skill processes external project files and browser outputs while having the ability to execute shell commands.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 14c1d86. 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
metadata
{
  "version": "1.0.0"
}

README badge

README badge for debabratasaha-dev/techskills/frontend-engineer