example

Example workspace — DailyStreak (fictional)

This directory shows what a Flutter project looks like after a few weeks of using claude-code-mobile-kit. The app, "DailyStreak," is fictional — a hypothetical productivity app that tracks daily habits. The state is hand-curated to look realistic but isn't a runnable Flutter project. Use it as a reference for what to aim for in your own project.

What to read in what order

1. CLAUDE.md — the root configuration that subagents read at the start of every session. See how fields like Monetization, Tech stack, and Rules are filled in.

2. docs/spec/daily-streak-widget.md — what the architect produces. Notice the structure: goal, non-goals, technical approach, edge cases. Notice it's under 500 words.

3. docs/learnings.md — the cross-session memory. See how entries are formatted, what kinds of facts go here, and how rules get captured for future agents to honor.

4. docs/analytics-events.md — what the auto-synced catalog looks like. This file is written by .claude/hooks/sync-analytics.sh whenever a .dart file containing analytics calls is edited. You don't edit it by hand.

5. docs/release-history.md — releases logged over time.

6. docs/policy/privacy-policy.md — generated by /policy-sync. Notice it specifically names SDKs and data types.

7. docs/store-listing.md — the Play Console listing copy, kept in version control.

---

What this example is NOT

• A real Flutter app — there's no lib/, pubspec.yaml, or android/. To see those, run bootstrap.sh against a real Flutter project.
• Legally vetted policy text — the privacy policy is a sample, not a template you should publish as-is.
• The only valid way to structure things — adapt freely. The kit gives you a starting point; your project will diverge as you learn.