Agent skill

architecture-feature-first

Use when creating a feature, designing folder structure, adding repositories/services/view models, wiring dependency injection, or deciding which layer owns logic.

evancagithub.com/evancaGitHub ↗
claude-codecodexcursorwindsurfMIT
Install
npx skills add evanca/flutter-ai-rules --skill architecture-feature-first --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 7 KB
Bundled scripts: none
Path: skills/architecture-feature-first/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 604
Language: Shell

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Flutter Architecture — Feature-First Skill This skill defines how to design, structure, and implement Flutter applications using the recommended **layered architecture** with **feature-first** file organization. It is **state management agnostic**: the business logic holder in the UI layer may be named ViewModel, Controller, Cubit, Bloc, Provider, or Notifier — depending on the chosen state management approach. The architectural rules apply equally to all of them. ## When to Use Use this skill when: * Designing the folder/file structure of a new Flutter app or feature. * Creating a new View, ViewModel, Repository, or Service. * Deciding which layer owns a piece of logic. * Wiring dependency injection between components. * Adding a domain (logic) layer for complex business logic. * Refactoring an existing app from type-first to feature-first organization. --- ## 1. Layers Separate every app into a **UI Layer** and a **Data Layer**. Add a **Logic (Domain) Layer** between them only for complex apps. ``` ┌──────────────────────────────────────────────────────────────┐ │ UI Layer │ Views + business logic holders │ │ │ (ViewModel / Cubit / Controller / Provider) │ ├────────────────────

What's inside
Steps it walks through
  1. When to Use
  2. 1. Layers
  3. 2. Feature-First File Structure
  4. Sample directory structure
  5. 3. Component Responsibilities
  6. View
  7. Business Logic Holder (ViewModel / Cubit / Controller / Provider)
  8. Repository
  9. Service
  10. 4. Domain Layer (Use Cases)
  11. 5. Dependency Injection
  12. 6. Workflow: Add a New Feature
  13. References
More from flutter-ai-rules
All skills →
About this skill
What does the architecture-feature-first skill do?

Use when creating a feature, designing folder structure, adding repositories/services/view models, wiring dependency injection, or deciding which layer owns logic.

How do I install it?

Run `npx skills add evanca/flutter-ai-rules --skill architecture-feature-first --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From evanca/flutter-ai-rules, a repository with 604 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going