WithJuly

Build a local-first sponsorship deal tracker for a single creator. Consolation build: this replaces the paperwork, not the deal flow.

Stack, no substitutions:
- Next.js 15 App Router, TypeScript, Tailwind
- SQLite via Drizzle ORM, file at ./data/deals.db
- No auth, no accounts, no telemetry, no external SaaS calls
- Runs with: npm install, npm run db:push, npm run dev

Data model:
- brand: name, contactName, contactEmail, notes
- deal: brandId, status (inbound, negotiating, agreed, in-production, delivered, invoiced, paid, dead), platform, deliverables (text), grossFee (integer cents), currency, usageRights (text), exclusivity (text), agreedAt, dueAt, invoicedAt, paidAt, notes
- rateNote: platform, audienceSize, deliverableType, feeCents, dateClosed, source (mine or reported), notes
- asset: dealId, label, url

Pages:
1. /pipeline: kanban board by deal status, drag to move, inline edit of fee and due date. Show totals per column in currency.
2. /deals/[id]: full deal detail, deliverable checklist stored as JSON, timeline of status changes, asset links.
3. /rates: table of rateNote rows plus a simple median and range calculator filtered by platform and deliverable type. Make it obvious that this is your own data only and that an empty table means you know nothing yet.
4. /money: unpaid deals sorted by days overdue, computed from invoicedAt, with a copy-to-clipboard chase email drafted from a template.
5. /kit: a printable one-page media kit. Audience numbers are typed in by hand and stored in a single settings row. Include a static export script that writes ./out/kit.html for hosting anywhere.

Explicitly out of scope, do not build: brand discovery, any marketplace or matching, contract e-signing, payment processing, OAuth to YouTube, TikTok or Instagram, benchmark data you did not enter yourself.

Include seed data with three fake brands and six deals across statuses. Put any future API keys in .env.example, none are required to run. README: one paragraph on setup, one paragraph stating plainly that this tracks deals and does not source them.

# AGENTS.md — Build guide for WithJuly

## Project scope
A local dashboard with a public media kit page, a deal pipeline board, rate notes, deliverable checklists and payment reminders.

Catalogue verdict: no. The software layer here is thin: a media kit page, a deal pipeline, some invoices and reminders. The part that matters is on the other side of the table, meaning actual brand relationships, inbound demand, and rate data from deals that already closed. An agent can build you a very tidy place to track sponsorships you do not have yet. It cannot tell you what a 40k-subscriber tech channel really gets paid for a 60 second integration, and it cannot make a marketing manager email you. Build the tracker if you want, but do not confuse it with the thing being replaced.
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 20 and a local Postgres or SQLite file
- A domain or subdomain if you want the media kit page to be public
- Your own audience numbers, pulled or pasted in manually
- Optional: a Stripe or invoicing tool for the actual money

## Stack and architecture
- SQLite via Drizzle ORM, file at ./data/deals.db.
- Data model:.
- Interface for this creator brand deals and sponsorship management workflow: a focused creator brand deals and sponsorship management input, review, and export interface.

## Security and data integrity
- On invalid input or interrupted processing, keep the original record, show the failed step, and permit a safe retry.
- Keep API keys and OAuth secrets in .env; redact them from logs, generated files, and error responses.
- State the practical limit: Inbound brand demand: no deals arrive because you built a pipeline.

## Agent implementation rules
- Project rule, data: Data model:.
- Project rule, behavior: Runs with: npm install, npm run db:push, npm run dev.
- Project rule, recovery: On invalid input or interrupted processing, keep the original record, show the failed step, and permit a safe retry.

## 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 creator brand deals and sponsorship management operation with sample or user-owned data: Runs with: npm install, npm run db:push, npm run dev.
- Show a concrete result or export: /kit: a printable one-page media kit. Audience numbers are typed in by hand and stored in a single settings row. Include a static export script that writes ./out/kit.html for hosting anywhere.
- State the practical limit: Inbound brand demand: no deals arrive because you built a pipeline.

## Engineering roadmap
1. Phase 1, architecture and data: SQLite via Drizzle ORM, file at ./data/deals.db. Data model:.
2. Phase 2, implement: Runs with: npm install, npm run db:push, npm run dev.
3. Phase 3, implement: brand: name, contactName, contactEmail, notes.
4. Phase 4, review and output: deal: brandId, status (inbound, negotiating, agreed, in-production, delivered, invoiced, paid, dead), platform, deliverables (text), grossFee (integer cents), currency, usageRights (text), exclusivity (text), agreedAt, dueAt, invoicedAt, paidAt, notes. /kit: a printable one-page media kit. Audience numbers are typed in by hand and stored in a single settings row. Include a static export script that writes ./out/kit.html for hosting anywhere.
5. Phase 5, recovery and acceptance: On invalid input or interrupted processing, keep the original record, show the failed step, and permit a safe retry. Verify this invariant with a saved fixture: A repeated payment webhook cannot deliver twice; a refund must revoke the relevant access without deleting the audit trail. State the practical limit: Inbound brand demand: no deals arrive because you built a pipeline.

## Paid-product capabilities outside this build
- Inbound brand demand: no deals arrive because you built a pipeline
- Benchmark rate data from real closed deals across comparable creators
- A human or process pushing negotiation and follow up on your behalf
- Brand-side trust, contracting and payment collection when a sponsor goes quiet
- Deal terms review, exclusivity and usage-rights sanity checks

## Implementation prompt
Build a local-first sponsorship deal tracker for a single creator. Consolation build: this replaces the paperwork, not the deal flow.

Stack, no substitutions:
- Next.js 15 App Router, TypeScript, Tailwind
- SQLite via Drizzle ORM, file at ./data/deals.db
- No auth, no accounts, no telemetry, no external SaaS calls
- Runs with: npm install, npm run db:push, npm run dev

Data model:
- brand: name, contactName, contactEmail, notes
- deal: brandId, status (inbound, negotiating, agreed, in-production, delivered, invoiced, paid, dead), platform, deliverables (text), grossFee (integer cents), currency, usageRights (text), exclusivity (text), agreedAt, dueAt, invoicedAt, paidAt, notes
- rateNote: platform, audienceSize, deliverableType, feeCents, dateClosed, source (mine or reported), notes
- asset: dealId, label, url

Pages:
1. /pipeline: kanban board by deal status, drag to move, inline edit of fee and due date. Show totals per column in currency.
2. /deals/[id]: full deal detail, deliverable checklist stored as JSON, timeline of status changes, asset links.
3. /rates: table of rateNote rows plus a simple median and range calculator filtered by platform and deliverable type. Make it obvious that this is your own data only and that an empty table means you know nothing yet.
4. /money: unpaid deals sorted by days overdue, computed from invoicedAt, with a copy-to-clipboard chase email drafted from a template.
5. /kit: a printable one-page media kit. Audience numbers are typed in by hand and stored in a single settings row. Include a static export script that writes ./out/kit.html for hosting anywhere.

Explicitly out of scope, do not build: brand discovery, any marketplace or matching, contract e-signing, payment processing, OAuth to YouTube, TikTok or Instagram, benchmark data you did not enter yourself.

Include seed data with three fake brands and six deals across statuses. Put any future API keys in .env.example, none are required to run. README: one paragraph on setup, one paragraph stating plainly that this tracks deals and does not source them.

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