Vibecode Connecteam

You are building a lean indie version of Connecteam.

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 =====
# Connecteam indie build

## Goal

Build the smallest trustworthy replacement for the core Connecteam workflow for one developer or a tiny team.

## Scope

Publish a two-week staff schedule, collect availability and time-off requests, approve shift claims or swaps, attach checklists, and record explicit clock-ins with an auditable CSV export.

## 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:
- native iOS and Android apps, offline use, and reliable push notifications
- GPS geofences, kiosk and NFC clocks, and background location workflows
- payroll integrations, overtime rules, and labor-law compliance support
- chat, training, HR documents, recognition, and the rest of the three-hub suite
- vendor support plus hardened permissions, audit history, and incident response

If those capabilities are essential, use Frappe HR 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 me a narrow small-team workforce scheduler to replace only Connecteam's visible operations loop. Requirements:

- Use Node.js 22, Fastify, Nunjucks, htmx, and better-sqlite3. Run one
  process behind Caddy; do not add a SPA, ORM, or container platform.
- Give one admin a mobile-first two-week schedule editor for employees, roles,
  locations, open shifts, recurring shifts, and per-shift checklists.
- Employees sign in with expiring magic links sent through SMTP credentials in
  .env. No public signup; hash tokens and rate-limit every login endpoint.
- Each employee can set availability, request time off, claim an open shift,
  request a swap, see only their own schedule, and mark shift tasks complete.
- Add explicit clock-in/out buttons. Store server time and optional one-shot
  browser location only after consent; never track location in the background.
- Managers approve requests, publish changes, and see an append-only audit log.
  Export schedules, requests, and worked time as CSV; never calculate payroll.
- Store everything in SQLite, make nightly timestamped backups, and include a
  tested restore command. No telemetry or third-party tracking.
- Out of scope: native apps, push notifications, chat, GPS geofences, kiosk and
  NFC clocks, payroll integrations, training, HR documents, and legal compliance.
- Add focused tests for permissions, overlapping shifts, token expiry, and CSV
  export, plus one Playwright flow from invite through completed shift.
- Include a README for .env, HTTPS, backups, retention, and the employee-data
  risks. End by running tests and listing the exact commands and results.

## Required capabilities

- private HTTPS deployment
- Node.js 22 and SQLite
- SMTP credentials for employee magic links
- documented access, backup, and retention policy

## 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 Connecteam.

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 =====
# Connecteam indie build

## Goal

Build the smallest trustworthy replacement for the core Connecteam workflow for one developer or a tiny team.

## Scope

Publish a two-week staff schedule, collect availability and time-off requests, approve shift claims or swaps, attach checklists, and record explicit clock-ins with an auditable CSV export.

## 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:
- native iOS and Android apps, offline use, and reliable push notifications
- GPS geofences, kiosk and NFC clocks, and background location workflows
- payroll integrations, overtime rules, and labor-law compliance support
- chat, training, HR documents, recognition, and the rest of the three-hub suite
- vendor support plus hardened permissions, audit history, and incident response

If those capabilities are essential, use Frappe HR 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 me a narrow small-team workforce scheduler to replace only Connecteam's visible operations loop. Requirements:

- Use Node.js 22, Fastify, Nunjucks, htmx, and better-sqlite3. Run one
  process behind Caddy; do not add a SPA, ORM, or container platform.
- Give one admin a mobile-first two-week schedule editor for employees, roles,
  locations, open shifts, recurring shifts, and per-shift checklists.
- Employees sign in with expiring magic links sent through SMTP credentials in
  .env. No public signup; hash tokens and rate-limit every login endpoint.
- Each employee can set availability, request time off, claim an open shift,
  request a swap, see only their own schedule, and mark shift tasks complete.
- Add explicit clock-in/out buttons. Store server time and optional one-shot
  browser location only after consent; never track location in the background.
- Managers approve requests, publish changes, and see an append-only audit log.
  Export schedules, requests, and worked time as CSV; never calculate payroll.
- Store everything in SQLite, make nightly timestamped backups, and include a
  tested restore command. No telemetry or third-party tracking.
- Out of scope: native apps, push notifications, chat, GPS geofences, kiosk and
  NFC clocks, payroll integrations, training, HR documents, and legal compliance.
- Add focused tests for permissions, overlapping shifts, token expiry, and CSV
  export, plus one Playwright flow from invite through completed shift.
- Include a README for .env, HTTPS, backups, retention, and the employee-data
  risks. End by running tests and listing the exact commands and results.

## Required capabilities

- private HTTPS deployment
- Node.js 22 and SQLite
- SMTP credentials for employee magic links
- documented access, backup, and retention policy

## 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 Connecteam.

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 =====
# Connecteam product brief

## Problem

Not as a one-shot. A narrow scheduler, availability form, shift checklist, and explicit clock-in log are buildable, but Connecteam's real product is the maintained mobile system around them: multi-user permissions, push delivery, GPS and kiosk capture, payroll integrations, audit history, and HR and compliance workflows. That is operational software a team has to trust, not a personal CRUD app.

## Product outcome

Publish a two-week staff schedule, collect availability and time-off requests, approve shift claims or swaps, attach checklists, and record explicit clock-ins with an auditable CSV export.

## Target user

A serious builder who needs a maintainable product foundation rather than a one-off demo.

## Required capabilities

- private HTTPS deployment
- Node.js 22 and SQLite
- SMTP credentials for employee magic links
- documented access, backup, and retention policy

## Explicit non-goals for v1

- native iOS and Android apps, offline use, and reliable push notifications
- GPS geofences, kiosk and NFC clocks, and background location workflows
- payroll integrations, overtime rules, and labor-law compliance support
- chat, training, HR documents, recognition, and the rest of the three-hub suite
- vendor support plus hardened permissions, audit history, and incident response

## 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 me a narrow small-team workforce scheduler to replace only Connecteam's visible operations loop. Requirements:

- Use Node.js 22, Fastify, Nunjucks, htmx, and better-sqlite3. Run one
  process behind Caddy; do not add a SPA, ORM, or container platform.
- Give one admin a mobile-first two-week schedule editor for employees, roles,
  locations, open shifts, recurring shifts, and per-shift checklists.
- Employees sign in with expiring magic links sent through SMTP credentials in
  .env. No public signup; hash tokens and rate-limit every login endpoint.
- Each employee can set availability, request time off, claim an open shift,
  request a swap, see only their own schedule, and mark shift tasks complete.
- Add explicit clock-in/out buttons. Store server time and optional one-shot
  browser location only after consent; never track location in the background.
- Managers approve requests, publish changes, and see an append-only audit log.
  Export schedules, requests, and worked time as CSV; never calculate payroll.
- Store everything in SQLite, make nightly timestamped backups, and include a
  tested restore command. No telemetry or third-party tracking.
- Out of scope: native apps, push notifications, chat, GPS geofences, kiosk and
  NFC clocks, payroll integrations, training, HR documents, and legal compliance.
- Add focused tests for permissions, overlapping shifts, token expiry, and CSV
  export, plus one Playwright flow from invite through completed shift.
- Include a README for .env, HTTPS, backups, retention, and the employee-data
  risks. End by running tests and listing the exact commands and results.

## 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 Connecteam capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.

# Connecteam indie build

## Goal

Build the smallest trustworthy replacement for the core Connecteam workflow for one developer or a tiny team.

## Scope

Publish a two-week staff schedule, collect availability and time-off requests, approve shift claims or swaps, attach checklists, and record explicit clock-ins with an auditable CSV export.

## 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:
- native iOS and Android apps, offline use, and reliable push notifications
- GPS geofences, kiosk and NFC clocks, and background location workflows
- payroll integrations, overtime rules, and labor-law compliance support
- chat, training, HR documents, recognition, and the rest of the three-hub suite
- vendor support plus hardened permissions, audit history, and incident response

If those capabilities are essential, use Frappe HR instead of pretending the gap is solved.

# 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

## Original build brief

Build me a narrow small-team workforce scheduler to replace only Connecteam's visible operations loop. Requirements:

- Use Node.js 22, Fastify, Nunjucks, htmx, and better-sqlite3. Run one
  process behind Caddy; do not add a SPA, ORM, or container platform.
- Give one admin a mobile-first two-week schedule editor for employees, roles,
  locations, open shifts, recurring shifts, and per-shift checklists.
- Employees sign in with expiring magic links sent through SMTP credentials in
  .env. No public signup; hash tokens and rate-limit every login endpoint.
- Each employee can set availability, request time off, claim an open shift,
  request a swap, see only their own schedule, and mark shift tasks complete.
- Add explicit clock-in/out buttons. Store server time and optional one-shot
  browser location only after consent; never track location in the background.
- Managers approve requests, publish changes, and see an append-only audit log.
  Export schedules, requests, and worked time as CSV; never calculate payroll.
- Store everything in SQLite, make nightly timestamped backups, and include a
  tested restore command. No telemetry or third-party tracking.
- Out of scope: native apps, push notifications, chat, GPS geofences, kiosk and
  NFC clocks, payroll integrations, training, HR documents, and legal compliance.
- Add focused tests for permissions, overlapping shifts, token expiry, and CSV
  export, plus one Playwright flow from invite through completed shift.
- Include a README for .env, HTTPS, backups, retention, and the employee-data
  risks. End by running tests and listing the exact commands and results.

## Required capabilities

- private HTTPS deployment
- Node.js 22 and SQLite
- SMTP credentials for employee magic links
- documented access, backup, and retention policy

## 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.

# 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.

# Connecteam product brief

## Problem

Not as a one-shot. A narrow scheduler, availability form, shift checklist, and explicit clock-in log are buildable, but Connecteam's real product is the maintained mobile system around them: multi-user permissions, push delivery, GPS and kiosk capture, payroll integrations, audit history, and HR and compliance workflows. That is operational software a team has to trust, not a personal CRUD app.

## Product outcome

Publish a two-week staff schedule, collect availability and time-off requests, approve shift claims or swaps, attach checklists, and record explicit clock-ins with an auditable CSV export.

## Target user

A serious builder who needs a maintainable product foundation rather than a one-off demo.

## Required capabilities

- private HTTPS deployment
- Node.js 22 and SQLite
- SMTP credentials for employee magic links
- documented access, backup, and retention policy

## Explicit non-goals for v1

- native iOS and Android apps, offline use, and reliable push notifications
- GPS geofences, kiosk and NFC clocks, and background location workflows
- payroll integrations, overtime rules, and labor-law compliance support
- chat, training, HR documents, recognition, and the rest of the three-hub suite
- vendor support plus hardened permissions, audit history, and incident response

## 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

## Starting brief

Build me a narrow small-team workforce scheduler to replace only Connecteam's visible operations loop. Requirements:

- Use Node.js 22, Fastify, Nunjucks, htmx, and better-sqlite3. Run one
  process behind Caddy; do not add a SPA, ORM, or container platform.
- Give one admin a mobile-first two-week schedule editor for employees, roles,
  locations, open shifts, recurring shifts, and per-shift checklists.
- Employees sign in with expiring magic links sent through SMTP credentials in
  .env. No public signup; hash tokens and rate-limit every login endpoint.
- Each employee can set availability, request time off, claim an open shift,
  request a swap, see only their own schedule, and mark shift tasks complete.
- Add explicit clock-in/out buttons. Store server time and optional one-shot
  browser location only after consent; never track location in the background.
- Managers approve requests, publish changes, and see an append-only audit log.
  Export schedules, requests, and worked time as CSV; never calculate payroll.
- Store everything in SQLite, make nightly timestamped backups, and include a
  tested restore command. No telemetry or third-party tracking.
- Out of scope: native apps, push notifications, chat, GPS geofences, kiosk and
  NFC clocks, payroll integrations, training, HR documents, and legal compliance.
- Add focused tests for permissions, overlapping shifts, token expiry, and CSV
  export, plus one Playwright flow from invite through completed shift.
- Include a README for .env, HTTPS, backups, retention, and the employee-data
  risks. End by running tests and listing the exact commands and results.

## 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.

# 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.

# 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

## 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 Connecteam 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