Vibecode Voidpet Garden

You are building a lean indie version of Voidpet Garden.

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

## Goal

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

## Scope

Log a mood and reflection locally, grow an original creature garden from the entries, review patterns over time and export the journal whenever you want.

## 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:
- Voidpet's original creature art, animations, names and worldbuilding
- the polished native mobile experience and app-store distribution
- the curated prompt, exercise, affirmation and meditation library
- the accumulated collection, journal history and ongoing content updates
- Giga perks such as cosmetics, larger pet limits and team templates

If those capabilities are essential, use Nightlio 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 private mobile mood journal with a creature garden to replace Voidpet Garden. Requirements:

- Use React Native with Expo, TypeScript, Expo Router and expo-sqlite; do not offer alternative stacks.
- The check-in screen lets me choose one of 12 emotion names, set intensity from 1 to 5, answer an original reflection prompt and save the entry locally.
- Turn each logged emotion into an original abstract creature or plant made from local SVG or vector shapes; entries grow the garden and unlock simple stages.
  Do not copy Voidpet names, art, characters or text.
- Add Garden, Check-in, History and Settings screens. History shows a 7-day mood timeline,
  emotion filters and an editable entry detail view.
- Seed 20 neutral prompts across gratitude, goals, emotional naming, relationships, body awareness
  and coping; label them as reflections, not therapy or medical advice.
- Store entries, creatures, prompt completions and settings in SQLite; add JSON export and a Delete all data action.
- Work fully offline with no accounts, telemetry, cloud sync or API keys. Keep all assets local.
- Include accessible labels, large touch targets, reduced-motion handling, empty states, validation
  and a first-run privacy note saying the app is not medical care.
- Out of scope: social features, clinical assessment, AI advice, subscriptions, notifications and App Store or Play Store release configuration.
- Include a README with setup commands, Expo permissions, the data model, export and backup instructions and the limits of using this as a personal reflective tool.


## Required capabilities

- React Native with Expo
- local SQLite storage
- iOS or Android device or emulator
- original creature illustrations or simple vector shapes

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

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

## Goal

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

## Scope

Log a mood and reflection locally, grow an original creature garden from the entries, review patterns over time and export the journal whenever you want.

## 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:
- Voidpet's original creature art, animations, names and worldbuilding
- the polished native mobile experience and app-store distribution
- the curated prompt, exercise, affirmation and meditation library
- the accumulated collection, journal history and ongoing content updates
- Giga perks such as cosmetics, larger pet limits and team templates

If those capabilities are essential, use Nightlio 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 private mobile mood journal with a creature garden to replace Voidpet Garden. Requirements:

- Use React Native with Expo, TypeScript, Expo Router and expo-sqlite; do not offer alternative stacks.
- The check-in screen lets me choose one of 12 emotion names, set intensity from 1 to 5, answer an original reflection prompt and save the entry locally.
- Turn each logged emotion into an original abstract creature or plant made from local SVG or vector shapes; entries grow the garden and unlock simple stages.
  Do not copy Voidpet names, art, characters or text.
- Add Garden, Check-in, History and Settings screens. History shows a 7-day mood timeline,
  emotion filters and an editable entry detail view.
- Seed 20 neutral prompts across gratitude, goals, emotional naming, relationships, body awareness
  and coping; label them as reflections, not therapy or medical advice.
- Store entries, creatures, prompt completions and settings in SQLite; add JSON export and a Delete all data action.
- Work fully offline with no accounts, telemetry, cloud sync or API keys. Keep all assets local.
- Include accessible labels, large touch targets, reduced-motion handling, empty states, validation
  and a first-run privacy note saying the app is not medical care.
- Out of scope: social features, clinical assessment, AI advice, subscriptions, notifications and App Store or Play Store release configuration.
- Include a README with setup commands, Expo permissions, the data model, export and backup instructions and the limits of using this as a personal reflective tool.


## Required capabilities

- React Native with Expo
- local SQLite storage
- iOS or Android device or emulator
- original creature illustrations or simple vector shapes

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

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

## Problem

The private core is a weekend build: journal entries, mood check-ins, reflection prompts and a local garden of original creatures are straightforward to model. Matching Voidpet Garden means more than reproducing that loop: the polished mobile experience, original creature universe, curated mental-health content and accumulated collection are real gaps. Build the personal version, but do not pretend it has Voidpet's art, writing, store distribution or ongoing content pipeline.

## Product outcome

Log a mood and reflection locally, grow an original creature garden from the entries, review patterns over time and export the journal whenever you want.

## Target user

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

## Required capabilities

- React Native with Expo
- local SQLite storage
- iOS or Android device or emulator
- original creature illustrations or simple vector shapes

## Explicit non-goals for v1

- Voidpet's original creature art, animations, names and worldbuilding
- the polished native mobile experience and app-store distribution
- the curated prompt, exercise, affirmation and meditation library
- the accumulated collection, journal history and ongoing content updates
- Giga perks such as cosmetics, larger pet limits and team templates

## 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 private mobile mood journal with a creature garden to replace Voidpet Garden. Requirements:

- Use React Native with Expo, TypeScript, Expo Router and expo-sqlite; do not offer alternative stacks.
- The check-in screen lets me choose one of 12 emotion names, set intensity from 1 to 5, answer an original reflection prompt and save the entry locally.
- Turn each logged emotion into an original abstract creature or plant made from local SVG or vector shapes; entries grow the garden and unlock simple stages.
  Do not copy Voidpet names, art, characters or text.
- Add Garden, Check-in, History and Settings screens. History shows a 7-day mood timeline,
  emotion filters and an editable entry detail view.
- Seed 20 neutral prompts across gratitude, goals, emotional naming, relationships, body awareness
  and coping; label them as reflections, not therapy or medical advice.
- Store entries, creatures, prompt completions and settings in SQLite; add JSON export and a Delete all data action.
- Work fully offline with no accounts, telemetry, cloud sync or API keys. Keep all assets local.
- Include accessible labels, large touch targets, reduced-motion handling, empty states, validation
  and a first-run privacy note saying the app is not medical care.
- Out of scope: social features, clinical assessment, AI advice, subscriptions, notifications and App Store or Play Store release configuration.
- Include a README with setup commands, Expo permissions, the data model, export and backup instructions and the limits of using this as a personal reflective tool.


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

# Voidpet Garden indie build

## Goal

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

## Scope

Log a mood and reflection locally, grow an original creature garden from the entries, review patterns over time and export the journal whenever you want.

## 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:
- Voidpet's original creature art, animations, names and worldbuilding
- the polished native mobile experience and app-store distribution
- the curated prompt, exercise, affirmation and meditation library
- the accumulated collection, journal history and ongoing content updates
- Giga perks such as cosmetics, larger pet limits and team templates

If those capabilities are essential, use Nightlio 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 private mobile mood journal with a creature garden to replace Voidpet Garden. Requirements:

- Use React Native with Expo, TypeScript, Expo Router and expo-sqlite; do not offer alternative stacks.
- The check-in screen lets me choose one of 12 emotion names, set intensity from 1 to 5, answer an original reflection prompt and save the entry locally.
- Turn each logged emotion into an original abstract creature or plant made from local SVG or vector shapes; entries grow the garden and unlock simple stages.
  Do not copy Voidpet names, art, characters or text.
- Add Garden, Check-in, History and Settings screens. History shows a 7-day mood timeline,
  emotion filters and an editable entry detail view.
- Seed 20 neutral prompts across gratitude, goals, emotional naming, relationships, body awareness
  and coping; label them as reflections, not therapy or medical advice.
- Store entries, creatures, prompt completions and settings in SQLite; add JSON export and a Delete all data action.
- Work fully offline with no accounts, telemetry, cloud sync or API keys. Keep all assets local.
- Include accessible labels, large touch targets, reduced-motion handling, empty states, validation
  and a first-run privacy note saying the app is not medical care.
- Out of scope: social features, clinical assessment, AI advice, subscriptions, notifications and App Store or Play Store release configuration.
- Include a README with setup commands, Expo permissions, the data model, export and backup instructions and the limits of using this as a personal reflective tool.


## Required capabilities

- React Native with Expo
- local SQLite storage
- iOS or Android device or emulator
- original creature illustrations or simple vector shapes

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

# Voidpet Garden product brief

## Problem

The private core is a weekend build: journal entries, mood check-ins, reflection prompts and a local garden of original creatures are straightforward to model. Matching Voidpet Garden means more than reproducing that loop: the polished mobile experience, original creature universe, curated mental-health content and accumulated collection are real gaps. Build the personal version, but do not pretend it has Voidpet's art, writing, store distribution or ongoing content pipeline.

## Product outcome

Log a mood and reflection locally, grow an original creature garden from the entries, review patterns over time and export the journal whenever you want.

## Target user

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

## Required capabilities

- React Native with Expo
- local SQLite storage
- iOS or Android device or emulator
- original creature illustrations or simple vector shapes

## Explicit non-goals for v1

- Voidpet's original creature art, animations, names and worldbuilding
- the polished native mobile experience and app-store distribution
- the curated prompt, exercise, affirmation and meditation library
- the accumulated collection, journal history and ongoing content updates
- Giga perks such as cosmetics, larger pet limits and team templates

## 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 private mobile mood journal with a creature garden to replace Voidpet Garden. Requirements:

- Use React Native with Expo, TypeScript, Expo Router and expo-sqlite; do not offer alternative stacks.
- The check-in screen lets me choose one of 12 emotion names, set intensity from 1 to 5, answer an original reflection prompt and save the entry locally.
- Turn each logged emotion into an original abstract creature or plant made from local SVG or vector shapes; entries grow the garden and unlock simple stages.
  Do not copy Voidpet names, art, characters or text.
- Add Garden, Check-in, History and Settings screens. History shows a 7-day mood timeline,
  emotion filters and an editable entry detail view.
- Seed 20 neutral prompts across gratitude, goals, emotional naming, relationships, body awareness
  and coping; label them as reflections, not therapy or medical advice.
- Store entries, creatures, prompt completions and settings in SQLite; add JSON export and a Delete all data action.
- Work fully offline with no accounts, telemetry, cloud sync or API keys. Keep all assets local.
- Include accessible labels, large touch targets, reduced-motion handling, empty states, validation
  and a first-run privacy note saying the app is not medical care.
- Out of scope: social features, clinical assessment, AI advice, subscriptions, notifications and App Store or Play Store release configuration.
- Include a README with setup commands, Expo permissions, the data model, export and backup instructions and the limits of using this as a personal reflective tool.


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