architect-frontend-feature-first-cn
Skill14 starsChanged 22 days agoApache-2.0View on GitHub
解释功能优先前端架构。按业务能力确定归属,按需分层,明确源码依赖和跨功能协作。
1 other project uses a version of this.
Adopted by
Most recently taken up by
- ontology-of-everything/concept-skillsword for word, first seen Nov 15, 2026
Other versions1 project uses a version of this.
Word for word · 1
- ontology-of-everything/concept-skills★ 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-feature-firstSkill
- 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-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
Files
功能优先前端架构
参考 Rémy Baudet 的 Feature-First Clean Architecture。
一个功能拥有一项业务能力及随它变化的界面、模型和数据访问。商品列表与详情可以同属 products。这样的划分让功能变更集中在一个模块内。
形状与职责
<源码根>/
app/
features/<feature>/
presentation/
domain/
data/
application/
shared/presentation负责界面、交互和界面状态。domain定义业务模型和规则。业务需要外部数据时,由这里定义仓库契约。data实现仓库契约,负责外部数据访问和转换。application编排需要协调多个操作或业务能力的用例。app装配依赖并管理路由。shared提供与具体功能无关的通用代码。
按实际职责创建目录。纯展示功能可只有 presentation。无界面功能可省去展示层。入口和路由沿用框架约定。
依赖规则
箭头表示源码依赖,相关层存在时才应用对应规则。
presentation → domain
presentation → application → domain
data → domain领域规则独立于界面框架和 I/O 实现。应用入口注入实现。跨功能业务协作使用所有者公开的契约或用例,保持依赖无环。功能表达导航意图,应用路由选择目标。
与其他风格的区别
Feature-first 选择业务能力作为一级边界。Layer-first 优先按技术职责归档,页面优先围绕路由或屏幕归档。Clean Architecture 约束源码依赖,MVVM 组织展示层。二者都可与 Feature-first 组合。
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.

