Add public showcase repository structure for Monbii

[Copilot]

Monbii's repo was a stub. This PR builds it out as a proper public showcase — product-focused, no source code exposed.

Structure added

• README.md — Rewritten with live demo link, screenshot preview table, core concept, feature list, tech stack table, and docs index
• LICENSE — All Rights Reserved
• docs/overview.md — Problem framing and behavioral design rationale (variable reward, low-friction check-ins, emotional anchoring)
• docs/architecture.md — High-level stack overview: React + Capacitor / Zustand / Supabase + Lovable Cloud / Lottie; includes ASCII system diagram
• docs/features.md — User-facing breakdown of companion system, habit tracking loop, progression/evolution, battle system, and notifications
• docs/roadmap.md — Near/medium/long-term product plans (offline support, multiple companions, adaptive battles, companion memory)
• screenshots/README.md — Placeholder table for four key screens with contribution instructions
• public-demo/link.md — Live URL (https://monbii.vercel.app/) with demo scope description
• .github/workflows/ci.yml — Lightweight markdownlint CI on push/PR to main; scoped to contents: read

Original prompt

You are creating a public showcase repository for a mobile app called Monbii.

This is NOT an open-source project.
Do NOT generate full application source code.

The purpose of this repository is to:

showcase the product
explain the system design
present features visually
demonstrate technical thinking without exposing proprietary code
Repository Requirements

1. Structure

Create the following structure:

monbii/
├── README.md
├── LICENSE (All Rights Reserved)
├── docs/
│ ├── overview.md
│ ├── architecture.md
│ ├── features.md
│ └── roadmap.md
├── screenshots/
│ └── (placeholder image files or instructions)
├── public-demo/
│ └── link.md
└── .github/
└── workflows/
└── ci.yml (optional lightweight CI for linting markdown)
2. README.md (HIGH PRIORITY)

Write a clean, professional README that includes:

Project title: Monbii
One-line description:
“A minimalist habit app where your companion grows with your consistency.”
Live demo link:
https://monbii.vercel.app/
Preview section with image placeholders
Core concept explanation:
habits affect companion
consistency = growth
missed habits = visible reaction
Features (user-focused, not technical)
Tech stack (high-level only):
React + Capacitor
Zustand
Supabase / Lovable Cloud
Lottie
Notes:
clearly state that the source code is private
Goal:
making habits feel alive instead of mechanical
3. docs/overview.md

Explain:

problem with traditional habit apps
why Monbii exists
behavioral design thinking behind it

Keep it concise and readable.

4. docs/architecture.md

Provide a high-level system architecture:

frontend (React + Capacitor)
backend (Supabase or cloud services)
state management (Zustand)
animation system (Lottie)

DO NOT include sensitive implementation details.

5. docs/features.md

Break down:

companion system
habit tracking loop
progression / evolution
battle system (high-level)
notifications

Focus on user experience, not code.

6. docs/roadmap.md

Include:

upcoming improvements
UX enhancements
system evolution ideas

Keep it realistic and product-focused.

7. public-demo/link.md

Include:

live URL
short description of what users can try
8. screenshots/

Add placeholders or instructions for:

home screen
habit screen
companion screen
battle screen
9. Style Rules
Clean, minimal, professional tone
No emojis except possibly in README title
No filler text
No generic AI phrasing
No over-explaining
10. Strict Constraints
DO NOT generate full application code
DO NOT scaffold a frontend app
DO NOT create fake APIs or backend code
DO NOT include unnecessary files
Goal

When someone lands on this repository, they should think:

“This is a real product with clear thinking behind it.”

Not:

“This is a template project.”