Social Fetch

Build me a focused social media scraper API workflow for the personal core of Social Fetch. Requirements:

- Stack (fixed): Node 22, TypeScript, Express, better-sqlite3, Playwright, Zod. No alternative stacks. Model selected repositories or projects, operations, results, revisions, and run logs; keep stable source IDs and timestamps.
- Paid product context: REST API for profiles, posts, transcripts, and engagement metrics across 20+ platforms. Build only this DIY scope: Fetch public profile and recent posts for one platform (TikTok or Instagram), normalize into JSON, cache in SQLite, expose a tiny local HTTP API.
- For social media scraper API, define a typed request/response or schema contract with one realistic example.
- Implement the narrow supported operation and persist its inputs, outputs, and version.
- Expose a CLI or local inspection view plus a copyable example and error documentation.
- Use a local web page with input, progress, review, and export views. Required input or access: Node + Playwright (or similar); optional residential proxy for anything beyond light personal use.
- Recovery: Invalid input must return a typed error; the same fixture must produce the documented output after restart.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: Invalid input must return a typed error; the same fixture must produce the documented output after restart.
- Out of scope: 20+ platforms on one schema and one API key; proxy / anti-bot / captcha handling. 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 Social Fetch

## Project scope
Fetch public profile and recent posts for one platform (TikTok or Instagram), normalize into JSON, cache in SQLite, expose a tiny local HTTP API.

Catalogue verdict: no. A personal TikTok or Instagram profile fetcher with Playwright and SQLite is a one-sitting build. Social Fetch is not that. It is kept-alive scrapers on 20+ platforms, proxy routing, anti-bot handling, a stable response schema, and credit metering. Your DIY script breaks when TikTok changes markup. The API bill is for that not being your problem.
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 + Playwright (or similar)
- SQLite
- optional residential proxy for anything beyond light personal use

## Stack and architecture
- Stack (fixed): Node 22, TypeScript, Express, better-sqlite3, Playwright, Zod. No alternative stacks.
- Model selected repositories or projects, operations, results, revisions, and run logs; keep stable source IDs and timestamps.
- Interface for this social media scraper API workflow: a local web page with input, progress, review, and export views.

## Security and data integrity
- Invalid input must return a typed error; the same fixture must produce the documented output after restart.
- Validate imported records and file paths; keep user data within the storage location named in the prompt.
- State the practical limit: 20+ platforms on one schema and one API key.

## Agent implementation rules
- Project rule, data: Model selected repositories or projects, operations, results, revisions, and run logs; keep stable source IDs and timestamps.
- Project rule, behavior: For social media scraper API, define a typed request/response or schema contract with one realistic example.
- Project rule, recovery: Invalid input must return a typed error; the same fixture must produce the documented output after restart.

## 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 media scraper API operation with sample or user-owned data: For social media scraper API, define a typed request/response or schema contract with one realistic example.
- Show a concrete result or export: Expose a CLI or local inspection view plus a copyable example and error documentation.
- State the practical limit: 20+ platforms on one schema and one API key.

## Engineering roadmap
1. Phase 1, architecture and data: Stack (fixed): Node 22, TypeScript, Express, better-sqlite3, Playwright, Zod. No alternative stacks. Model selected repositories or projects, operations, results, revisions, and run logs; keep stable source IDs and timestamps.
2. Phase 2, implement: For social media scraper API, define a typed request/response or schema contract with one realistic example.
3. Phase 3, implement: Implement the narrow supported operation and persist its inputs, outputs, and version.
4. Phase 4, review and output: Expose a CLI or local inspection view plus a copyable example and error documentation.
5. Phase 5, recovery and acceptance: Verify this invariant with a saved fixture: Invalid input must return a typed error; the same fixture must produce the documented output after restart. State the practical limit: 20+ platforms on one schema and one API key.

## Paid-product capabilities outside this build
- 20+ platforms on one schema and one API key
- proxy / anti-bot / captcha handling
- someone else patching when platforms break
- production metering, request IDs, and uptime
- monitors, webhooks, and batch enrichment at volume

## Implementation prompt
Build me a focused social media scraper API workflow for the personal core of Social Fetch. Requirements:

- Stack (fixed): Node 22, TypeScript, Express, better-sqlite3, Playwright, Zod. No alternative stacks. Model selected repositories or projects, operations, results, revisions, and run logs; keep stable source IDs and timestamps.
- Paid product context: REST API for profiles, posts, transcripts, and engagement metrics across 20+ platforms. Build only this DIY scope: Fetch public profile and recent posts for one platform (TikTok or Instagram), normalize into JSON, cache in SQLite, expose a tiny local HTTP API.
- For social media scraper API, define a typed request/response or schema contract with one realistic example.
- Implement the narrow supported operation and persist its inputs, outputs, and version.
- Expose a CLI or local inspection view plus a copyable example and error documentation.
- Use a local web page with input, progress, review, and export views. Required input or access: Node + Playwright (or similar); optional residential proxy for anything beyond light personal use.
- Recovery: Invalid input must return a typed error; the same fixture must produce the documented output after restart.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: Invalid input must return a typed error; the same fixture must produce the documented output after restart.
- Out of scope: 20+ platforms on one schema and one API key; proxy / anti-bot / captcha handling. 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.