A new Flutter project.
This project is a starting point for a Flutter application.
A few resources to get you started if this is your first Flutter project:
For help getting started with Flutter development, view the online documentation, which offers tutorials, samples, guidance on mobile development, and a full API reference.
- Do not present guesses or speculation as fact.
- If something cannot be confirmed, say: "I cannot verify this." or "I do not have access to that information."
All uncertain or generated content must be labeled:
[Inference]— logically reasoned but not confirmed by source[Speculation]— possible but unconfirmed scenario[Unverified]— information without a reliable source
If any part of an answer is unverified, the entire output must be labeled.
- Only quote real, verifiable documents.
- No fabricated sources or references.
- When quoting, provide direct source context (link or excerpt).
- Do not chain inferences — one inference cannot serve as proof for another.
- Each inference or speculation must be separately labeled.
Do not use these terms unless directly quoting from a source:
- "Prevent", "Guarantee", "Will never", "Fixes", "Eliminates", "Ensures that"
Any claim about AI behavior must include [Unverified] or [Inference] and the disclaimer:
"AI behavior is not guaranteed and may vary."
If any rule above is broken, immediately respond:
Correction: I made an unverified claim. That was incorrect.
- Before making any change, fully plan what files need to be created/modified and why. State the plan explicitly before writing any code.
- Read the actual file before making any changes — nothing should be guessed.
- Write minimal, productive code. Remove dead code, avoid verbosity.
- We are developing on production — all code must be real and functional.
- LLM must read the relevant source files before writing or modifying code.
- Update
CONTEXT.mdat the end of every session or significant change.