Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/chohra-med/expo_boilerplatenpx agentmods add rules/chohra-med/expo_boilerplate/app_feature_first_architectureWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/chohra-med/expo_boilerplate/app_feature_first_architecture)<a href="https://agentmods.dev/rules/chohra-med/expo_boilerplate/app_feature_first_architecture"><img src="https://agentmods.dev/badge/rules/chohra-med/expo_boilerplate/app_feature_first_architecture/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/chohra-med/expo_boilerplate/app_feature_first_architecture"><img src="https://agentmods.dev/badge/rules/chohra-med/expo_boilerplate/app_feature_first_architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.06279 | $0.06279 |
| Opus 5 | $0.03139 | $0.03139 |
| Sonnet 5 | $0.01256 | $0.01256 |
| Haiku 4.5 | $0.00628 | $0.00628 |
Grade A, and why
app_feature_first_architecture scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 940 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature-First Architecture Guide
Overview
Feature-first architecture is a design pattern that organizes code by business features rather than technical layers. This approach promotes better maintainability, scalability, and team collaboration by keeping related functionality together and reducing coupling between different parts of the application.
Core Principles
1. Feature Isolation
- Each feature is self-contained with its own components, logic, and state
- Features communicate through well-defined interfaces
- Minimal dependencies between features
- Clear boundaries and responsibilities
2. Shared Resources
- Common functionality is extracted to shared directories
- UI components, utilities, and services are globally accessible
- Consistent patterns across all features
3. Scalability
- Easy to add new features without affecting existing ones
- Clear structure for team members to work independently
- Simple to remove or refactor features
Project Structure
src/
├── features/ # Feature-specific code
│ ├── auth/ # Authentication feature
│ │ ├── api/ # API calls and endpoints
│ │ ├── components/ # Feature-specific components
│ │ ├── hooks/ # Custom hooks
│ │ ├── screens/ # Screen components
│ │ ├── services/ # Business logic
│ │ ├── store/ # State management
│ │ └── types/ # Type definitions
│ ├── media-library/ # Media management feature
│ ├── collections/ # Collections feature
│ └── settings/ # Settings feature
├── navigation/ # Navigation configuration
│ ├── navigators/ # Navigator components
│ ├── routes.ts # Route definitions
│ └── routes.types.ts # Navigation types
├── services/ # Global services
│ ├── api/ # API configuration
│ ├── datadog/ # Monitoring service
│ └── logging/ # Logging services
├── store/ # Global store configuration
│ ├── store.ts # Store setup
│ ├── reducers.ts # Root reducer
│ └── app.slice.ts # App-level state
├── ui/ # Shared UI components
│ ├── components/ # Reusable components
│ ├── style/ # Theme and styling
│ └── tokens/ # Design tokens
├── utils/ # Utility functions
├── schemas/ # Data validation schemas
├── config/ # Configuration files
└── entrypoints/ # App entry points
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 940 lines · 6,279 tokens per session scan A 559478eda681
app_feature_first_architecture is a cursor rule published in the GitHub repository chohra-med/expo_boilerplate (33 stars, last pushed 9d ago), licensed MIT. It adds 6,279 tokens to every session, about $0.0314 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other cursor rules, from other repositories
coding-guidelines
React Native Expo SDK 54 project with TypeScript, Expo Router v6, Redux Toolkit, and modern development practices.
library-conventions
React Native library conventions for this starter. Apply when creating or editing components, hooks, types, or tests in src/.
error-handling
Error boundaries, loading states, and server error handling.
ai-collaboration
Instructions for AI agent code generation workflow.
api-validation
API route validation — enforces Zod validation on all route handlers and server actions.
file-uploads
Image and file upload patterns — prevents insecure client-side uploads and missing file validation.