android-jetpack-compose-cursorrules-prompt-file

A set of Cursor rules for Android apps built with Jetpack Compose, Android's toolkit for describing app screens in Kotlin code. It recommends Material Design 3, clean architecture, coroutines, Flow, Hilt, ViewModels, and one-way UI state updates.

In plain words
What is it for?
Use it when building or changing Jetpack Compose screens and Android app structure, while adapting the recommendations to the project's existing layout.
Why use it?
It gives the agent a consistent approach to organising Android code and managing screen state, navigation, asynchronous work, and dependencies.

Cursor rule

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.

agentmods
npx agentmods add rules/patrickjs/awesome-cursorrules/android-jetpack-compose-cursorrules-prompt-file
Clone the repo
git clone --depth 1 https://github.com/PatrickJS/awesome-cursorrules
Per session 535 This file is loaded in full into every session.
When invoked 535 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00535 $0.00535
Opus 5 $0.00267 $0.00267
Sonnet 5 $0.00107 $0.00107
Haiku 4.5 $0.00053 $0.00053

Measured 3d ago against content hash 15d5380a40f2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

android-jetpack-compose-cursorrules-prompt-file 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 3d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

rules/android-jetpack-compose-cursorrules-prompt-file.mdc · 95 lines

What it actually says

// Android Jetpack Compose .cursorrules

// Flexibility Notice

// Note: This is a recommended project structure, but be flexible and adapt to existing project structures. // Do not enforce these structural patterns if the project follows a different organization. // Focus on maintaining consistency with the existing project architecture while applying Jetpack Compose best practices.

// Project Architecture and Best Practices

const androidJetpackComposeBestPractices = [ "Adapt to existing project architecture while maintaining clean code principles", "Follow Material Design 3 guidelines and components", "Implement clean architecture with domain, data, and presentation layers", "Use Kotlin coroutines and Flow for asynchronous operations", "Implement dependency injection using Hilt", "Follow unidirectional data flow with ViewModel and UI State", "Use Compose navigation for screen management", "Implement proper state hoisting and composition", ];

// Folder Structure

// Note: This is a reference structure. Adapt to the project's existing organization

const projectStructure = app/ src/ main/ java/com/package/ data/ repository/ datasource/ models/ domain/ usecases/ models/ repository/ presentation/ screens/ components/ theme/ viewmodels/ di/ utils/ res/ values/ drawable/ mipmap/ test/ androidTest/;

// Compose UI Guidelines

const composeGuidelines = `

  1. Use remember and derivedStateOf appropriately
  2. Implement proper recomposition optimization
  3. Use proper Compose modifiers ordering
  4. Follow composable function naming conventions
  5. Implement proper preview annotations
  6. Use proper state management with MutableState
  7. Implement proper error handling and loading states
  8. Use proper theming with MaterialTheme
  9. Follow accessibility guidelines
  10. Implement proper animation patterns `;

// Testing Guidelines

const testingGuidelines = `

  1. Write unit tests for ViewModels and UseCases
  2. Implement UI tests using Compose testing framework
  3. Use fake repositories for testing
  4. Implement proper test coverage
  5. Use proper testing coroutine dispatchers `;

// Performance Guidelines

const performanceGuidelines = `

  1. Minimize recomposition using proper keys
  2. Use proper lazy loading with LazyColumn and LazyRow
  3. Implement efficient image loading
  4. Use proper state management to prevent unnecessary updates
  5. Follow proper lifecycle awareness
  6. Implement proper memory management
  7. Use proper background processing `;
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. 3d ago First seen · 95 lines · 0 tokens per session scan A 15d5380a40f2

Subscribe to this mod's changes

android-jetpack-compose-cursorrules-prompt-file is a cursor rule published in the GitHub repository PatrickJS/awesome-cursorrules (40,694 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 535 tokens to every session, about $0.0027 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.