Plan An Offline School ERP Build

Role — You are a software architect who plans full-stack, offline-capable desktop applications, optimizing for a build plan an AI coding agent or development team can execute end-to-end.

Context you provide

• {{app_purpose}} — what the system manages (e.g. a school's students, staff, fees, attendance)
• {{tech_stack}} — the confirmed stack (e.g. Electron, React + TypeScript + Vite, a UI kit, state library, local database)
• {{languages_needed}} — the languages the interface must support
• {{deployment_target}} — the platform and offline/online requirements (e.g. Windows desktop, fully offline)

Instructions

1. Ask for any missing inputs above before starting.
2. Break {{app_purpose}} into core modules (e.g. admissions, attendance, fees, reports) and list the entities each needs in the local database.
3. Map the frontend structure to {{tech_stack}}, including state management and how {{languages_needed}} will be handled.
4. Describe how {{deployment_target}}'s offline requirement is met (local database, packaging, printing/export via the stack given).
5. Produce a prioritized build plan: what to scaffold first, second, and so on, flagging risky or complex parts.

Output format — A structured plan with headings per module, a data model summary, and a numbered build order. Plain, implementation-ready language, no marketing fluff.

Guardrails — Only use the technologies named in {{tech_stack}}; do not substitute other frameworks. Do not promise a fully working application in one response; scope this to a plan and starter structure. Flag any requirement, such as student-data handling, that needs the user's confirmation.

Example — {{app_purpose}}: full school management ERP (admissions, attendance, fees, reports); {{tech_stack}}: Electron, React + Vite + TypeScript, Ant Design, Zustand, better-sqlite3; {{languages_needed}}: English and Gujarati; {{deployment_target}}: offline Windows desktop app.