project_overview_template

project_overview_template is a cursor rule for Cursor from moclam1905/CocktailRecipes. It costs 13 tokens per session (4,553 once invoked), scanned A, original, MIT.

A template for documenting the architecture of an Android application built with Kotlin and Jetpack Compose. It describes layers, modules, and common patterns such as MVVM and dependency injection.

In plain words
What is it for?
Use it to document or plan Android projects with separate app, data, domain, core, and feature modules.
Why use it?
It gives feature work a consistent view of where code belongs and how the application is organized.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it to document or plan Android projects with separate app, data, domain, core, and feature modules.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/moclam1905/cocktailrecipes/project_overview_template
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/moclam1905/CocktailRecipes

Made for: Cursor.

Wrote 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.

agentmods badge for project_overview_template

README.md
[![agentmods](https://agentmods.dev/badge/rules/moclam1905/cocktailrecipes/project_overview_template/github.svg)](https://agentmods.dev/rules/moclam1905/cocktailrecipes/project_overview_template)
Your own site
<a href="https://agentmods.dev/rules/moclam1905/cocktailrecipes/project_overview_template"><img src="https://agentmods.dev/badge/rules/moclam1905/cocktailrecipes/project_overview_template/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.

agentmods 80×15 button for project_overview_template

Your own site · 80×15
<a href="https://agentmods.dev/rules/moclam1905/cocktailrecipes/project_overview_template"><img src="https://agentmods.dev/badge/rules/moclam1905/cocktailrecipes/project_overview_template.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,553 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00013 $0.04553
Opus 5.5 $0.00005 $0.01821
Sonnet 5.5 $0.00003 $0.00911
Haiku 4.5 $0.00001 $0.00455

Measured 2mo ago against content hash fbd9751dd5a6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

project_overview_template 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 2mo 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.

.cursor/rules/android-kotlin-compose-rules/project_overview_template.mdc · 282 lines

How it starts

The opening of the file, as written. The whole thing — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Project Overview Template

This project is a modern Android application built with Kotlin and Jetpack Compose, following a Clean Architecture approach. The architecture emphasizes separation of concerns, modular code organization, and use of Android best practices (MVVM, dependency injection with Hilt, etc.) to create a scalable and maintainable codebase.

Project Structure

The project is organized into multiple Gradle modules to enforce clear layering and feature separation:

ProjectName/
├── app/                   - Android app module (application entry point, UI composition, navigation)
├── domain/                - Domain layer (business logic: use cases, domain models, repository interfaces)
├── data/                  - Data layer (implementation of repositories, network services, database access)
├── core/                  - Core utilities (common code such as UI theming, extensions, constants) *optional*
├── feature_login/         - Feature module: Login (UI screens and ViewModel for user authentication)
├── feature_dashboard/     - Feature module: Dashboard (UI and logic for the dashboard feature)
└── buildSrc/              - Build script module (Gradle Kotlin DSL for dependency versions and build logic)

Each feature of the app (e.g., login, dashboard, etc.) can be implemented in its own module (like feature_login, feature_dashboard above), which depends on the core, domain, and data modules. This modular structure improves encapsulation and build times, and makes it easier to scale the codebase.

Key Patterns & Concepts

  1. Clean Architecture (Layered Architecture): The codebase is divided into layers (presentation, domain, data) to separate concerns:

    • Presentation layer (UI): Contains Android-specific code, Jetpack Compose UI, ViewModels. Depends on the domain layer.

    • Domain layer: Contains enterprise logic, use case classes, and domain models. This layer is independent of any Android framework or library.

Read the full file on GitHub · 282 lines

Changes

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.

  1. 2mo ago First seen · 282 lines · 4,553 tokens per session scan A fbd9751dd5a6

Subscribe to this mod's changes

project_overview_template is a cursor rule published in the GitHub repository moclam1905/CocktailRecipes (1 stars, last pushed 1y ago), licensed MIT. It adds 13 tokens to every session and 4,553 once invoked, about $0.0001 per session on Opus 5.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-31.

Related

Other cursor rules, from other repositories

ios-project-onboarding

Walks a new developer through one-time setup of an EXISTING configured iOS project from a blank macOS install — Xcode, Fastlane, SPM dependencies, code signing, simulator, and a smoke-test build. Assumes App Store Connect + Firebase + Fastlane are already configured upstream; user just needs local toolchain +…

JoDaBaRo/agentic-mobile-rules · 182 tokens

compose-core

Modern Android development rules: Kotlin 2.x with K2, Jetpack Compose, Material 3, state hoisting + StateFlow + collectAsStateWithLifecycle, Hilt with hiltViewModel(), type-safe Navigation Compose, KSP, Version Catalogs, Compose Compiler as Kotlin plugin.

RoninForge/roninforge-kotlin-compose · 2,288 tokens

compose-architecture

Android architecture patterns: feature modularization, repository + data source pattern, sealed interfaces for UI state, ViewModel + StateFlow, Ktor / Retrofit + Kotlin Serialization, Room with Flow returns + KSP, coroutines structured concurrency.

RoninForge/roninforge-kotlin-compose · 0 tokens

android

Coding rules for native Android applications, including Kotlin, Jetpack Compose, and common application architecture patterns. Android is Google’s mobile operating system; Kotlin is a programming language commonly used for it, and Jetpack Compose is a toolkit for building screens.

flyeric0212/cursor-rules · 1,831 tokens

android_bak

A set of conventions and recommended practices for native Android development using Kotlin, Java, and Jetpack Compose, Android's toolkit for building user interfaces.

flyeric0212/cursor-rules · 1,067 tokens

python

A set of rules for native Android development, including Kotlin, Jetpack Compose, and architecture patterns. Kotlin is a programming language, and Jetpack Compose is Android’s toolkit for building interfaces in code.

flyeric0212/cursor-rules · 314 tokens