agentleFS
anandartinanandartin/celestial-skills/skills/compose-android-app-engineering/AGENTS.md

celestial-skills / compose-android-app-engineering

AGENTS.md1 starsChanged 18 days agoApache-2.0View on GitHub

A native Android app in Kotlin with declarative UI, one-way data flow and screenshot plus journey tests. When a Celestial experience skill is in use, give each journey one end-to-end test (happy path plus its error and empty states) and name analytics events object_action from its measures. Review checklist - Correctness: does it do w

The file

We split this AGENTS.md into the rules it gives an agent

8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Prefer small, pure functions and explicit types at module boundaries.

    line 26
  2. Distinctive:

    Every async action has loading, empty, error and success states, matching the experience skill.

    line 36
  3. Distinctive:

    Use stable types and keys in lazy lists.

    line 44
  4. Distinctive:

    Use native elements first.

    line 47
  5. Distinctive:

    Every interactive composable has a content description or visible label and a 48dp minimum touch target.

    line 48
  6. Very specific:

    When a Celestial design skill is in use, write its tokens as Compose MaterialTheme in core/designsystem/Theme.kt, and build its components …

    line 51
  7. Very specific:

    When a Celestial experience skill is in use, give each journey one end-to-end test (happy path plus its error and empty states) and name …

    line 53
  8. Distinctive:

    Every release has a written rollback path

    line 89

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

AGENTS.md — Jetpack Compose Android app

A native Android app in Kotlin with declarative UI, one-way data flow and screenshot plus journey tests.

Setup and commands

  • dev: ./gradlew installDebug
  • lint: ./gradlew lint ktlintCheck detekt
  • test: ./gradlew test connectedCheck
  • build: ./gradlew bundleRelease
  • install: ./gradlew dependencies

Project structure

  • app/ — Application, navigation graph, dependency setup
  • feature/<journey>/ — Screens and view models for one journey
  • core/designsystem/ — Theme, tokens and design-skill components
  • core/data/ — Repositories, network and database
  • core/analytics/ — Event names from the experience skill

Code style

  • Files: PascalCase.kt
  • Tests: <Type>Test.kt; <Journey>JourneyTest.kt
  • Branches: type/short-description
  • Components: PascalCase composables named after the design-skill component

Code

  • Prefer small, pure functions and explicit types at module boundaries. (Easier to test, review and change.)
  • Composables are stateless; state is hoisted to the view model. (Previews and tests stay simple.)

Components

  • Components read design tokens; no raw hex values, pixel sizes or font names in component code. (One token change restyles the product.)

Data

  • Analytics events are object_action in snake_case and come from the experience skill’s measures. (Names stay consistent across teams and tools.)

Errors

  • Every async action has loading, empty, error and success states, matching the experience skill. (Unhandled states are where users get stuck.)

Security

  • Secrets never live in the repository; read them from the environment or a secret store. (A leaked key outlives the commit that removed it.)
  • Validate every input on the server, even when the client already did. (Clients can be bypassed.)
  • Web pages ship a Content-Security-Policy, HSTS, X-Frame-Options and nosniff. (Cheap protection against the most common attacks.)

Performance

  • Use stable types and keys in lazy lists; check recomposition counts for list screens. (Keeps scrolling smooth.)

Accessibility

  • Use native elements first; add ARIA only when no native element fits. (Native controls bring keyboard and screen-reader support for free.)
  • Every interactive composable has a content description or visible label and a 48dp minimum touch target. (TalkBack users and platform guidance.)

Design and journeys

When a Celestial design skill is in use, write its tokens as Compose MaterialTheme in core/designsystem/Theme.kt, and build its components in core/designsystem/component with the same names and variants. Components read tokens only — no raw colours, sizes or font names.

When a Celestial experience skill is in use, give each journey one end-to-end test (happy path plus its error and empty states) and name analytics events object_action from its measures.

Testing and checks (must pass before a pull request)

GateToolThresholdWhen
Lint and typesThe stack’s linter and type checker0 errorsEvery pull request
Unit and component testsThe stack’s test runnerAll pass; every design-skill component state coveredEvery pull request
Journey testsEnd-to-end runnerOne test per experience-skill journey: happy path + error stateEvery pull request
AccessibilityCompose semantics checks + Accessibility Test FrameworkNo errors on journey screensEvery pull request
Performance budgetMacrobenchmarkCold start ≤ 2s on a mid-range device · no janky frames in list scrollNightly
Dependency and secret scanDependency audit + secret scannerNo high or critical findings; no secretsEvery pull request and nightly
Preview deployHosting preview environmentA working preview link on the pull requestEvery pull request

Pull requests

  • Branching: Short-lived branches; release branches per Play release.

Review checklist

  • Correctness: does it do what the issue asks, including edge cases?
  • Readability: could a new teammate change it safely?
  • Architecture: is it in the right place, with the right boundaries?
  • Security: inputs, secrets, permissions, dependencies
  • Performance: budgets, queries, bundle size
  • Tests fail when the code is broken (flip a condition and re-run)
  • Screenshots attached for UI changes

Definition of done

  • Acceptance criteria met and demoed on the preview link
  • Tests added for new behaviour and every state
  • Accessibility and performance gates green
  • Analytics events named from the experience skill
  • Docs or changelog updated when behaviour changes

Release

  • Small pull requests (aim for under 400 changed lines)
  • CI green before review
  • Squash-merge to main; main is always deployable
  • Every release has a written rollback path
  • Internal track on every merge; staged rollout 10% → 50% → 100%

Incidents

  • Halt the staged rollout; remote config flags to disable features

Generated from the Celestial engineering skill “Jetpack Compose Android app” (engineering core v1.0, checked 2026-10-25).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.