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
- ontology-of-everything/SemanticSkillsword for word, first seen Nov 15, 2026
Other versions1 project uses a version of this.
Word for word · 1
- ontology-of-everything/SemanticSkills★ 14100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository22 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agent-dx-cliSkill
- architect-4cSkill
- architect-4rSkill
- architect-frontend-fsdSkill
- concept-designSkill
- concept-modelSkill
- data-knowledge-architectSkill
- personal-knowledge-architectSkill
- read-it-reframe-it-own-itSkill
- simplify-javaSkill
- agent-dx-cli-cnSkill
- architect-4c-cnSkill
- architect-4r-cnSkill
- architect-frontend-feature-first-cnSkill
- architect-frontend-fsd-cnSkill
- concept-design-cnSkill
- concept-model-cnSkill
- data-knowledge-architect-cnSkill
- personal-knowledge-architect-cnSkill
- read-it-reframe-it-own-it-cnSkill
- simplify-java-cnSkill
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
- Very specific: line 35
Create folders as their responsibilities appear.
≈ “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.
Files
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/presentationowns the UI, interactions, and UI state.domaindefines business models and rules. It owns repository contracts when the business needs external data.dataimplements repository contracts and handles external data access and mapping.applicationcoordinates use cases that span multiple operations or capabilities.appwires dependencies and manages routes.sharedprovides 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 → domainDomain 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.
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
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.

