Repurpose.io

Build me a focused content repurposing workflow for the personal core of Repurpose.io. 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: Automatically reformats and publishes audio and video across platforms. Build only this DIY scope: Build a personal content repurposing planner that stores drafts, previews platform variants, and exports a posting queue without pretending to bypass platform APIs.
- For content repurposing, save a platform-specific draft with text, media references, and intended publish time.
- Preview the selected platform variant and queue only actions supported by its current official API.
- Show delivery receipts or export the posting queue for manual publishing.
- 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: A failed platform call retains the draft and cannot be marked published; retries use a stable delivery key.
- Out of scope: team approvals and asset workflows; protection from API and policy changes. 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 Repurpose.io

## Project scope
Build a personal content repurposing 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. Repurpose.io'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 content repurposing workflow: a local web page with input, progress, review, and export views.

## Security and data integrity
- A failed platform call retains the draft and cannot be marked published; retries use a stable delivery key.
- Keep API keys and OAuth secrets in .env; redact them from logs, generated files, and error responses.
- State the practical limit: team approvals and asset workflows.

## 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 content repurposing, save a platform-specific draft with text, media references, and intended publish time.
- Project rule, recovery: A failed platform call retains the draft and cannot be marked published; retries use a stable delivery key.

## 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 content repurposing operation with sample or user-owned data: For content repurposing, save a platform-specific draft with text, media references, and intended publish time.
- Show a concrete result or export: Show delivery receipts or export the posting queue for manual publishing.
- State the practical limit: team approvals and asset workflows.

## 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 content repurposing, save a platform-specific draft with text, media references, and intended publish time.
3. Phase 3, implement: Preview the selected platform variant and queue only actions supported by its current official API.
4. Phase 4, review and output: Show delivery receipts or export the posting queue for manual publishing.
5. Phase 5, recovery and acceptance: Verify this invariant with a saved fixture: A failed platform call retains the draft and cannot be marked published; retries use a stable delivery key. State the practical limit: team approvals and asset workflows.

## Paid-product capabilities outside this build
- team approvals and asset workflows
- protection from API and policy changes
- production codecs, rendering speed, and media templates
- reliable direct publishing across networks
- analytics history and attribution

## Implementation prompt
Build me a focused content repurposing workflow for the personal core of Repurpose.io. 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: Automatically reformats and publishes audio and video across platforms. Build only this DIY scope: Build a personal content repurposing planner that stores drafts, previews platform variants, and exports a posting queue without pretending to bypass platform APIs.
- For content repurposing, save a platform-specific draft with text, media references, and intended publish time.
- Preview the selected platform variant and queue only actions supported by its current official API.
- Show delivery receipts or export the posting queue for manual publishing.
- 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: A failed platform call retains the draft and cannot be marked published; retries use a stable delivery key.
- Out of scope: team approvals and asset workflows; protection from API and policy changes. 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.