Thunkable

Build me a focused internal tools and application builders workflow for the personal core of Thunkable. Requirements:

- Use Next.js 15, TypeScript, Tailwind CSS, PostgreSQL, Drizzle ORM, and Docker Compose. Model repositories, builds, deployments, logs, and rollback points; store source IDs and timestamps for each.
- Paid product context: Prototype a mobile app with fixed components and local data. Build only this DIY scope: Prototype a mobile app from fixed components, define tables and views, build a constrained CRUD interface over local data or one approved data source, and deploy it for a small trusted team.
- Create a schema editor for text, number, boolean, date, enum, and relation fields.
- Generate list, detail, create, edit, and kanban views from the schema.
- Implement role-based read and write rules for admin and member roles. Support one REST connector with encrypted credentials and explicit field mapping. Add an activity log, CSV import or export, backups, and health checks.
- Use a local web page with input, progress, review, and export views. Required input or access: Docker; self-hosted deploy target.
- Recovery: If API credentials for one selected integration is unavailable, keep the source record and show a recoverable error instead of a fabricated result.
- 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: native build infrastructure, device integrations, publishing pipeline, and education ecosystem; hundreds of connectors. 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 Thunkable

## Project scope
Prototype a mobile app from fixed components, define tables and views, build a constrained CRUD interface over local data or one approved data source, and deploy it for a small trusted team.

Catalogue verdict: no. A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Thunkable, prototype a mobile app with fixed components and local data. The hard boundary is native build infrastructure, device integrations, publishing pipeline, and education ecosystem, plus connectors, runtime reliability, and governance.
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 deploy target
- API credentials for one selected integration

## Stack and architecture
- Use Next.js 15, TypeScript, Tailwind CSS, PostgreSQL, Drizzle ORM, and Docker Compose.
- Model repositories, builds, deployments, logs, and rollback points; store source IDs and timestamps for each.
- Interface for this internal tools and application builders workflow: a local web page with input, progress, review, and export views.

## Security and data integrity
- If API credentials for one selected integration is unavailable, keep the source record and show a recoverable error instead of a fabricated result.
- Validate imported records and file paths; keep user data within the storage location named in the prompt.
- State the practical limit: native build infrastructure, device integrations, publishing pipeline, and education ecosystem.

## Agent implementation rules
- Project rule, data: Model repositories, builds, deployments, logs, and rollback points; store source IDs and timestamps for each.
- Project rule, behavior: Create a schema editor for text, number, boolean, date, enum, and relation fields.
- Project rule, recovery: If API credentials for one selected integration is unavailable, keep the source record and show a recoverable error instead of a fabricated result.

## 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 internal tools and application builders operation with sample or user-owned data: Create a schema editor for text, number, boolean, date, enum, and relation fields.
- Show a concrete result or export: Add an activity log, CSV import or export, backups, and health checks.
- State the practical limit: native build infrastructure, device integrations, publishing pipeline, and education ecosystem.

## Engineering roadmap
1. Phase 1, architecture and data: Use Next.js 15, TypeScript, Tailwind CSS, PostgreSQL, Drizzle ORM, and Docker Compose. Model repositories, builds, deployments, logs, and rollback points; store source IDs and timestamps for each.
2. Phase 2, implement: Create a schema editor for text, number, boolean, date, enum, and relation fields.
3. Phase 3, implement: Generate list, detail, create, edit, and kanban views from the schema.
4. Phase 4, review and output: Implement role-based read and write rules for admin and member roles. Add an activity log, CSV import or export, backups, and health checks.
5. Phase 5, recovery and acceptance: If API credentials for one selected integration is unavailable, keep the source record and show a recoverable error instead of a fabricated result. 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: native build infrastructure, device integrations, publishing pipeline, and education ecosystem.

## Paid-product capabilities outside this build
- native build infrastructure, device integrations, publishing pipeline, and education ecosystem
- hundreds of connectors
- pixel-perfect app design
- mobile app-store builds
- enterprise permissions and scale

## Implementation prompt
Build me a focused internal tools and application builders workflow for the personal core of Thunkable. Requirements:

- Use Next.js 15, TypeScript, Tailwind CSS, PostgreSQL, Drizzle ORM, and Docker Compose. Model repositories, builds, deployments, logs, and rollback points; store source IDs and timestamps for each.
- Paid product context: Prototype a mobile app with fixed components and local data. Build only this DIY scope: Prototype a mobile app from fixed components, define tables and views, build a constrained CRUD interface over local data or one approved data source, and deploy it for a small trusted team.
- Create a schema editor for text, number, boolean, date, enum, and relation fields.
- Generate list, detail, create, edit, and kanban views from the schema.
- Implement role-based read and write rules for admin and member roles. Support one REST connector with encrypted credentials and explicit field mapping. Add an activity log, CSV import or export, backups, and health checks.
- Use a local web page with input, progress, review, and export views. Required input or access: Docker; self-hosted deploy target.
- Recovery: If API credentials for one selected integration is unavailable, keep the source record and show a recoverable error instead of a fabricated result.
- 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: native build infrastructure, device integrations, publishing pipeline, and education ecosystem; hundreds of connectors. 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.