Vibecode TimeTac
track this build5 steps, step by step0%KINDA · weekend project
If you are one person logging hours against projects, this is a solved evening: a table, a timer, a CSV export, done. TimeTac is not sold for that, it is sold to companies that must prove who worked when, which in Spain means a daily time record that survives an inspection. An agent can absolutely build the clock-in screen, the leave calendar and the monthly timesheet PDF, and it will feel surprisingly complete. What it will not hand you is the tamper-resistant audit trail, the payroll and HR exports your accountant already accepts, and the phone app your field staff will actually open. So: yes for yourself, shaky the moment other people's paychecks depend on your SQLite file.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of TimeTac. 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 ===== # TimeTac indie build ## Goal Build the smallest trustworthy replacement for the core TimeTac workflow for one developer or a tiny team. ## Scope A local web app where people clock in and out, log time against projects, request time off, and export approved monthly timesheets as CSV or PDF. ## 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: - Legally defensible records: no tamper-evident log, no retention guarantees, nothing an inspector or works council will nod at - Native iOS and Android apps with GPS, offline clock-in and geofencing for people who are not at a desk - Hardware terminals and badge or fingerprint clock-in for shop floors - Payroll, ERP and HR integrations plus the export formats your bookkeeper already imports without complaining - Someone else owning uptime, overtime rule edge cases and the shift and break math for each country If those capabilities are essential, use TimeTac 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 self-hosted team time tracking app called Hours. Empty folder, no cloud services. Stack, no substitutions: Next.js 15 with the App Router and TypeScript, Tailwind for styling, SQLite through Prisma, all data in ./data/hours.db. Session auth with an httpOnly signed cookie, secret in .env as SESSION_SECRET. No third-party auth, no telemetry, no analytics. Data model: User (name, email, passwordHash, role of admin or member, weeklyHours, vacationDaysPerYear), Project (name, client, archived), TimeEntry (userId, projectId nullable, start, end nullable, note, breakMinutes, approvedAt nullable), Absence (userId, type of vacation or sick or unpaid, startDate, endDate, status of pending or approved or rejected), AuditLog (userId, action, targetType, targetId, before JSON, after JSON, createdAt). Member views: a big clock in and clock out button showing today's running total, a project picker, an editable list of this week's entries with hour totals per day and week, an absence request form, and a personal balance showing hours worked versus contracted and vacation days used versus remaining. Admin views: everyone's entries for a chosen month in a grid, one-click approve per user per month which locks those entries from editing, approve or reject absence requests, CRUD for users and projects, and exports: CSV of entries filtered by month and user, plus a printable HTML monthly timesheet per user with signature lines. Every create, update and delete on TimeEntry and Absence writes an AuditLog row. Never hard delete a TimeEntry, use a deletedAt flag and keep it out of totals. Rules: overlapping open entries are rejected, entries longer than 12 hours warn on save, a configurable auto break deduction of 30 minutes past 6 hours is applied at display time not at write time. Out of scope, do not build: mobile apps, GPS or geofencing, payroll integrations, invoicing, multi-tenant orgs, email sending. Ship a seed script with two users, three projects and a week of sample entries, a README with setup and backup instructions, and Vitest tests for the totals and break deduction math. ## Required capabilities - Node 20+ - somewhere to run it that your team can reach, plus HTTPS if it leaves your laptop - backups you actually test, because these records are the evidence ## 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 TimeTac. 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 ===== # TimeTac indie build ## Goal Build the smallest trustworthy replacement for the core TimeTac workflow for one developer or a tiny team. ## Scope A local web app where people clock in and out, log time against projects, request time off, and export approved monthly timesheets as CSV or PDF. ## 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: - Legally defensible records: no tamper-evident log, no retention guarantees, nothing an inspector or works council will nod at - Native iOS and Android apps with GPS, offline clock-in and geofencing for people who are not at a desk - Hardware terminals and badge or fingerprint clock-in for shop floors - Payroll, ERP and HR integrations plus the export formats your bookkeeper already imports without complaining - Someone else owning uptime, overtime rule edge cases and the shift and break math for each country If those capabilities are essential, use TimeTac 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 self-hosted team time tracking app called Hours. Empty folder, no cloud services. Stack, no substitutions: Next.js 15 with the App Router and TypeScript, Tailwind for styling, SQLite through Prisma, all data in ./data/hours.db. Session auth with an httpOnly signed cookie, secret in .env as SESSION_SECRET. No third-party auth, no telemetry, no analytics. Data model: User (name, email, passwordHash, role of admin or member, weeklyHours, vacationDaysPerYear), Project (name, client, archived), TimeEntry (userId, projectId nullable, start, end nullable, note, breakMinutes, approvedAt nullable), Absence (userId, type of vacation or sick or unpaid, startDate, endDate, status of pending or approved or rejected), AuditLog (userId, action, targetType, targetId, before JSON, after JSON, createdAt). Member views: a big clock in and clock out button showing today's running total, a project picker, an editable list of this week's entries with hour totals per day and week, an absence request form, and a personal balance showing hours worked versus contracted and vacation days used versus remaining. Admin views: everyone's entries for a chosen month in a grid, one-click approve per user per month which locks those entries from editing, approve or reject absence requests, CRUD for users and projects, and exports: CSV of entries filtered by month and user, plus a printable HTML monthly timesheet per user with signature lines. Every create, update and delete on TimeEntry and Absence writes an AuditLog row. Never hard delete a TimeEntry, use a deletedAt flag and keep it out of totals. Rules: overlapping open entries are rejected, entries longer than 12 hours warn on save, a configurable auto break deduction of 30 minutes past 6 hours is applied at display time not at write time. Out of scope, do not build: mobile apps, GPS or geofencing, payroll integrations, invoicing, multi-tenant orgs, email sending. Ship a seed script with two users, three projects and a week of sample entries, a README with setup and backup instructions, and Vitest tests for the totals and break deduction math. ## Required capabilities - Node 20+ - somewhere to run it that your team can reach, plus HTTPS if it leaves your laptop - backups you actually test, because these records are the evidence ## 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 TimeTac. 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 ===== # TimeTac product brief ## Problem If you are one person logging hours against projects, this is a solved evening: a table, a timer, a CSV export, done. TimeTac is not sold for that, it is sold to companies that must prove who worked when, which in Spain means a daily time record that survives an inspection. An agent can absolutely build the clock-in screen, the leave calendar and the monthly timesheet PDF, and it will feel surprisingly complete. What it will not hand you is the tamper-resistant audit trail, the payroll and HR exports your accountant already accepts, and the phone app your field staff will actually open. So: yes for yourself, shaky the moment other people's paychecks depend on your SQLite file. ## Product outcome A local web app where people clock in and out, log time against projects, request time off, and export approved monthly timesheets as CSV or PDF. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Node 20+ - somewhere to run it that your team can reach, plus HTTPS if it leaves your laptop - backups you actually test, because these records are the evidence ## Explicit non-goals for v1 - Legally defensible records: no tamper-evident log, no retention guarantees, nothing an inspector or works council will nod at - Native iOS and Android apps with GPS, offline clock-in and geofencing for people who are not at a desk - Hardware terminals and badge or fingerprint clock-in for shop floors - Payroll, ERP and HR integrations plus the export formats your bookkeeper already imports without complaining - Someone else owning uptime, overtime rule edge cases and the shift and break math for each country ## 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 self-hosted team time tracking app called Hours. Empty folder, no cloud services. Stack, no substitutions: Next.js 15 with the App Router and TypeScript, Tailwind for styling, SQLite through Prisma, all data in ./data/hours.db. Session auth with an httpOnly signed cookie, secret in .env as SESSION_SECRET. No third-party auth, no telemetry, no analytics. Data model: User (name, email, passwordHash, role of admin or member, weeklyHours, vacationDaysPerYear), Project (name, client, archived), TimeEntry (userId, projectId nullable, start, end nullable, note, breakMinutes, approvedAt nullable), Absence (userId, type of vacation or sick or unpaid, startDate, endDate, status of pending or approved or rejected), AuditLog (userId, action, targetType, targetId, before JSON, after JSON, createdAt). Member views: a big clock in and clock out button showing today's running total, a project picker, an editable list of this week's entries with hour totals per day and week, an absence request form, and a personal balance showing hours worked versus contracted and vacation days used versus remaining. Admin views: everyone's entries for a chosen month in a grid, one-click approve per user per month which locks those entries from editing, approve or reject absence requests, CRUD for users and projects, and exports: CSV of entries filtered by month and user, plus a printable HTML monthly timesheet per user with signature lines. Every create, update and delete on TimeEntry and Absence writes an AuditLog row. Never hard delete a TimeEntry, use a deletedAt flag and keep it out of totals. Rules: overlapping open entries are rejected, entries longer than 12 hours warn on save, a configurable auto break deduction of 30 minutes past 6 hours is applied at display time not at write time. Out of scope, do not build: mobile apps, GPS or geofencing, payroll integrations, invoicing, multi-tenant orgs, email sending. Ship a seed script with two users, three projects and a week of sample entries, a README with setup and backup instructions, and Vitest tests for the totals and break deduction math. ## 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 TimeTac capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# TimeTac indie build ## Goal Build the smallest trustworthy replacement for the core TimeTac workflow for one developer or a tiny team. ## Scope A local web app where people clock in and out, log time against projects, request time off, and export approved monthly timesheets as CSV or PDF. ## 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: - Legally defensible records: no tamper-evident log, no retention guarantees, nothing an inspector or works council will nod at - Native iOS and Android apps with GPS, offline clock-in and geofencing for people who are not at a desk - Hardware terminals and badge or fingerprint clock-in for shop floors - Payroll, ERP and HR integrations plus the export formats your bookkeeper already imports without complaining - Someone else owning uptime, overtime rule edge cases and the shift and break math for each country If those capabilities are essential, use TimeTac 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 self-hosted team time tracking app called Hours. Empty folder, no cloud services. Stack, no substitutions: Next.js 15 with the App Router and TypeScript, Tailwind for styling, SQLite through Prisma, all data in ./data/hours.db. Session auth with an httpOnly signed cookie, secret in .env as SESSION_SECRET. No third-party auth, no telemetry, no analytics. Data model: User (name, email, passwordHash, role of admin or member, weeklyHours, vacationDaysPerYear), Project (name, client, archived), TimeEntry (userId, projectId nullable, start, end nullable, note, breakMinutes, approvedAt nullable), Absence (userId, type of vacation or sick or unpaid, startDate, endDate, status of pending or approved or rejected), AuditLog (userId, action, targetType, targetId, before JSON, after JSON, createdAt). Member views: a big clock in and clock out button showing today's running total, a project picker, an editable list of this week's entries with hour totals per day and week, an absence request form, and a personal balance showing hours worked versus contracted and vacation days used versus remaining. Admin views: everyone's entries for a chosen month in a grid, one-click approve per user per month which locks those entries from editing, approve or reject absence requests, CRUD for users and projects, and exports: CSV of entries filtered by month and user, plus a printable HTML monthly timesheet per user with signature lines. Every create, update and delete on TimeEntry and Absence writes an AuditLog row. Never hard delete a TimeEntry, use a deletedAt flag and keep it out of totals. Rules: overlapping open entries are rejected, entries longer than 12 hours warn on save, a configurable auto break deduction of 30 minutes past 6 hours is applied at display time not at write time. Out of scope, do not build: mobile apps, GPS or geofencing, payroll integrations, invoicing, multi-tenant orgs, email sending. Ship a seed script with two users, three projects and a week of sample entries, a README with setup and backup instructions, and Vitest tests for the totals and break deduction math. ## Required capabilities - Node 20+ - somewhere to run it that your team can reach, plus HTTPS if it leaves your laptop - backups you actually test, because these records are the evidence ## 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
# TimeTac product brief ## Problem If you are one person logging hours against projects, this is a solved evening: a table, a timer, a CSV export, done. TimeTac is not sold for that, it is sold to companies that must prove who worked when, which in Spain means a daily time record that survives an inspection. An agent can absolutely build the clock-in screen, the leave calendar and the monthly timesheet PDF, and it will feel surprisingly complete. What it will not hand you is the tamper-resistant audit trail, the payroll and HR exports your accountant already accepts, and the phone app your field staff will actually open. So: yes for yourself, shaky the moment other people's paychecks depend on your SQLite file. ## Product outcome A local web app where people clock in and out, log time against projects, request time off, and export approved monthly timesheets as CSV or PDF. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Node 20+ - somewhere to run it that your team can reach, plus HTTPS if it leaves your laptop - backups you actually test, because these records are the evidence ## Explicit non-goals for v1 - Legally defensible records: no tamper-evident log, no retention guarantees, nothing an inspector or works council will nod at - Native iOS and Android apps with GPS, offline clock-in and geofencing for people who are not at a desk - Hardware terminals and badge or fingerprint clock-in for shop floors - Payroll, ERP and HR integrations plus the export formats your bookkeeper already imports without complaining - Someone else owning uptime, overtime rule edge cases and the shift and break math for each country ## 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 self-hosted team time tracking app called Hours. Empty folder, no cloud services. Stack, no substitutions: Next.js 15 with the App Router and TypeScript, Tailwind for styling, SQLite through Prisma, all data in ./data/hours.db. Session auth with an httpOnly signed cookie, secret in .env as SESSION_SECRET. No third-party auth, no telemetry, no analytics. Data model: User (name, email, passwordHash, role of admin or member, weeklyHours, vacationDaysPerYear), Project (name, client, archived), TimeEntry (userId, projectId nullable, start, end nullable, note, breakMinutes, approvedAt nullable), Absence (userId, type of vacation or sick or unpaid, startDate, endDate, status of pending or approved or rejected), AuditLog (userId, action, targetType, targetId, before JSON, after JSON, createdAt). Member views: a big clock in and clock out button showing today's running total, a project picker, an editable list of this week's entries with hour totals per day and week, an absence request form, and a personal balance showing hours worked versus contracted and vacation days used versus remaining. Admin views: everyone's entries for a chosen month in a grid, one-click approve per user per month which locks those entries from editing, approve or reject absence requests, CRUD for users and projects, and exports: CSV of entries filtered by month and user, plus a printable HTML monthly timesheet per user with signature lines. Every create, update and delete on TimeEntry and Absence writes an AuditLog row. Never hard delete a TimeEntry, use a deletedAt flag and keep it out of totals. Rules: overlapping open entries are rejected, entries longer than 12 hours warn on save, a configurable auto break deduction of 30 minutes past 6 hours is applied at display time not at write time. Out of scope, do not build: mobile apps, GPS or geofencing, payroll integrations, invoicing, multi-tenant orgs, email sending. Ship a seed script with two users, three projects and a week of sample entries, a README with setup and backup instructions, and Vitest tests for the totals and break deduction math. ## 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 TimeTac 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
Companies do not buy time tracking because timers are hard, they buy it because a missing time record is a fine and a disputed overtime claim is a lawsuit. The paid version comes with rule sets for breaks, overtime and absence accrual per country, exports that payroll accepts, apps that work on a phone in a van, and a vendor to point at when something is wrong. A self-hosted app you wrote yourself is fine for your own invoicing and a bad idea the moment an employee disagrees with it.
xLegally defensible records: no tamper-evident log, no retention guarantees, nothing an inspector or works council will nod at
xNative iOS and Android apps with GPS, offline clock-in and geofencing for people who are not at a desk
xHardware terminals and badge or fingerprint clock-in for shop floors
xPayroll, ERP and HR integrations plus the export formats your bookkeeper already imports without complaining
xSomeone else owning uptime, overtime rule edge cases and the shift and break math for each country
Nothing worth pointing at. That's why the prompt exists.
share on X ↗"I just replaced TimeTac ($7.2/mo) with one prompt"
Vibecode TimeTac
Kinda. The core of TimeTac is buildable in a weekend with the prompt on this page, but there are real gaps: Legally defensible records: no tamper-evident log, no retention guarantees, nothing an inspector or works council will nod at, Native iOS and Android apps with GPS, offline clock-in and geofencing for people who are not at a desk. Read the honest list above before committing.
How much does TimeTac cost?
TimeTac costs about $7.2/month (Employee Time Tracking module, checked 2026-08-18), which is $86.4 per year.
What do I lose by replacing TimeTac?
Honestly: Legally defensible records: no tamper-evident log, no retention guarantees, nothing an inspector or works council will nod at; Native iOS and Android apps with GPS, offline clock-in and geofencing for people who are not at a desk; Hardware terminals and badge or fingerprint clock-in for shop floors; Payroll, ERP and HR integrations plus the export formats your bookkeeper already imports without complaining; Someone else owning uptime, overtime rule edge cases and the shift and break math for each country. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to TimeTac?
No mature open-source alternative worth pointing at, which is exactly why the one-shot prompt on this page exists.