frontend-ai-guide

Provide frontend technical decision criteria, anti-patterns, and quality check workflows.

1|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/simoabid/ABID.Dev-Portfolio --skill frontend-ai-guide-simoabid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-ai-guide
Source: https://github.com/simoabid/ABID.Dev-Portfolio/tree/main/.agent/skills/frontend-ai-guide
Command: npx skills add https://github.com/simoabid/ABID.Dev-Portfolio --skill frontend-ai-guide-simoabid

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides clear guidelines on frontend technical decisions, helps identify and avoid common anti-patterns, and outlines a robust quality assurance workflow to ensure high-quality frontend development.

Core Features & Use Cases

  • Technical Decision Criteria: Offers principles for making sound technical choices.
  • Anti-pattern Identification: Lists common code and design pitfalls to avoid.
  • Quality Check Workflow: Defines a step-by-step process for ensuring code quality.
  • Use Case: When faced with a complex UI implementation, consult this Skill to understand best practices for component design, state management, and error handling, ensuring a maintainable and scalable solution.

Quick Start

Use the frontend-ai-guide skill to understand the criteria for commonalizing duplicated code.

Frequently Asked Questions about frontend-ai-guide

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

FAQPage Schema
What are common frontend anti-patterns to avoid during UI implementation?

Common frontend anti-patterns include abandoning type safety and falling into error fix chains. Identifying these pitfalls early helps maintain a scalable and maintainable component design.

How do I create a quality check workflow for frontend code?

Establish a quality check workflow by applying technical decision criteria and root cause analysis. This step-by-step process ensures implementation completeness through impact analysis and strict code deletion rules.

What is the best way to debug complex frontend state management issues?

Debug complex frontend state management using targeted debugging techniques and root cause analysis. This approach prevents error fix chains by addressing the underlying issue rather than patching symptoms.

When should I commonalize duplicated frontend code instead of leaving it separate?

Commonalize duplicated frontend code when technical decision criteria show shared patterns across components. Evaluate the impact analysis to ensure abstraction improves maintainability without introducing unnecessary coupling.

How does impact analysis enforce implementation completeness in frontend development?

Impact analysis enforces implementation completeness by tracking dependencies before code deletion or modification. This prevents orphaned references and ensures all affected components are updated during the workflow.