performance-optimization

A set of rules for improving the speed and resource use of Android Compose applications. It covers screen updates, memory, network requests, app startup, and background work.

In plain words
What is it for?
Use it when tuning Compose screens, handling large datasets or images, reducing API work, improving offline behavior, or shortening app startup.
Why use it?
It helps avoid unnecessary screen redraws, memory leaks, slow network use, and long launch times.

Cursor rule for Cursor

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/heegyeong/composesample/performance-optimization
Clone the repo
git clone --depth 1 https://github.com/HeeGyeong/ComposeSample

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 132 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.00132
Opus 5 $0.00000 $0.00066
Sonnet 5 $0.00000 $0.00026
Haiku 4.5 $0.00000 $0.00013

Measured yesterday against content hash 0c5c42c695d0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

performance-optimization 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 yesterday.

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/performance-optimization.mdc · 31 lines

What it actually says

Performance Optimization Guide

Compose Optimization

  • Use remember/derivedStateOf appropriately
  • Minimize LaunchedEffect scope
  • Prevent unnecessary recompositions
  • Optimize key usage

Memory Management

  • Cache image resources
  • Prevent memory leaks
  • Manage background tasks
  • Implement pagination for large datasets

Network Optimization

  • Image compression and caching
  • Cache API responses
  • Use batch requests
  • Implement offline-first strategy

App Launch Optimization

  • Minimize cold start time
  • Implement lazy initialization
  • Process heavy tasks in background
  • Optimize screen transitions
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. yesterday First seen · 31 lines · 0 tokens per session scan A 0c5c42c695d0

Subscribe to this mod's changes

performance-optimization is a cursor rule published in the GitHub repository HeeGyeong/ComposeSample (11 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 132 tokens. 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.