# AGENTS.md — Build guide for Loomly

## Project scope
Plan a small team's posts through draft, changes requested, approved and scheduled states, then publish one approved destination.

Catalogue verdict: kinda. The core loop is buildable, but a dependable replacement becomes a real weekend or multi-day project. For Loomly, plan, approve, and schedule a small team's content calendar. The hard boundary is approval workflow, multi-network publishing, asset library, analytics, and 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
- Runtime and tools: TypeScript, Node, SQLite, a scheduled worker and a React draft/calendar interface.
- Before starting: An approved account for one documented publishing API, its current media/character rules and a sample post; API access and provider charges are separate.

## Stack and architecture
- TypeScript, Node, SQLite, a scheduled worker and a React draft/calendar interface
- Data design: Store PostRevision, ReviewerDecision, Schedule and Receipt; any content/media change invalidates earlier approval and the queued job pins the reviewed revision.
- Setup: An approved account for one documented publishing API, its current media/character rules and a sample post; API access and provider charges are separate

## Security and data integrity
- Freeze the approved content revision at enqueue time. Keep one receipt per destination and stop on revoked credentials or ambiguous publish results; retry only after checking provider state. Offer manual export for unsupported networks.
- Platform previews are approximations until checked against current APIs. Do not publish via personal browser automation or infer approval from silence.
- Keep secrets outside client bundles and exported projects; document what leaves the device and make retention/deletion controls visible.

## Agent implementation rules
- Project rule — domain: Store PostRevision, ReviewerDecision, Schedule and Receipt; any content/media change invalidates earlier approval and the queued job pins the reviewed revision.
- Project rule — scope and recovery: Platform previews are approximations until checked against current APIs. Do not publish via personal browser automation or infer approval from silence.
- Project rule — acceptance: Approve a post, replace its image and attempt scheduling; require renewed approval and retain the prior review discussion in the audit trail.
- Project rule — delivery: document real setup commands and permissions; do not claim a build, accuracy level, performance result or security certification that has not been demonstrated.

## Optional agent skills and references
- Recommended skill: [web-design-guidelines](https://github.com/vercel-labs/agent-skills/blob/main/skills/web-design-guidelines/SKILL.md) — review keyboard access, focus, validation, error recovery and the readable work/review interface or HTML report. Follow the maintainer's installation instructions and match its requirements to the chosen runtime.
- Recommended skill: [sharp-edges](https://github.com/trailofbits/skills/blob/main/plugins/sharp-edges/skills/sharp-edges/SKILL.md) — review configuration and API defaults against the app-specific invariants and recovery boundaries above; this is not a security certification. Follow the maintainer's installation instructions and match its requirements to the chosen runtime.

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 working slice using synthetic or explicitly authorized non-sensitive examples: Plan a small team's posts through draft, changes requested, approved and scheduled states, then publish one approved destination.
- Share a synthetic example export and the acceptance walkthrough; keep real customer, health, financial and source data private: Approve a post, replace its image and attempt scheduling; require renewed approval and retain the prior review discussion in the audit trail.
- State the limits before asking someone to replace their existing tool: Platform previews are approximations until checked against current APIs. Do not publish via personal browser automation or infer approval from silence.

## Engineering roadmap
1. Phase 1 — Pin the working slice and create its example input: Plan a small team's posts through draft, changes requested, approved and scheduled states, then publish one approved destination. Confirm setup: An approved account for one documented publishing API, its current media/character rules and a sample post; API access and provider charges are separate.
2. Phase 2 — Implement persistence and write-time invariants before decorating the UI: Store PostRevision, ReviewerDecision, Schedule and Receipt; any content/media change invalidates earlier approval and the queued job pins the reviewed revision.
3. Phase 3 — Connect the working view to real saved state. Freeze the approved content revision at enqueue time. Keep one receipt per destination and stop on revoked credentials or ambiguous publish results; retry only after checking provider state. Offer manual export for unsupported networks.
4. Phase 4 — Expose the app-specific limits and recovery path in context: Platform previews are approximations until checked against current APIs. Do not publish via personal browser automation or infer approval from silence.
5. Phase 5 — Walk through this concrete acceptance case and preserve its exported evidence: Approve a post, replace its image and attempt scheduling; require renewed approval and retain the prior review discussion in the audit trail. Finish the README and backup/restore instructions; report unfinished capabilities explicitly.

## Paid-product capabilities outside this build
- approval workflow, multi-network publishing, asset library, analytics, and support
- many maintained network APIs
- inbox and moderation
- deep analytics
- team approvals and asset libraries

## Implementation prompt
Build the following focused alternative to Loomly. This is a deliberately limited personal or small-team substitute, not parity with the paid service.

WORKING SLICE
Plan a small team's posts through draft, changes requested, approved and scheduled states, then publish one approved destination.

SETUP AND ARCHITECTURE
Use TypeScript, Node, SQLite, a scheduled worker and a React draft/calendar interface. Prerequisites: An approved account for one documented publishing API, its current media/character rules and a sample post; API access and provider charges are separate. Before integrating anything, record actual versions and permissions, plus model files or provider limits only where used, in the README; make unavailable dependencies visible rather than simulating success.

DOMAIN MODEL AND INVARIANTS
Store PostRevision, ReviewerDecision, Schedule and Receipt; any content/media change invalidates earlier approval and the queued job pins the reviewed revision.

IMPLEMENTATION CONTRACT
Freeze the approved content revision at enqueue time. Keep one receipt per destination and stop on revoked credentials or ambiguous publish results; retry only after checking provider state. Offer manual export for unsupported networks. Provide an input/setup view, the main work view, and a review/export view appropriate to this workflow. Preserve the last saved state if a job or save fails. Include empty, loading, permission-denied, partial and retryable-error states. Log identifiers and error categories without secret values or unnecessary private content.

APP-SPECIFIC BOUNDARY AND RECOVERY
Platform previews are approximations until checked against current APIs. Do not publish via personal browser automation or infer approval from silence.

ACCEPTANCE SCENARIO
Approve a post, replace its image and attempt scheduling; require renewed approval and retain the prior review discussion in the audit trail. Also reopen the app after an interrupted operation, confirm the saved record/export remains inspectable, and document the recovery action. These are implementation acceptance requirements, not a claim that this guide has been tested.

DELIVERY
Deliver a runnable repository with migrations or project-format versioning, a non-sensitive example, environment/permission setup, the exact manual acceptance steps, and a backup/export-and-restore walkthrough. Implement the working slice before optional integrations; list any deferred paid-product capabilities honestly. Do not add capabilities outside the working slice just to resemble the original product.

PROJECT RULES FOR AGENTS.md
Keep the domain invariants above executable at the write boundary. Propose scope changes before adding providers or permissions. Never fabricate source evidence, publish results, identity matches or successful delivery. Preserve user originals and require an explicit confirmation for destructive changes or external publication.

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