Hootsuite

Build me a focused social scheduling and content repurposing workflow for the personal core of Hootsuite. Requirements:

- Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and one official social-platform API. Model sources or channels, posts, dated observations, drafts, and reports; keep stable source IDs and timestamps.
- Paid product context: Schedule to one approved network and review a basic content calendar. Build only this DIY scope: Draft and schedule posts to one approved network, preview them accurately, publish through the official API, and retain a searchable content calendar.
- Support drafts, scheduled times, queues, campaigns, tags, and a weekly calendar.
- Connect exactly one social network using its documented OAuth flow.
- Publish through an idempotent background job with retries and clear failure states. Store platform post identifiers and refresh publication status without scraping. Add reusable snippets, local media storage, CSV export, and a token reconnect flow.
- Use a local web page with input, progress, review, and export views. Required input or access: developer application for one social network; OAuth credentials. Keep credentials in .env.
- Recovery: Publish through an idempotent background job with retries and clear failure states.
- 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: connector breadth, social inbox, listening, analytics, governance, and enterprise support; many maintained network APIs. 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 Hootsuite

## Project scope
Draft and schedule posts to one approved network, preview them accurately, publish through the official API, and retain a searchable content calendar.

Catalogue verdict: no. A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Hootsuite, schedule to one approved network and review a basic content calendar. The hard boundary is connector breadth, social inbox, listening, analytics, governance, and enterprise support, plus api access, connector upkeep, and collaboration.
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
- developer application for one social network
- OAuth credentials
- PostgreSQL
- public HTTPS endpoint
- background worker

## Stack and architecture
- Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and one official social-platform API.
- Model sources or channels, posts, dated observations, drafts, and reports; keep stable source IDs and timestamps.
- Interface for this social scheduling and content repurposing workflow: a local web page with input, progress, review, and export views.

## Security and data integrity
- Publish through an idempotent background job with retries and clear failure states.
- Keep API keys and OAuth secrets in .env; redact them from logs, generated files, and error responses.
- State the practical limit: connector breadth, social inbox, listening, analytics, governance, and enterprise support.

## 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: Support drafts, scheduled times, queues, campaigns, tags, and a weekly calendar.
- Project rule, recovery: Publish through an idempotent background job with retries and clear failure states.

## 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 social scheduling and content repurposing operation with sample or user-owned data: Support drafts, scheduled times, queues, campaigns, tags, and a weekly calendar.
- Show a concrete result or export: Add reusable snippets, local media storage, CSV export, and a token reconnect flow.
- State the practical limit: connector breadth, social inbox, listening, analytics, governance, and enterprise support.

## Engineering roadmap
1. Phase 1, architecture and data: Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and one official social-platform API. Model sources or channels, posts, dated observations, drafts, and reports; keep stable source IDs and timestamps.
2. Phase 2, implement: Support drafts, scheduled times, queues, campaigns, tags, and a weekly calendar.
3. Phase 3, implement: Connect exactly one social network using its documented OAuth flow.
4. Phase 4, review and output: Publish through an idempotent background job with retries and clear failure states. Add reusable snippets, local media storage, CSV export, and a token reconnect flow.
5. Phase 5, recovery and acceptance: Publish through an idempotent background job with retries and clear failure states. 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: connector breadth, social inbox, listening, analytics, governance, and enterprise support.

## Paid-product capabilities outside this build
- connector breadth, social inbox, listening, analytics, governance, and enterprise support
- many maintained network APIs
- inbox and moderation
- deep analytics
- team approvals and asset libraries

## Implementation prompt
Build me a focused social scheduling and content repurposing workflow for the personal core of Hootsuite. Requirements:

- Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and one official social-platform API. Model sources or channels, posts, dated observations, drafts, and reports; keep stable source IDs and timestamps.
- Paid product context: Schedule to one approved network and review a basic content calendar. Build only this DIY scope: Draft and schedule posts to one approved network, preview them accurately, publish through the official API, and retain a searchable content calendar.
- Support drafts, scheduled times, queues, campaigns, tags, and a weekly calendar.
- Connect exactly one social network using its documented OAuth flow.
- Publish through an idempotent background job with retries and clear failure states. Store platform post identifiers and refresh publication status without scraping. Add reusable snippets, local media storage, CSV export, and a token reconnect flow.
- Use a local web page with input, progress, review, and export views. Required input or access: developer application for one social network; OAuth credentials. Keep credentials in .env.
- Recovery: Publish through an idempotent background job with retries and clear failure states.
- 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: connector breadth, social inbox, listening, analytics, governance, and enterprise support; many maintained network APIs. 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.