AuthoredUp

Build me a local LinkedIn post planner as a limited substitute for AuthoredUp. Requirements:

- Use Node, Express, and better-sqlite3 on localhost. Store draft text, optional local media path, tags, intended publish time, status, and a revision history.
- Show an editor with a plain text LinkedIn-style preview, character count, and a queue ordered by planned date. Keep draft, ready, and manually published states distinct.
- Add reusable text snippets and a calendar of planned posts. Export one post as text plus its media files, or export the queue as CSV and Markdown.
- A publish checklist lets me copy the text and open LinkedIn. I confirm the public post URL after posting; never mark an item published simply because its scheduled time passed.
- Search drafts by text and tag. Preserve prior versions when editing and make accidental status changes reversible.
- No accounts, telemetry, browser automation, scraping, platform analytics, or API publishing by default. LinkedIn API access varies by permission and approved product; explain any future API integration separately.
- README: local data path, backup and restore, media handling, and the manual publishing workflow.

# AGENTS.md — Build guide for AuthoredUp

## Project scope
Build a personal LinkedIn publishing 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. AuthoredUp'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
- Node and Express
- better-sqlite3
- Server-rendered HTML
- Local media files and CSV/Markdown export

## Security and data integrity
- Bind to localhost and do not store LinkedIn credentials
- Preserve drafts and revisions during manual publication
- Avoid scraping and browser automation

## Agent implementation rules
- Keep scheduled and published states separate
- Require the user to record the actual public post URL

## 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.
- Describe a drafting and manual publishing planner, not a posting or analytics integration

## Engineering roadmap
1. Build drafts, revisions, tags, snippets, and the queue calendar.
2. Add preview, manual publish checklist, and explicit post URL confirmation.
3. Export posts and document missing API publishing and analytics.

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

## Implementation prompt
Build me a local LinkedIn post planner as a limited substitute for AuthoredUp. Requirements:

- Use Node, Express, and better-sqlite3 on localhost. Store draft text, optional local media path, tags, intended publish time, status, and a revision history.
- Show an editor with a plain text LinkedIn-style preview, character count, and a queue ordered by planned date. Keep draft, ready, and manually published states distinct.
- Add reusable text snippets and a calendar of planned posts. Export one post as text plus its media files, or export the queue as CSV and Markdown.
- A publish checklist lets me copy the text and open LinkedIn. I confirm the public post URL after posting; never mark an item published simply because its scheduled time passed.
- Search drafts by text and tag. Preserve prior versions when editing and make accidental status changes reversible.
- No accounts, telemetry, browser automation, scraping, platform analytics, or API publishing by default. LinkedIn API access varies by permission and approved product; explain any future API integration separately.
- README: local data path, backup and restore, media handling, and the manual publishing workflow.

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