beetzung
6dedaf0e8b
This includes the new sdk module, MapService + mapper implementation, Apollo provider module, Hilt app integration, and the project .gitignore update. Made-with: Cursor
35 lines
1.4 KiB
Plaintext
35 lines
1.4 KiB
Plaintext
---
|
|
description: Core constraints for AIRMQ recreation project
|
|
alwaysApply: true
|
|
---
|
|
|
|
# AIRMQ Recreation Core Rules
|
|
|
|
## Repository boundaries
|
|
|
|
1. Do not modify anything under `C:\Users\sysop\Desktop\airmq-android`.
|
|
2. Treat `airmq-android` as read-only reference only.
|
|
3. Create and apply all code/config/build changes only under `C:\Users\sysop\Desktop\airmq-android-2026`.
|
|
|
|
## Working policy
|
|
|
|
- When referencing legacy implementation details, copy behavior intentionally into the new project rather than editing old files.
|
|
- If a task appears to require modifying the old project, stop and propose an equivalent change in `airmq-android-2026` instead.
|
|
|
|
## Naming convention
|
|
|
|
- Use `AirMQ` everywhere for product naming.
|
|
- Never use mixed-case variants in text, docs, comments, identifiers, filenames, or symbols.
|
|
|
|
## Baseline architecture and platform stack
|
|
|
|
Use this stack as the default foundation for all implementation work in `airmq-android-2026`:
|
|
|
|
1. Jetpack Compose for UI.
|
|
2. Compose Navigation 3 as the in-app navigation system.
|
|
3. Firebase for mobile backend capabilities (for example auth, analytics, crash reporting, messaging, or remote config as needed).
|
|
4. OpenStreetMap platform for map rendering and map-related interactions.
|
|
5. Apollo GraphQL for GraphQL schema integration, client generation, and network operations.
|
|
|
|
If a requested change conflicts with this baseline, ask for explicit approval before introducing an alternative.
|