Building a React starter with enforceable architecture

Описание и применение

Создан шаблон JST, который определяет архитектурные слои и применяет правила ESLint для обеспечения чистой структуры в React‑приложениях.

Задача

Developers struggle to maintain clean architecture and enforce boundaries in growing React applications.

Результат

The JST template enforces architectural boundaries, reduces code coupling, and provides mechanical checks that help developers maintain a clean structure as projects grow.

Рабочий процесс

• 1. Define architectural layers: Pages, Features, Entities, External effects, Concrete implementations.
• 2. Create a template with conventional tooling (React, TypeScript, SSR, routing, tests).
• 3. Add ESLint rules and repository checks to enforce boundary violations.
• 4. Separate architecture rules from general code‑quality rules into plugins.
• 5. Provide generators for entities, features, widgets, modules, and packages to establish boundaries at creation.
• 6. Run diagnostics in editor, pre‑commit, and CI to reject violations and explain expected routes.
• 7. Offer a project‑local MCP server for coding agents to receive architecture context and bounded checks.

Доказательства

I started converting the rules that could be checked mechanically into ESLint rules and repository checks. They now run in the editor, before a commit, and in CI.

Источник

JST includes generators for entities, features, widgets, modules, and packages. Their purpose is not to save a few keystrokes. They create the smallest valid public API and dependency shape so that a developer starts from a known state.

Источник

The first evaluation was not flattering to JST. Under the original time limit, the control setup completed five of five retained runs, while JST completed one of five retained runs.

Источник