HoneyBook

Build me a local client and invoice tracker for a solo service business as a narrow substitute for HoneyBook. Requirements:

- Use Node, Express, better-sqlite3, and server-rendered HTML on localhost. Store clients, projects, proposal drafts, invoices, payment records, and imported bank rows in one SQLite database.
- Create a client and project with contact details, service dates, notes, and a status. Draft a proposal with line items and a quoted total; preserve each revision and mark acceptance manually after a client responds outside the app.
- Turn an accepted proposal into an invoice with a unique number, issue date, due date, currency, line items, and optional deposit requested. Render a printable PDF; do not calculate taxes automatically.
- Record payments and deposits manually with date, amount, method, and reference. Show invoice balance and project total using integer minor currency units; never count a deposit twice.
- Import a bank CSV through a reviewed column mapping. Match rows to recorded payments by amount, date range, and reference for confirmation, keeping unmatched rows visible. Do not mark an invoice paid from a guessed match.
- Export clients, proposals, invoices, payments, and unmatched imports as CSV. Back up SQLite using its supported backup mechanism and provide restore instructions.
- No accounts, telemetry, e-signatures, live payment collection, bank feeds, payroll, tax filing, or accounting-compliance claims. README: data path, manual proposal and payment steps, CSV mapping, backup, and accountant review limits.

# AGENTS.md — Build guide for HoneyBook

## Project scope
Build a private clientflow platform ledger that imports user-supplied CSV files, categorizes entries, reconciles balances, and exports reports.

Catalogue verdict: no. Do not mistake the interface for the product. HoneyBook's durable value is banking, compliance, trust, which a solo one-shot build cannot reproduce responsibly. The prompt therefore builds only the closest honest personal consolation tool.
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
- Node.js 22
- SQLite
- CSV exports from the user's own accounts
- Explicit README warning that this is a consolation build, not a production replacement

## Stack and architecture
- Node and Express
- better-sqlite3
- Server-rendered HTML
- Printable invoice PDF and CSV export

## Security and data integrity
- Bind to localhost and do not store bank credentials
- Use integer minor currency units and prevent duplicate payment references per invoice
- Preserve proposal revisions and original imported bank rows
- Use SQLite backup operations for consistent snapshots

## Agent implementation rules
- Keep proposal revisions, invoice lineage, and payment allocations traceable
- Require user confirmation before matching imported bank rows to payments

## 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.
- Describe a solo client, proposal, and invoice workflow without payment or accounting-service claims

## Engineering roadmap
1. Model clients, projects, versioned proposal drafts, invoices, payments, and bank import batches.
2. Build proposal drafting, manual acceptance, invoice conversion, and deposit/balance views.
3. Add reviewed CSV matching, unmatched rows, export, and backup; document missing signatures and payment rails.

## Paid-product capabilities outside this build
- multi-user controls and accountant workflows
- calendar-provider edge cases and timezone correctness
- live bank feeds and payment rails
- tax and accounting rule updates
- audited security and recovery

## Implementation prompt
Build me a local client and invoice tracker for a solo service business as a narrow substitute for HoneyBook. Requirements:

- Use Node, Express, better-sqlite3, and server-rendered HTML on localhost. Store clients, projects, proposal drafts, invoices, payment records, and imported bank rows in one SQLite database.
- Create a client and project with contact details, service dates, notes, and a status. Draft a proposal with line items and a quoted total; preserve each revision and mark acceptance manually after a client responds outside the app.
- Turn an accepted proposal into an invoice with a unique number, issue date, due date, currency, line items, and optional deposit requested. Render a printable PDF; do not calculate taxes automatically.
- Record payments and deposits manually with date, amount, method, and reference. Show invoice balance and project total using integer minor currency units; never count a deposit twice.
- Import a bank CSV through a reviewed column mapping. Match rows to recorded payments by amount, date range, and reference for confirmation, keeping unmatched rows visible. Do not mark an invoice paid from a guessed match.
- Export clients, proposals, invoices, payments, and unmatched imports as CSV. Back up SQLite using its supported backup mechanism and provide restore instructions.
- No accounts, telemetry, e-signatures, live payment collection, bank feeds, payroll, tax filing, or accounting-compliance claims. README: data path, manual proposal and payment steps, CSV mapping, backup, and accountant review limits.

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