Quickbase

Build me a focused spreadsheet databases and operational data apps workflow for the personal core of Quickbase. Requirements:

- Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and Docker Compose. Model tasks, projects, schedules, dependencies, and completion events; store source IDs and timestamps for each.
- Paid product context: Build a constrained operational database and forms for one small team. Build only this DIY scope: Model structured records in a constrained operational database for one small team, provide form, grid, kanban, and filtered views, and expose a documented API.
- Create workspaces, bases, tables, fields, records, attachments, relations, and saved views.
- Support text, number, currency, date, boolean, select, formula-lite, and relation field types.
- Add role-based permissions, optimistic concurrency checks, audit history, and trash restore.
- Use a local web page with input, progress, review, and export views. Required input or access: Docker; self-hosted server.
- Recovery: Add role-based permissions, optimistic concurrency checks, audit history, and trash restore.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: An invalid input or interrupted operation must retain the source and show a recoverable state; exported records must reload with the same IDs.
- Out of scope: enterprise governance, integrations, scale, app lifecycle, and support; real-time multiplayer. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

# AGENTS.md — Build guide for Quickbase

## Project scope
Model structured records in a constrained operational database for one small team, provide form, grid, kanban, and filtered views, and expose a documented API.

Catalogue verdict: no. A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Quickbase, build a constrained operational database and forms for one small team. The hard boundary is enterprise governance, integrations, scale, app lifecycle, and support, plus data model flexibility, collaboration, and integrations.
Use the implementation prompt below to define the deliverable. Complete each phase's acceptance checks before extending the scope.

## Working agreement
- Inspect the repository and its existing instructions before choosing paths, dependencies or commands. Keep one coherent stack and explain changes to the proposed architecture.
- Plan a vertical slice that accepts a real input and produces the useful output described below. Persist only the state the prompt calls for; respect memory-only and upstream-managed workflows. Use fixtures only when they are clearly labelled.
- After scaffolding, document the actual install, development, check and build commands in README and keep them synchronized with the package or project manifest. Do not report commands as successful unless they ran.
- Work in small steps. At handoff, list implemented flows, checks actually performed, remaining blockers, and any credentials or provider setup the owner must supply.
- Do not publish, spend money, contact customers, delete source data or run irreversible migrations without the project owner's authorization.

## Prerequisites
- Docker
- PostgreSQL
- self-hosted server
- optional object storage for attachments

## Stack and architecture
- Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and Docker Compose.
- Model tasks, projects, schedules, dependencies, and completion events; store source IDs and timestamps for each.
- Interface for this spreadsheet databases and operational data apps workflow: a local web page with input, progress, review, and export views.

## Security and data integrity
- Add role-based permissions, optimistic concurrency checks, audit history, and trash restore.
- Validate imported records and file paths; keep user data within the storage location named in the prompt.
- State the practical limit: enterprise governance, integrations, scale, app lifecycle, and support.

## Agent implementation rules
- Project rule, data: Model tasks, projects, schedules, dependencies, and completion events; store source IDs and timestamps for each.
- Project rule, behavior: Create workspaces, bases, tables, fields, records, attachments, relations, and saved views.
- Project rule, recovery: Add role-based permissions, optimistic concurrency checks, audit history, and trash restore.

## Optional agent skills and references
No installable skill is listed for this guide; use the project rules and the stack documentation.

Read the linked SKILL.md and its dependencies before adding a skill. Select only the skills matching this project's runtime and task; their documentation does not supply API access, credentials or approval to perform external actions. Pin the reviewed revision where the tool supports it. Follow the chosen agent's documented project-level installation mechanism.

## Distribution ideas
These are optional planning notes. Obtain the owner's approval before publishing or contacting anyone.
- Demonstrate this spreadsheet databases and operational data apps operation with sample or user-owned data: Create workspaces, bases, tables, fields, records, attachments, relations, and saved views.
- Show a concrete result or export: Provide CSV import or export and a token-authenticated REST API generated from the schema.
- State the practical limit: enterprise governance, integrations, scale, app lifecycle, and support.

## Engineering roadmap
1. Phase 1, architecture and data: Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and Docker Compose. Model tasks, projects, schedules, dependencies, and completion events; store source IDs and timestamps for each.
2. Phase 2, implement: Create workspaces, bases, tables, fields, records, attachments, relations, and saved views.
3. Phase 3, implement: Support text, number, currency, date, boolean, select, formula-lite, and relation field types.
4. Phase 4, review and output: Add role-based permissions, optimistic concurrency checks, audit history, and trash restore. Provide CSV import or export and a token-authenticated REST API generated from the schema.
5. Phase 5, recovery and acceptance: Add role-based permissions, optimistic concurrency checks, audit history, and trash restore. Verify this invariant with a saved fixture: An invalid input or interrupted operation must retain the source and show a recoverable state; exported records must reload with the same IDs. State the practical limit: enterprise governance, integrations, scale, app lifecycle, and support.

## Paid-product capabilities outside this build
- enterprise governance, integrations, scale, app lifecycle, and support
- real-time multiplayer
- automation and integration breadth
- scale and formula depth
- enterprise permissions

## Implementation prompt
Build me a focused spreadsheet databases and operational data apps workflow for the personal core of Quickbase. Requirements:

- Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and Docker Compose. Model tasks, projects, schedules, dependencies, and completion events; store source IDs and timestamps for each.
- Paid product context: Build a constrained operational database and forms for one small team. Build only this DIY scope: Model structured records in a constrained operational database for one small team, provide form, grid, kanban, and filtered views, and expose a documented API.
- Create workspaces, bases, tables, fields, records, attachments, relations, and saved views.
- Support text, number, currency, date, boolean, select, formula-lite, and relation field types.
- Add role-based permissions, optimistic concurrency checks, audit history, and trash restore.
- Use a local web page with input, progress, review, and export views. Required input or access: Docker; self-hosted server.
- Recovery: Add role-based permissions, optimistic concurrency checks, audit history, and trash restore.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: An invalid input or interrupted operation must retain the source and show a recoverable state; exported records must reload with the same IDs.
- Out of scope: enterprise governance, integrations, scale, app lifecycle, and support; real-time multiplayer. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

## Completion evidence
Demonstrate the prompt's acceptance scenarios against the scoped workflow. Include setup from a clean checkout and failure recovery. Check persistence across restart and export/restore only for the state the prompt says to store; for memory-only tools, confirm that temporary content is discarded as specified. Record actual results and remaining limitations. A detailed plan alone does not establish a working replacement.