Tweet Hunter

Build me a focused X growth workflow for the personal core of Tweet Hunter. Requirements:

- Use exactly this stack: Next.js 15 + TypeScript + PostgreSQL + BullMQ. Model sources or channels, posts, dated observations, drafts, and reports; keep stable source IDs and timestamps.
- Paid product context: AI writing, scheduling, automation, lead tools, and analytics for X. Build only this DIY scope: Build a personal X growth planner that stores drafts, previews platform variants, and exports a posting queue without pretending to bypass platform APIs.
- For X growth, connect one permitted source or import a user-owned metrics export.
- Store dated raw observations and calculate the named summary from those records.
- Show a report with source, time range, and CSV export.
- Use a local web page with input, progress, review, and export views. Required input or access: hosted database and worker; official platform OAuth credentials where available. Keep credentials in .env.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: An API gap must be labelled missing; a replayed export cannot double-count the same observation.
- Out of scope: calendar-provider edge cases and timezone correctness; reliable direct publishing across networks. 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 Tweet Hunter

## Project scope
Build a personal X growth planner that stores drafts, previews platform variants, and exports a posting queue without pretending to bypass platform APIs.

Catalogue verdict: no. Do not mistake the interface for the product. Tweet Hunter's durable value is platform APIs, distribution, 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
- hosted database and worker
- official platform OAuth credentials where available
- Explicit README warning that this is a consolation build, not a production replacement

## Stack and architecture
- Use exactly this stack: Next.js 15 + TypeScript + PostgreSQL + BullMQ.
- Model sources or channels, posts, dated observations, drafts, and reports; keep stable source IDs and timestamps.
- Interface for this X growth workflow: a local web page with input, progress, review, and export views.

## Security and data integrity
- An API gap must be labelled missing; a replayed export cannot double-count the same observation.
- Keep API keys and OAuth secrets in .env; redact them from logs, generated files, and error responses.
- State the practical limit: calendar-provider edge cases and timezone correctness.

## Agent implementation rules
- Project rule, data: Model sources or channels, posts, dated observations, drafts, and reports; keep stable source IDs and timestamps.
- Project rule, behavior: For X growth, connect one permitted source or import a user-owned metrics export.
- Project rule, recovery: An API gap must be labelled missing; a replayed export cannot double-count the same observation.

## 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 X growth operation with sample or user-owned data: For X growth, connect one permitted source or import a user-owned metrics export.
- Show a concrete result or export: Show a report with source, time range, and CSV export.
- State the practical limit: calendar-provider edge cases and timezone correctness.

## Engineering roadmap
1. Phase 1, architecture and data: Use exactly this stack: Next.js 15 + TypeScript + PostgreSQL + BullMQ. Model sources or channels, posts, dated observations, drafts, and reports; keep stable source IDs and timestamps.
2. Phase 2, implement: For X growth, connect one permitted source or import a user-owned metrics export.
3. Phase 3, implement: Store dated raw observations and calculate the named summary from those records.
4. Phase 4, review and output: Show a report with source, time range, and CSV export.
5. Phase 5, recovery and acceptance: Verify this invariant with a saved fixture: An API gap must be labelled missing; a replayed export cannot double-count the same observation. State the practical limit: calendar-provider edge cases and timezone correctness.

## Paid-product capabilities outside this build
- calendar-provider edge cases and timezone correctness
- reliable direct publishing across networks
- analytics history and attribution
- team approvals and asset workflows
- protection from API and policy changes

## Implementation prompt
Build me a focused X growth workflow for the personal core of Tweet Hunter. Requirements:

- Use exactly this stack: Next.js 15 + TypeScript + PostgreSQL + BullMQ. Model sources or channels, posts, dated observations, drafts, and reports; keep stable source IDs and timestamps.
- Paid product context: AI writing, scheduling, automation, lead tools, and analytics for X. Build only this DIY scope: Build a personal X growth planner that stores drafts, previews platform variants, and exports a posting queue without pretending to bypass platform APIs.
- For X growth, connect one permitted source or import a user-owned metrics export.
- Store dated raw observations and calculate the named summary from those records.
- Show a report with source, time range, and CSV export.
- Use a local web page with input, progress, review, and export views. Required input or access: hosted database and worker; official platform OAuth credentials where available. Keep credentials in .env.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: An API gap must be labelled missing; a replayed export cannot double-count the same observation.
- Out of scope: calendar-provider edge cases and timezone correctness; reliable direct publishing across networks. 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.