aiasys-frontend-architecture

What problem does it solve?

This skill resolves the inconsistency between generic frontend best practices and the actual architecture of the AIASys project, preventing developers from introducing incompatible patterns, dependencies, or structural choices that deviate from the existing codebase skeleton.

Core Features & Use Cases

• Project-Specific Architecture Rules: Clearly defines the AIASys frontend's actual tech stack, tradeoffs, and constraints, including custom manual routing, Context + Hooks state management, custom fetch-based httpClient, and conditional Feature-Folder usage.
• Development Priority Guidance: Establishes this skill as the top priority reference for AIASys frontend development, overriding generic frontend skills when conflicts arise.
• Use Case: When adding a new page, API call, or shared component to the AIASys web app, use this skill to confirm the correct directory placement, routing registration, state scope, and API usage rules to avoid refactoring overhead.

Quick Start

When developing any new frontend feature for the AIASys project, first reference this skill to confirm routing, state management, and component structure requirements before writing implementation code.