@easysociable/cli 0.1.8 → 0.1.10

package/content-engine/starter/platforms/x.md

@@ -1,78 +0,0 @@
-# Platform: X (Twitter)
-
-**Scope:** How to *write* for X — length, rhythm, quality bars.  
-**Not in this file:** Who you are, product story, pillars, voice, audience.  
-Those live under `profiles/<id>/` (via account → profile resolve).  
-**Pixels / canvas:** Optional; if images, EasySociable `PLATFORM_SPECS` for **x** (often wide ~1200×675 or `1:1` for multi-image).
-
-Agent: before drafting any X post, read this file for craft. For topics/tone/readers, use resolved profile files.
-
----
-
-## Defaults
-
-- Language: English (unless user asks otherwise)
-- Default unit: **1 short post** (not a thread), unless user asks for a thread
-- Assume timeline scroll: **first line** does most of the work
-- Success for easysociable-builder: **qualified replies / DMs**, not raw impressions
-- Pack: **optional**. Text-first; add carousel/images when showing the visual production layer
-
-## Length & shape
-
-| Form | Guidance |
-|------|----------|
-| Single post | Prefer **1–3 short sentences** or tight line breaks. Rarely fill the full character limit. |
-| Thread | Only if user asks. Tweet 1 = hook only; each next tweet = one idea; end without a summary paragraph that restates everything. |
-| Reply | Add information or a precise question. Avoid “Great point!” / empty agreement. |
-| Media | Optional. If used, text should still stand alone if the image fails. Carousel images = proof of system, not the default body. |
-
-## Hooks (mechanics only — not your brand story)
-
-A strong first line usually does **one** of:
-
-- Names a **concrete mistake** or false belief
-- States a **sharp contrast** (X vs Y)
-- Opens a **gap** the rest of the post closes
-- Gives a **specific** observation (not “in today’s world…”)
-
-Avoid first lines that only announce a topic list (“Here are 3 tips to…”).
-
-## Craft rules
-
-1. **One idea per post** (or per thread tweet).
-2. Prefer concrete nouns and verbs over abstract “value / leverage / unlock”.
-3. Cut filler and restatements. No closing that only summarizes what was already said.
-4. Line breaks are for rhythm, not for fake drama on every word.
-5. Questions: use when you want replies; make them answerable, not vague (“thoughts?”).
-6. Links: prefer zero or one; if needed, put after the point lands — not as the whole post.
-7. Optimize for **classifiable takes** and conversation — authority/signal, not soft lifestyle chatter (that’s closer to Threads).
-8. EasySociable only when earned; frame as **visual production layer**, never as full content OS.
-
-## Anti-slop (X)
-
-Do **not** default to:
-
-- “In a world where…” / “Here’s the thing:” / “Let’s dive in”
-- “It’s not X, it’s Y” as empty cadence with no substance
-- Engagement bait with no point (“Who’s still awake?” / “Like if you agree”)
-- Wall of hashtags
-- Corporate intern tone or fake guru certainty without a claim the user owns
-- Comment-gate lead magnets (“Comment SLIDES”) as the primary CTA
-- **RIP Canva** / “AI replaced your designer” as the main hook
-- Empty praise replies when engaging others’ posts
-
-## Quality self-check (before showing draft to user)
-
-- [ ] First line works without the rest?
-- [ ] Would a stranger understand the claim in one read?
-- [ ] Any sentence pure filler? Delete it.
-- [ ] Does this match **pillars.md** (topic allowed), not only “sounds like a tweet”?
-- [ ] Would the right ICP reply “we have this problem” / ask how — or only react with emoji?
-- [ ] No invented metrics, customers, or results?
-- [ ] If media: still makes sense as text-only?
-
-## Out of scope here
-
-- Carousel / slideshow page structure → run `pack` + EasySociable skills; see also `linkedin.md` / `ig.md` / `tiktok.md` for visual-native networks  
-- Learned strategies → `wiki/claims/`; techniques → `wiki/atoms/`  
-- Multi-platform native rules → other `platforms/*.md` files (do **not** paste X copy into Threads/LI/IG/TT unchanged)  

package/content-engine/starter/platforms/xiaohongshu.md

@@ -1,19 +0,0 @@
-# Platform: Xiaohongshu (小红书)
-
-**Scope:** How to *write* for Xiaohongshu notes.  
-**Not in this file:** Who you are, pillars, voice, audience.
-
-## Defaults
-
-- Language: follow the account; many notes mix 中文 body + English product names
-- Default unit: **single image note** in V1 (slideshow not a Content Pack route yet)
-- Pack: **no** for V1 — hand off to **easysociable-template** fill-slots
-- Canvas: often **3:4 @ 1080×1440** — see Template `PLATFORM_SPECS`
-
-## Craft
-
-- Cover must stop the thumb; one idea per note
-- Caption: concrete, saveable, not empty lifestyle filler
-- Do not invent personal metrics or “爆款” proof
-
-Missing more specific house rules → stop and ask; do not invent craft.

package/content-engine/starter/products/README.md

@@ -1,38 +0,0 @@
-# products/
-
-First-class **product facts library**. Products describe what the creator
-offers; they are not audience needs, topics, or published claims.
-
-| Path | Role |
-|------|------|
-| `_index.md` | Product registry and lifecycle |
-| `entries/P-*.md` | Product facts, boundaries, pricing, proof and claims |
-| `_template.md` | Product entry shape |
-
-## Relationship to the content engine
-
-```text
-Needs (demand evidence) + Profile (identity)
-  → Topic (editorial judgment)
-  → optional Product fit (offer context)
-  → Run
-```
-
-- A `Need` records what an audience member actually said.
-- A `Product` records what is currently offered and what it does not promise.
-- A `Topic` decides whether something is worth saying. It may cite zero, one, or
-  several products.
-- Product fit never makes a Topic `ready` by itself, and a product description
-  never becomes a Need quote.
-
-## Rules
-
-- Keep product facts current. Prices and entitlements must include an
-  `effective_from` date and a source of truth.
-- Do not invent customers, outcomes, metrics, testimonials or proof.
-- Mark a product `retired` instead of silently deleting a product used by a
-  Topic or Run.
-- Use `product_fit: none` for useful education that does not need a product
-  connection. Do not force a CTA into every Topic.
-- Product claims here describe the offer. The `wiki/claims/` catalog tracks
-  propositions tested through published content; they are different objects.

package/content-engine/starter/products/_index.md

@@ -1,25 +0,0 @@
-# Products index
-
-Newest rows on top. This is the registry; product facts live in the entry
-file.
-
-| id | name | status | audience | price | effective_from | file |
-|----|------|--------|----------|-------|----------------|------|
-| P-002 | Content Engine | active | AI-native creators and small content teams building repeatable content workflows | free local install; hosted features not included | 2026-09-16 | products/entries/P-002-content-engine.md |
-| P-001 | EasySociable | active | creators and teams producing branded multi-page social visuals | see entry | 2026-09-04 | products/entries/P-001-easysociable.md |
-
-## Status values
-
-| status | Meaning |
-|--------|---------|
-| `draft` | Being defined; do not use for product claims |
-| `active` | Current offer; may be cited by Topics and Runs |
-| `retired` | No longer offered; retained for historical references |
-
-## Agent rules
-
-- Read the product entry before making a product claim.
-- `price` is a lookup hint only; use the dated entry for exact pricing and
-  entitlements.
-- A Topic may cite `product_ids: none` even when the account has active
-  products.

package/content-engine/starter/products/_template.md

@@ -1,56 +0,0 @@
----
-id: P-YYYYMMDD-XX
-name:
-status: draft
-effective_from: YYYY-MM-DD
-source_of_truth:
----
-
-# Product name
-
-## Product promise
-
-One sentence describing the customer change. Do not promise an outcome the
-product cannot control.
-
-## What it is
-
-## Best for
-
-## Not for
-
-## Problem
-
-## Mechanism
-
-How the product addresses the problem.
-
-## Not solving
-
-Explicit exclusions and limitations.
-
-## Pricing and entitlements
-
-Include currency, billing period, limits and plan differences. Record the
-effective date above.
-
-## Proof
-
-Named evidence only. Empty is valid.
-
-## Objections
-
-## Claims
-
-### Safe to say
-
-### Say carefully
-
-### Do not say
-
-## CTA
-
-When to educate, mention, invite, or sell.
-
-## Version notes
-

package/content-engine/starter/products/entries/P-001-easysociable.md

@@ -1,150 +0,0 @@
----
-id: P-001
-name: EasySociable
-status: active
-effective_from: 2026-09-04
-source_of_truth:
-  - docs/prd.md
-  - docs/pricing-v1.md
-  - apps/easysociable/app/routes/home.tsx
----
-
-# EasySociable
-
-## Product promise
-
-Turn an agent-produced content argument into a reusable, branded,
-reviewable, multi-page social visual pack.
-
-## What it is
-
-EasySociable is the hosted visual production layer for an external Agent. It
-provides reusable Page Templates, Brands, durable Slideshow Runs, Studio
-review/editing, and browser Download of the reviewed PNG pack.
-
-The Agent supplies the content reasoning and page structure. EasySociable does
-not write the content or provide a hosted LLM.
-
-## Best for
-
-- Creators who already use Codex, Claude Code, or a comparable Agent for
-  content reasoning.
-- Creators and teams producing branded carousels across TikTok, Instagram,
-  LinkedIn, or Threads.
-- Operators who need reusable visual systems, role-specific layouts, and a
-  review step before download.
-
-## Not for
-
-- Users looking for a browser-only content writing assistant.
-- Users who want a general-purpose freeform design editor instead of a
-  constrained reusable visual system.
-- Users who want EasySociable to manage their social accounts or publish
-  automatically.
-
-## Problem
-
-An Agent can produce the argument, but the visual production context is often
-lost: each carousel starts from a blank design, brand instructions are
-repeated, and a small revision can require regeneration.
-
-When one idea must become several platform deliverables, the operator also has
-to repeat layout and export work while checking platform-specific canvases.
-
-## Mechanism
-
-- Page Templates are discoverable by layout role such as `cover`, `hook`,
-  `value`, `steps`, `proof`, and `cta`, so a content structure can be matched
-  to an appropriate visual layout.
-- A Brand and reusable templates persist visual decisions across future Runs.
-- Studio keeps the complete Run reviewable and allows supported text and image
-  slot edits before Download.
-- Platform-specific Layout Family variants and exports adapt the same
-  structured content to supported canvas presets.
-
-## Not solving
-
-- Content strategy, audience research, or the quality of the Agent's thesis.
-- Guaranteed reach, engagement, conversions, or viral performance.
-- Automatic social posting or social-account connection.
-- A hosted LLM or a replacement for the user's Agent.
-- Unlimited arbitrary canvas editing or unrestricted template composition.
-
-## Pricing and entitlements
-
-Early-access prices; list prices and free limits may change.
-
-| Plan | Monthly | Annual | Slideshow Download | Brands | Image library |
-|------|---------|--------|--------------------|--------|---------------|
-| Free | $0 | — | 3/month, 1 platform per pack | 1 | 2 GB |
-| Creator | $19 | $190/year | Unlimited, all selected V1 platforms | 5 | 50 GB |
-| Pro | $39 | $390/year | Unlimited, all selected V1 platforms | 25 | 200 GB |
-| Agency | Sales-led | Contract | Contract | >25 | >200 GB |
-
-Paid plans include the full system-template catalog, up to 20 pages per
-Slideshow Run, private drafts, three API keys, no overage and no watermark.
-Pixels leave the product through Studio Download; CLI/MCP is not a final PNG
-factory.
-
-## Proof
-
-No customer proof is recorded here. Do not invent testimonials, adoption
-metrics or performance improvements.
-
-## Objections
-
-### “Canva already does this.”
-
-Canva is the broader freeform design workspace. EasySociable is for an
-Agent-first, repeatable visual production workflow with role-aware templates,
-durable Runs and Studio review.
-
-### “Can the Agent write my post?”
-
-The Agent can do that outside EasySociable. EasySociable owns the visual
-production layer.
-
-### “Can I publish directly?”
-
-V1 produces a reviewed Download from Studio. It does not connect social
-accounts or publish posts.
-
-## Claims
-
-### Safe to say
-
-- Reuse saved Brands and Page Templates.
-- Select layouts by supported page role.
-- Review and edit supported slots in Studio before Download.
-- Create platform-specific variants for supported V1 platforms and canvases.
-
-### Say carefully
-
-- “One idea, multiple platforms” means the structured Run is adapted and
-  exported for supported platform formats; it does not mean one identical file
-  is valid everywhere.
-- “Faster” requires a user-specific baseline. Do not claim a universal time
-  saving.
-- “Branded” means the configured Brand and selected templates are applied; it
-  does not mean every creative decision is automatically correct.
-
-### Do not say
-
-- “Guaranteed higher engagement.”
-- “One-click automatic publishing.”
-- “AI writes all your content.”
-- “No review is needed.”
-- “Every platform receives the same file.”
-
-## CTA
-
-- `educate`: explain the Agent-to-visual production gap.
-- `mention`: show how a role-specific template or Brand persists.
-- `invite`: ask users to try a real content Run and review it in Studio.
-- `sell`: use only when the audience has a validated need for repeated
-  branded visual production.
-
-## Version notes
-
-- 2026-09-04: early-access pricing and V1 entitlements from
-  `docs/pricing-v1.md`.

package/content-engine/starter/products/entries/P-002-content-engine.md

@@ -1,136 +0,0 @@
----
-id: P-002
-name: Content Engine
-status: active
-effective_from: 2026-09-16
-source_of_truth:
-  - apps/cli/README.md
-  - apps/cli/package.json
-  - apps/cli/content-engine/starter/CLAUDE.md
-  - apps/cli/content-engine/starter/engine.json
----
-
-# Content Engine
-
-## Product promise
-
-Give AI-native creators and small content teams a local, repeatable workflow
-from audience signals to topics, briefs, drafts, review, feedback, and
-publishable content.
-
-## What it is
-
-Content Engine is a local-first content system installed and operated through
-the `easysociable` command-line tool. It provides a structured local vault,
-profile and audience context, needs, topics, product facts, drafts, runs,
-feedback, and a workbench for inspecting the engine.
-
-It does not require Obsidian. The engine can be initialized and served from a
-workspace directory.
-
-## Best for
-
-- AI-native creators building a repeatable publishing workflow.
-- Agency-of-one operators and small content teams managing recurring content
-  decisions and review.
-- Users who want local files and Agent-assisted workflows instead of a
-  browser-only content writing assistant.
-
-## Not for
-
-- Users looking for guaranteed reach, engagement, conversions, or virality.
-- Users who want an AI model to invent their audience, point of view, proof,
-  or customer results.
-- Users who want a hosted LLM or automatic social-account publishing.
-- Users who only want one prompt or one generated post without a repeatable
-  workflow.
-
-## Problem
-
-AI makes drafting easier, but a blank prompt does not preserve the audience,
-point of view, editorial judgment, review standards, or feedback from the last
-piece. Content Engine turns those decisions into explicit local objects that
-an Agent can use again.
-
-## Mechanism
-
-- Local profile, audience, voice, boundaries, and pillar files provide durable
-  context.
-- Needs and source material become evaluated Topics rather than immediate
-  drafts.
-- Brief, draft, editor, rubric, run, and feedback stages make review and
-  publishing decisions explicit.
-- Product and recommendation libraries keep owned-offer facts separate from
-  audience demand and third-party research.
-- The CLI can initialize, validate, build, serve, and detect local engines.
-
-## Installation
-
-The CLI and local Content Engine are free to install:
-
-```bash
-curl -fsSL https://easysociable.com/install.sh | bash
-easysociable install --skills content,template,slideshow --yes
-easysociable engine init --root /workspace --yes
-```
-
-The installer requires Node.js 20 or newer. The Content Engine workbench also
-requires `python3`. The default CLI skill set currently includes Template and
-Slideshow; the `content` skill is enabled explicitly above.
-
-## Pricing and entitlements
-
-Content Engine and its CLI installation path are free to install. This entry
-does not claim paid hosted features, managed storage, or a hosted LLM.
-
-## Proof
-
-No customer proof, adoption metrics, or performance improvements are recorded.
-
-## Boundaries
-
-- Content Engine owns local content knowledge, editorial workflow, and
-  production tracking.
-- EasySociable is a separate visual production layer for branded templates,
-  slideshow runs, Studio review, and PNG download.
-- The Agent remains responsible for reasoning, content judgment, and supplied
-  evidence.
-- The system does not guarantee that generated content is correct, useful, or
-  successful.
-
-## Claims
-
-### Safe to say
-
-- Install the CLI from the public installer or npm package.
-- Initialize a local Content Engine with `easysociable engine init`.
-- Use local files to preserve profile, audience, needs, topics, briefs, and
-  feedback.
-- Validate and serve the engine through CLI commands.
-
-### Say carefully
-
-- “One-command install” refers to installing the CLI; enabling the Content
-  skill and initializing the engine are additional CLI commands.
-- “Free” refers to the local Content Engine and CLI installation path, not to
-  hosted EasySociable plans or hosted usage.
-- “Gets better” means decisions and feedback persist for the next run; it does
-  not mean the Agent learns autonomously from every review.
-
-### Do not say
-
-- “AI writes and publishes everything automatically.”
-- “The Content Engine guarantees better performance.”
-- “Obsidian is required.”
-- “The hosted EasySociable app is the Content Engine.”
-
-## CTA
-
-- `educate`: explain why content needs durable decisions before generation.
-- `invite`: install the CLI and initialize a local engine.
-- `mention`: show how a Topic, Brief, or review gate survives into the next
-  run.
-
-## Version notes
-
-- 2026-09-16: Added as the local-first Content Engine product.

package/content-engine/starter/profiles/_index.md

@@ -1,16 +0,0 @@
-# Profiles index
-
-Reusable **content profiles**: pillars + audience + voice.  
-Accounts point here; do not copy profile bodies into account files.
-
-| id | path | voice | one_liner | accounts | product_ids | recommendation_scope |
-|----|------|-------|-----------|----------|-------------|---------------------|
-| default | profiles/default/ | `profiles/default/voice.md` | Replace this one-liner with the profile’s job | your-handle | none | none |
-
-## Voice column
-
-- Empty or `profile` → load `profiles/<id>/voice.md`
-- Explicit path → load that file instead
-
-`profiles/<id>/lanes.md` describes publishing lanes such as teaching, building,
-reviewing and comparing. A lane is not a replacement for a pillar.

package/content-engine/starter/profiles/default/README.md

@@ -1,17 +0,0 @@
-# Profile: default
-
-Replace this starter profile before the first serious draft.
-
-| File | Role |
-|------|------|
-| `pillars.md` | Topics this profile may cover |
-| `audience.md` | Readers + per-platform emphasis |
-| `voice.md` | Identity + Experience + Values + Persona |
-| `stories.md` | Story inventory (cite or none) |
-| `boundaries.md` | Creator must-avoid (Not covering / Never claim) |
-| `expression.md` | Expression likes / dislikes |
-| `lanes.md` | Publishing lanes |
-| `keywords.md` | Three-track: listen→Hits, search=SEO, ask=GEO |
-| `handles.md` | ≤8 ally/foil/competitor handles |
-
-Accounts: see `accounts/_index.md`.

package/content-engine/starter/profiles/default/audience.md

@@ -1,38 +0,0 @@
-# Audience — profile `default`
-
-**Role:** Who this profile writes for.  
-**Not:** Platform craft (`platforms/*.md`).
-
-## Cross-platform core
-
-### Primary readers
-
-1. (fill)
-
-### Not for
-
-- (fill)
-
-### Jobs to be done
-
-1. (fill)
-
-## Per-platform emphasis
-
-Fill the section for **this run’s platform** before drafting. Sibling platforms get their own run.
-
-### x
-
-- (fill)
-
-### linkedin
-
-- (fill)
-
-### ig
-
-- (fill)
-
-### tiktok
-
-- (fill)

package/content-engine/starter/profiles/default/boundaries.md

@@ -1,14 +0,0 @@
-# Boundaries — profile `default`
-
-**Role:** Topics, audiences, and claims this creator will not write.  
-**Not:** Audience “Not for” (`./audience.md`) — that excludes readers.
-
-Missing this file is a **hard-gate fail**. Write this starter, then interview. Never invent boundaries.
-
-## Not covering
-
-- (fill)
-
-## Never claim
-
-- (fill)

package/content-engine/starter/profiles/default/expression.md

@@ -1,18 +0,0 @@
-# Expression — profile `default`
-
-**Role:** Concrete likes and dislikes (phrases, structures, clichés).  
-**Not:** Hype bans (`./voice.md` Do not say).
-
-Missing this file = `profile: partial`, not a hard-gate fail.
-
-## Likes
-
-1. (fill)
-2. (fill)
-3. (fill)
-
-## Dislikes
-
-1. (fill)
-2. (fill)
-3. (fill)

package/content-engine/starter/profiles/default/handles.md

@@ -1,8 +0,0 @@
-# Handles — profile `default`
-
-**Role:** Small ally / foil / competitor list (≤8). Not a topic radar. Demand language → `./keywords.md`.
-
-| # | platform | handle | niche_tag | why_on_list | weight | status |
-|---|----------|--------|-----------|-------------|--------|--------|
-
-Zero starter rows. Add only with a concrete ally/foil/competitor reason.

package/content-engine/starter/profiles/default/keywords.md

@@ -1,31 +0,0 @@
-# Keywords — profile `default`
-
-**Role:** Three-track recipes — **listen** (social), **search** (SEO), **ask** (GEO). Not topics.
-
-| track | Means | Default use |
-|-------|--------|-------------|
-| `listen` | Social search strings | 「扫关键词」→ Hits |
-| `search` | Google/SEO phrases | Content map; volume optional; not default social scan |
-| `ask` | 15–25 word AI-engine questions | GEO coverage; not social scan |
-
-**Scan rule:** 「扫关键词」→ `track=listen` + `active` only → Hits. Never scan → Topic.
-
-| id | track | query | platform | intent | layer | pillar | why | weight | status | seed_from | pair_id | volume | kd | serp_intent | volume_source | volume_at | ask_engines | last_scanned |
-|----|-------|-------|----------|--------|-------|--------|-----|--------|--------|-----------|---------|--------|----|-------------|---------------|-----------|-------------|--------------|
-| K-01 | listen | (fill audience pain phrase) | x | pain | L1 | P1 | (why) | 1.0 | paused | manual |  |  |  |  |  |  |  |  |
-
-Replace fill rows after interview / first needs. Prefer 8–12 active **listen** seeds before routine scans.
-
-## Column notes
-
-| Column | Meaning |
-|--------|---------|
-| `track` | `listen` \| `search` \| `ask` |
-| `seed_from` | `need:N-…` / `hit:H-…` / `audience` / `pillar:P…` / `manual` |
-| `volume` / `kd` | search annotations; empty OK |
-
-## Agent rules
-
-- Default scan: listen + active only; max 5
-- Propose new rows in chat; write after confirm
-- Do not invent Need quotes from keywords

package/content-engine/starter/profiles/default/lanes.md

@@ -1,12 +0,0 @@
-# Content lanes
-
-Lanes describe how this profile publishes, not what the profile is about.
-Pillars remain the durable subjects.
-
-| id | name | purpose | status |
-|----|------|---------|--------|
-| teach | Teaching | Explain systems, mechanisms and workflows | active |
-| build | Building in public | Share implementation decisions and lessons | active |
-| review | Tool review | Review third-party AI products with evidence | active |
-| compare | Tool comparison | Compare options by a stated user job | active |
-| offer | Product education | Explain owned product mechanisms and limits | active |