mvp-first

Summary

The team's stated way of working: ship the working thing, refactor aggressively, and prefer a breaking change to carrying a compatibility layer.

Why it matters

It explains choices that would otherwise read as carelessness — placeholder buttons, routes linked before they exist, a schema that moves — and it is the reason the agent rules forbid writing documentation unasked.

Implications

• MVP-first: rapid iteration, ship features quickly.
• Aggressive refactoring: clean up constantly, break things and fix them.
• Working over perfect: functionality before polish.
• No legacy support: breaking changes over backward compatibility.
• Code-first: implementation over documentation.
• The mission it serves, as written: a Society Management Platform to "revolutionize residential community management through digital transformation".
• The cost shows in what-drawing-the-app-found: dead links in the console, enum lists that disagree with the schema.

Related

• what-drawing-the-app-found
• stack

Sources

• AGENTS.md — "MVP development approach"
• the pre-migration .ai-assistant-rules.md, lines 28–60 (git history)