Vibecode Educamos
track this build5 steps, step by step0%NOT REALLY · don't bother
This is not an app you own, it is the system of record your school runs on. The grades, attendance marks, timetables and official report cards live on the school's tenant, entered by teachers you do not employ, under student data rules you do not control. A personal replacement would have nothing authoritative to read from: there is no public API you can point at, and scraping a minor's school portal is a bad idea on several axes at once. Even if you rebuilt the parent-facing screens perfectly, the moment a teacher posts a notice it would appear in Educamos and not in your build. The honest DIY here is a private tracker that sits beside it, not a replacement for it.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of Educamos. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Educamos indie build ## Goal Build the smallest trustworthy replacement for the core Educamos workflow for one developer or a tiny team. ## Scope A local family dashboard where you manually log grades, homework and school notices per child and get a simple trend view plus a weekly summary. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - Authoritative data: teachers enter grades and attendance in Educamos, not in your app - Two-way messaging with teachers and the school office - Official documents: report cards, absence justifications, enrolment and billing flows - Timetable, room and substitution updates that come from the school's own scheduling - Everyone else on it: the school, other parents, the administration staff If those capabilities are essential, use Educamos instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build a local-only family school tracker called Boletin. Single user, no accounts, no cloud. Stack, no substitutions: - Node 20, TypeScript, Fastify for the server - SQLite via better-sqlite3, file at ./data/boletin.db, schema created on first run - Server-rendered HTML with a single Pico.css CDN link, plus a little vanilla JS. No React, no build step beyond tsc. Data model: - child: id, name, school_year - subject: id, child_id, name, teacher_name (optional), weight (optional) - grade: id, subject_id, date, label, score, max_score, notes - attendance: id, child_id, date, status (present, absent, late, excused), notes - note: id, child_id, date, source (teacher, school, me), title, body, pinned boolean - homework: id, subject_id, due_date, title, done boolean Features, in scope: - Child switcher in the header. - Dashboard per child: current average per subject (weighted if weights set), homework due in the next 7 days, last 5 notes, absence count this term. - Forms to add and edit every entity. Fast keyboard entry matters more than looks: one page per entity type with an inline add row at the top. - Subject detail page with a plain SVG line chart of grades over time, no chart library. - A weekly summary page rendered from the last 7 days of data, with a copy-to-clipboard plain text version. - CSV import for grades: columns subject,date,label,score,max_score. Show a preview and a row count before committing. - Export everything to JSON at /export, and a button that copies the SQLite file to ./backups with a timestamp. Explicitly out of scope, do not attempt: - Any connection to a school platform, no scraping, no login automation, no unofficial APIs - Multi-user, invites, or messaging - Push notifications, email, telemetry, analytics Details: - npm start runs the server on PORT from .env, default 3000. Commit .env.example only. - Seed script with one fictional child and two subjects so the UI is not empty on first run. - README: what this is, what it is not, and one blunt line saying grades must be typed in by hand because the school's system is the source of truth. ## Required capabilities - Node and a local SQLite file - Manual entry, or copy-paste from whatever the school actually sends you - Nothing else, no school system access ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a lean indie version of Educamos. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Educamos indie build ## Goal Build the smallest trustworthy replacement for the core Educamos workflow for one developer or a tiny team. ## Scope A local family dashboard where you manually log grades, homework and school notices per child and get a simple trend view plus a weekly summary. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - Authoritative data: teachers enter grades and attendance in Educamos, not in your app - Two-way messaging with teachers and the school office - Official documents: report cards, absence justifications, enrolment and billing flows - Timetable, room and substitution updates that come from the school's own scheduling - Everyone else on it: the school, other parents, the administration staff If those capabilities are essential, use Educamos instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build a local-only family school tracker called Boletin. Single user, no accounts, no cloud. Stack, no substitutions: - Node 20, TypeScript, Fastify for the server - SQLite via better-sqlite3, file at ./data/boletin.db, schema created on first run - Server-rendered HTML with a single Pico.css CDN link, plus a little vanilla JS. No React, no build step beyond tsc. Data model: - child: id, name, school_year - subject: id, child_id, name, teacher_name (optional), weight (optional) - grade: id, subject_id, date, label, score, max_score, notes - attendance: id, child_id, date, status (present, absent, late, excused), notes - note: id, child_id, date, source (teacher, school, me), title, body, pinned boolean - homework: id, subject_id, due_date, title, done boolean Features, in scope: - Child switcher in the header. - Dashboard per child: current average per subject (weighted if weights set), homework due in the next 7 days, last 5 notes, absence count this term. - Forms to add and edit every entity. Fast keyboard entry matters more than looks: one page per entity type with an inline add row at the top. - Subject detail page with a plain SVG line chart of grades over time, no chart library. - A weekly summary page rendered from the last 7 days of data, with a copy-to-clipboard plain text version. - CSV import for grades: columns subject,date,label,score,max_score. Show a preview and a row count before committing. - Export everything to JSON at /export, and a button that copies the SQLite file to ./backups with a timestamp. Explicitly out of scope, do not attempt: - Any connection to a school platform, no scraping, no login automation, no unofficial APIs - Multi-user, invites, or messaging - Push notifications, email, telemetry, analytics Details: - npm start runs the server on PORT from .env, default 3000. Commit .env.example only. - Seed script with one fictional child and two subjects so the UI is not empty on first run. - README: what this is, what it is not, and one blunt line saying grades must be typed in by hand because the school's system is the source of truth. ## Required capabilities - Node and a local SQLite file - Manual entry, or copy-paste from whatever the school actually sends you - Nothing else, no school system access ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a production product version of Educamos. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== PRODUCT.md ===== # Educamos product brief ## Problem This is not an app you own, it is the system of record your school runs on. The grades, attendance marks, timetables and official report cards live on the school's tenant, entered by teachers you do not employ, under student data rules you do not control. A personal replacement would have nothing authoritative to read from: there is no public API you can point at, and scraping a minor's school portal is a bad idea on several axes at once. Even if you rebuilt the parent-facing screens perfectly, the moment a teacher posts a notice it would appear in Educamos and not in your build. The honest DIY here is a private tracker that sits beside it, not a replacement for it. ## Product outcome A local family dashboard where you manually log grades, homework and school notices per child and get a simple trend view plus a weekly summary. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Node and a local SQLite file - Manual entry, or copy-paste from whatever the school actually sends you - Nothing else, no school system access ## Explicit non-goals for v1 - Authoritative data: teachers enter grades and attendance in Educamos, not in your app - Two-way messaging with teachers and the school office - Official documents: report cards, absence justifications, enrolment and billing flows - Timetable, room and substitution updates that come from the school's own scheduling - Everyone else on it: the school, other parents, the administration staff ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees. ===== ARCHITECTURE.md ===== # Architecture ## Starting brief Build a local-only family school tracker called Boletin. Single user, no accounts, no cloud. Stack, no substitutions: - Node 20, TypeScript, Fastify for the server - SQLite via better-sqlite3, file at ./data/boletin.db, schema created on first run - Server-rendered HTML with a single Pico.css CDN link, plus a little vanilla JS. No React, no build step beyond tsc. Data model: - child: id, name, school_year - subject: id, child_id, name, teacher_name (optional), weight (optional) - grade: id, subject_id, date, label, score, max_score, notes - attendance: id, child_id, date, status (present, absent, late, excused), notes - note: id, child_id, date, source (teacher, school, me), title, body, pinned boolean - homework: id, subject_id, due_date, title, done boolean Features, in scope: - Child switcher in the header. - Dashboard per child: current average per subject (weighted if weights set), homework due in the next 7 days, last 5 notes, absence count this term. - Forms to add and edit every entity. Fast keyboard entry matters more than looks: one page per entity type with an inline add row at the top. - Subject detail page with a plain SVG line chart of grades over time, no chart library. - A weekly summary page rendered from the last 7 days of data, with a copy-to-clipboard plain text version. - CSV import for grades: columns subject,date,label,score,max_score. Show a preview and a row count before committing. - Export everything to JSON at /export, and a button that copies the SQLite file to ./backups with a timestamp. Explicitly out of scope, do not attempt: - Any connection to a school platform, no scraping, no login automation, no unofficial APIs - Multi-user, invites, or messaging - Push notifications, email, telemetry, analytics Details: - npm start runs the server on PORT from .env, default 3000. Commit .env.example only. - Seed script with one fictional child and two subjects so the UI is not empty on first run. - README: what this is, what it is not, and one blunt line saying grades must be typed in by hand because the school's system is the source of truth. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it. ===== AGENTS.md ===== # Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone. ===== MILESTONES.md ===== # Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations. ===== OPERATIONS.md ===== # Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted Educamos capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# Educamos indie build ## Goal Build the smallest trustworthy replacement for the core Educamos workflow for one developer or a tiny team. ## Scope A local family dashboard where you manually log grades, homework and school notices per child and get a simple trend view plus a weekly summary. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - Authoritative data: teachers enter grades and attendance in Educamos, not in your app - Two-way messaging with teachers and the school office - Official documents: report cards, absence justifications, enrolment and billing flows - Timetable, room and substitution updates that come from the school's own scheduling - Everyone else on it: the school, other parents, the administration staff If those capabilities are essential, use Educamos instead of pretending the gap is solved.
AGENTS.md
# Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs".
BUILD_PLAN.md
# Build plan ## Original build brief Build a local-only family school tracker called Boletin. Single user, no accounts, no cloud. Stack, no substitutions: - Node 20, TypeScript, Fastify for the server - SQLite via better-sqlite3, file at ./data/boletin.db, schema created on first run - Server-rendered HTML with a single Pico.css CDN link, plus a little vanilla JS. No React, no build step beyond tsc. Data model: - child: id, name, school_year - subject: id, child_id, name, teacher_name (optional), weight (optional) - grade: id, subject_id, date, label, score, max_score, notes - attendance: id, child_id, date, status (present, absent, late, excused), notes - note: id, child_id, date, source (teacher, school, me), title, body, pinned boolean - homework: id, subject_id, due_date, title, done boolean Features, in scope: - Child switcher in the header. - Dashboard per child: current average per subject (weighted if weights set), homework due in the next 7 days, last 5 notes, absence count this term. - Forms to add and edit every entity. Fast keyboard entry matters more than looks: one page per entity type with an inline add row at the top. - Subject detail page with a plain SVG line chart of grades over time, no chart library. - A weekly summary page rendered from the last 7 days of data, with a copy-to-clipboard plain text version. - CSV import for grades: columns subject,date,label,score,max_score. Show a preview and a row count before committing. - Export everything to JSON at /export, and a button that copies the SQLite file to ./backups with a timestamp. Explicitly out of scope, do not attempt: - Any connection to a school platform, no scraping, no login automation, no unofficial APIs - Multi-user, invites, or messaging - Push notifications, email, telemetry, analytics Details: - npm start runs the server on PORT from .env, default 3000. Commit .env.example only. - Seed script with one fictional child and two subjects so the UI is not empty on first run. - README: what this is, what it is not, and one blunt line saying grades must be typed in by hand because the school's system is the source of truth. ## Required capabilities - Node and a local SQLite file - Manual entry, or copy-paste from whatever the school actually sends you - Nothing else, no school system access ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden.
.env.example
# Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
PRODUCT.md
# Educamos product brief ## Problem This is not an app you own, it is the system of record your school runs on. The grades, attendance marks, timetables and official report cards live on the school's tenant, entered by teachers you do not employ, under student data rules you do not control. A personal replacement would have nothing authoritative to read from: there is no public API you can point at, and scraping a minor's school portal is a bad idea on several axes at once. Even if you rebuilt the parent-facing screens perfectly, the moment a teacher posts a notice it would appear in Educamos and not in your build. The honest DIY here is a private tracker that sits beside it, not a replacement for it. ## Product outcome A local family dashboard where you manually log grades, homework and school notices per child and get a simple trend view plus a weekly summary. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Node and a local SQLite file - Manual entry, or copy-paste from whatever the school actually sends you - Nothing else, no school system access ## Explicit non-goals for v1 - Authoritative data: teachers enter grades and attendance in Educamos, not in your app - Two-way messaging with teachers and the school office - Official documents: report cards, absence justifications, enrolment and billing flows - Timetable, room and substitution updates that come from the school's own scheduling - Everyone else on it: the school, other parents, the administration staff ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees.
ARCHITECTURE.md
# Architecture ## Starting brief Build a local-only family school tracker called Boletin. Single user, no accounts, no cloud. Stack, no substitutions: - Node 20, TypeScript, Fastify for the server - SQLite via better-sqlite3, file at ./data/boletin.db, schema created on first run - Server-rendered HTML with a single Pico.css CDN link, plus a little vanilla JS. No React, no build step beyond tsc. Data model: - child: id, name, school_year - subject: id, child_id, name, teacher_name (optional), weight (optional) - grade: id, subject_id, date, label, score, max_score, notes - attendance: id, child_id, date, status (present, absent, late, excused), notes - note: id, child_id, date, source (teacher, school, me), title, body, pinned boolean - homework: id, subject_id, due_date, title, done boolean Features, in scope: - Child switcher in the header. - Dashboard per child: current average per subject (weighted if weights set), homework due in the next 7 days, last 5 notes, absence count this term. - Forms to add and edit every entity. Fast keyboard entry matters more than looks: one page per entity type with an inline add row at the top. - Subject detail page with a plain SVG line chart of grades over time, no chart library. - A weekly summary page rendered from the last 7 days of data, with a copy-to-clipboard plain text version. - CSV import for grades: columns subject,date,label,score,max_score. Show a preview and a row count before committing. - Export everything to JSON at /export, and a button that copies the SQLite file to ./backups with a timestamp. Explicitly out of scope, do not attempt: - Any connection to a school platform, no scraping, no login automation, no unofficial APIs - Multi-user, invites, or messaging - Push notifications, email, telemetry, analytics Details: - npm start runs the server on PORT from .env, default 3000. Commit .env.example only. - Seed script with one fictional child and two subjects so the UI is not empty on first run. - README: what this is, what it is not, and one blunt line saying grades must be typed in by hand because the school's system is the source of truth. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.
AGENTS.md
# Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone.
MILESTONES.md
# Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.
OPERATIONS.md
# Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted Educamos capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
$ choose a build depth, inspect the files, then open the complete pack in your agent · this prompt is generated from the build plan · improve it via PR
Nobody chooses Educamos as a consumer. The school buys it because it wires together academic records, attendance, timetabling, family communication and often billing into one tenant that the administration and the teaching staff both live in, with student data handling that a school's legal obligations require somebody to be accountable for. Parents pay in attention, not money, and use it because that is where the grades appear. Ripping it out means retraining a whole staff and migrating years of academic records, which is exactly the kind of project schools do once a decade at most.
xAuthoritative data: teachers enter grades and attendance in Educamos, not in your app
xTwo-way messaging with teachers and the school office
xOfficial documents: report cards, absence justifications, enrolment and billing flows
xTimetable, room and substitution updates that come from the school's own scheduling
xEveryone else on it: the school, other parents, the administration staff
Nothing worth pointing at. That's why the prompt exists.
share on X ↗"I just replaced Educamos with one prompt"
Vibecode Educamos
Not really. Educamos's value is not the code: The moat is that the school, not you, owns the data and the staff who type it in. See the honest breakdown above.
How much does Educamos cost?
Educamos's pricing is usage-based or varies by plan · Sold to schools by Grupo SM (SM Educamos); functional modules (academic, administrative, economic) are contracted separately, so there is no list price. Only a request-information form is offered..
What do I lose by replacing Educamos?
Honestly: Authoritative data: teachers enter grades and attendance in Educamos, not in your app; Two-way messaging with teachers and the school office; Official documents: report cards, absence justifications, enrolment and billing flows; Timetable, room and substitution updates that come from the school's own scheduling; Everyone else on it: the school, other parents, the administration staff. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Educamos?
No mature open-source alternative worth pointing at, which is exactly why the one-shot prompt on this page exists.