senior-frontend-engineer

Enforce senior-level frontend engineering standards across React codebases.

1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/iAmAdheil/DSP_TARA --skill senior-frontend-engineer-iamadheil
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: senior-frontend-engineer
Source: https://github.com/iAmAdheil/DSP_TARA/tree/main/.claude/skills/senior-frontend-engineer
Command: npx skills add https://github.com/iAmAdheil/DSP_TARA --skill senior-frontend-engineer-iamadheil

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforce senior-level frontend engineering standards to reduce ad-hoc coding, improve maintainability, and ensure production-quality guardrails across architecture, components, hooks, and testing.

Core Features & Use Cases

  • Architecture-first approach to frontend feature implementation and refactoring.
  • Enforced directory structure and design-system usage to maintain consistency.
  • Quality gates for testing, linting, and maintainability; clear guidelines for file size, complexity, and naming.
  • Use Cases: when starting a new feature, refactoring legacy code, performing architecture reviews.

Quick Start

Before coding, define page data contracts and baseline architecture to enforce consistency.

Frequently Asked Questions about senior-frontend-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce frontend architecture standards during a React project refactor?▼

Enforce frontend architecture standards by applying architecture-first quality guardrails to React refactors, ensuring predictable directory structure, design-system usage, and maintainable code across components and hooks.

What is the best way to establish maintainability guardrails for new frontend features?▼

The best way to establish maintainability guardrails is to define page data contracts and baseline architecture before coding, applying quality gates for testing, linting, file size, and complexity.

Can I use these quality guardrails for architecture reviews in existing React codebases?▼

Yes, you can use these quality guardrails for architecture reviews in existing React codebases to reduce ad-hoc coding, enforce naming guidelines, and ensure production-quality standards across components and hooks.

How do I prevent ad-hoc coding and ensure consistent design-system usage in frontend development?▼

Prevent ad-hoc coding by enforcing senior-level frontend engineering standards that mandate design-system usage, dictate directory structure, and impose strict quality gates for testing and linting.

Do I need to define data contracts before coding to enforce frontend quality?▼

Yes, you need to define page data contracts and baseline architecture before coding to enforce consistency, establish clear maintainability guidelines, and ensure predictable quality across the codebase.