03-ENRICH-architecture

Enforce frontend architecture standards for domain-based modular projects.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/medtrics/medtrics-acumen --skill 03-enrich-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 03-ENRICH-architecture
Source: https://github.com/medtrics/medtrics-acumen/tree/main/templates/domain-based/skills/03-ENRICH-architecture
Command: npx skills add https://github.com/medtrics/medtrics-acumen --skill 03-enrich-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive set of frontend architecture standards and conventions to ensure consistency, maintainability, and scalability in domain-based modular projects.

Core Features & Use Cases

  • Project Structure Guidance: Defines the ideal directory layout for domains, components, hooks, and services.
  • Naming Conventions: Establishes clear naming rules for files, folders, components, and hooks.
  • Domain Management: Outlines how to structure self-contained feature modules with domain.json and priority-based boundaries.
  • Service & Hook Patterns: Details best practices for data access layers and React hook implementation, including TanStack Query usage.
  • Component Hierarchy: Enforces Atomic Design principles for UI components (atoms, molecules, organisms, templates).
  • RTL, Accessibility, Performance: Provides strict guidelines for internationalization, user experience, and code optimization.
  • Use Case: When starting a new feature, use this skill to ensure the code adheres to established architectural patterns, promoting team collaboration and reducing technical debt.

Quick Start

Use the 03-ENRICH-architecture skill to define the project structure and naming conventions for the new 'user-profile' domain.

Frequently Asked Questions about 03-ENRICH-architecture

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

FAQPage Schema
How do I structure a domain-driven React project for better maintainability?

Structure a domain-driven React project by organizing directories into self-contained feature modules, using domain.json for boundaries, and applying priority-based domain management to ensure scalability and maintainability.

What are the best practices for naming files and components in a TypeScript frontend architecture?

Best practices for naming files and components in a TypeScript frontend architecture involve establishing clear, consistent rules for files, folders, React components, and hooks to enforce code standards across the project.

How does Atomic Design apply to React component hierarchy?

Atomic Design applies to React component hierarchy by enforcing strict categorization of UI components into atoms, molecules, organisms, and templates, ensuring reusable and structured frontend implementation.

Can I use TanStack Query for data fetching patterns in domain-based modules?

You can use TanStack Query for data fetching patterns in domain-based modules by implementing detailed service and React hook patterns that define best practices for the data access layer.

When do I need to implement RTL support and accessibility in frontend architecture?

Implement RTL support and accessibility in frontend architecture when establishing project standards, using strict guidelines for internationalization and user experience to ensure broad usability and compliance.

What is the best way to reduce technical debt in frontend code organization?

The best way to reduce technical debt in frontend code organization is to enforce comprehensive architecture standards covering project structure, naming conventions, and component hierarchy to promote team collaboration.