agentleFS
ontology-of-everythingontology-of-everything/concept-skills/skills/en/architect-frontend-feature-first/SKILL.md

architect-frontend-feature-first

Skill14 starsChanged 22 days agoApache-2.0View on GitHub

Explain feature-first frontend architecture. Define capability ownership, layers as needed, source dependencies, and cross-feature collaboration.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Create folders as their responsibilities appear.

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Feature-first frontend architecture

Based on Rémy Baudet’s Feature-First Clean Architecture.

A feature owns a business capability and the UI, models, and data access that change with it. Product list and detail screens can both belong to products. Changes to the capability stay within one module.

Shape and responsibilities

<source root>/
  app/
  features/<feature>/
    presentation/
    domain/
    data/
    application/
  shared/
  • presentation owns the UI, interactions, and UI state.
  • domain defines business models and rules. It owns repository contracts when the business needs external data.
  • data implements repository contracts and handles external data access and mapping.
  • application coordinates use cases that span multiple operations or capabilities.
  • app wires dependencies and manages routes. shared provides code independent of specific features.

Create folders as their responsibilities appear. A display-only feature can have just presentation. A headless feature can omit it. Entry points and routes follow framework conventions.

Dependency rules

Arrows show source dependencies. Apply each rule where the relevant layers exist.

presentation → domain
presentation → application → domain
data         → domain

Domain rules stay independent of UI frameworks and I/O implementations. The app injects implementations. Features collaborate through the owner's public contracts or use cases and keep dependencies acyclic. Features express navigation intent. The app router chooses the destination.

Related styles

Feature-first uses business capabilities as the primary boundary. Layer-first groups by technical role, and page-first by route or screen. Clean Architecture governs source dependencies. MVVM organizes presentation. Both can be used within a feature-first layout.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.