@easysociable/cli 0.1.7 → 0.1.9

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

@@ -1,9 +0,0 @@
-# accounts/
-
-| File | Role |
-|------|------|
-| `_index.md` | **Source of truth** for handle → profile, platforms, voice, overrides path |
-| `overrides/<handle>.md` | **Optional** — only when account-only deltas exist; path listed in `_index.overrides` |
-
-Do **not** keep a full `accounts/<handle>.md` for every account.  
-Pillars/audience bodies stay under `profiles/<id>/`.

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

@@ -1,31 +0,0 @@
-# Accounts index
-
-Each handle points at a **profile** + platforms.  
-Full pillars/audience/voice live under `profiles/<id>/` (unless voice overridden).
-
-Replace the starter handle before the first run.
-
-| handle | profile_id | voice | platforms | default_platform | overrides | status |
-|--------|------------|-------|-----------|------------------|-----------|--------|
-| your-handle | default | profile | x | x | | active |
-
-## Columns
-
-| Column | Meaning |
-|--------|---------|
-| `handle` | Social account id |
-| `profile_id` | Row in `profiles/_index.md` |
-| `voice` | `profile` → `profiles/<profile_id>/voice.md`; or explicit path to another voice file |
-| `platforms` | Platforms this account posts on |
-| `default_platform` | Watchlist / catalog filter when unset — **not** used to silent-default 开一单 |
-| `overrides` | Empty = none; else path e.g. `accounts/overrides/<handle>.md` |
-| `status` | active / planned / retired |
-
-## Resolve path (Agent)
-
-1. Read this table for the handle (default: first **active** row)
-2. Load `profiles/<profile_id>/pillars.md` + `audience.md`
-3. Voice: if `profile` or empty → `profiles/<profile_id>/voice.md`; else load the path in the cell
-4. If `overrides` non-empty, read that file last
-5. Load `platforms/<platform>.md` for craft (**required** when drafting that platform; map in `platforms/README.md`)
-6. Filter swipe/atoms/claims by platform + profile (`*` = all)

package/content-engine/starter/accounts/overrides/README.md

@@ -1,3 +0,0 @@
-# Account overrides
-
-Optional per-handle deltas. Path must be listed in `accounts/_index.md` `overrides` column.

package/content-engine/starter/engine.json

@@ -1,23 +0,0 @@
-{
-  "schemaVersion": "content-engine.v1",
-  "locale": "en",
-  "root": "Content Engine",
-  "paths": {
-    "runs": "runs",
-    "exports": "exports",
-    "topics": "topics",
-    "needs": "needs",
-    "hits": "hits",
-    "products": "products",
-    "recommendations": "recommendations",
-    "swipe": "swipe",
-    "profiles": "profiles",
-    "inbox": "inbox",
-    "accounts": "accounts",
-    "raw": "raw",
-    "published": "published",
-    "wiki": "wiki",
-    "platforms": "platforms",
-    "workbench": "workbench"
-  }
-}

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

@@ -1,28 +0,0 @@
-# exports/
-
-**Rendered image packs only** (slideshow skill / Gateway). Not drafts.
-
-## Layout
-
-One run = one platform, so the slug already scopes the platform. Optional `<platform>/` subfolder still OK.
-
-```text
-exports/
-  <run-folder-slug>/          # same name as runs/YYYY-MM-DD-slug[-platform]
-    01.png
-    02.png
-    …
-    manifest.json             # optional: job_id, deck_hint, page_count
-```
-
-Example: `exports/2026-08-26-angle-linkedin/01.png`
-
-## Pointers
-
-- `runs/.../pack.md` → `export_path: exports/<slug>/`  
-- `runs/_index` column `export`: `no` \| `yes`  
-- **Do not** put binaries in `published/` — only URLs after ship  
-
-## Until slideshow skill is wired
-
-Folder may stay empty. Agent must not invent images; pack render status stays `not_requested` / `blocked`.

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

@@ -1,5 +0,0 @@
-# Hits
-
-Research triage board. Scan → stage here → route to Needs or Library (swipe/atom). Not a Topic queue.
-
-See engine `CLAUDE.md` **§ Hits**.

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

@@ -1,30 +0,0 @@
-# Hits index (research triage)
-
-**Role:** Staging board for research hits. Route to Needs or Library — **not** a Topic queue.
-
-Newest on top. Scan may write rows here (include source-post heat). Routing out still needs explicit confirm.
-
-| id | date | profile | platform | keyword_id | source | hit_kind | signal | status | excerpt | src_likes | src_replies | src_bookmarks | src_views | engagement_at | file |
-|----|------|---------|----------|------------|--------|----------|--------|--------|---------|-----------|-------------|---------------|-----------|---------------|------|
-
-## Status
-
-| status | Meaning |
-|--------|---------|
-| `triage` | Waiting for route |
-| `routed_need` | Written to `needs/` |
-| `routed_library` | Capture + library ingest path |
-| `discarded` | Rejected |
-
-## Columns
-
-| Column | Meaning |
-|--------|---------|
-| `keyword_id` | Primary recipe `K-xx` |
-| `src_*` | Source-post heat snapshot (not our results) |
-
-## Agent rules
-
-- Exits: **need** \| **library** \| **discard**. Hits are not Topic inputs.
-- On scan: write `keyword_id` + engagement snapshot when known. Do not invent metrics.
-- Author hooks ≠ Needs. Zero starter rows — do not invent hits.

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

@@ -1,46 +0,0 @@
----
-id: H-YYYYMMDD-XX
-date: YYYY-MM-DD
-profile: default
-platform: x
-status: triage
-hit_kind: author_post | comment | thread
-signal: demand_language | structure | foil | mixed | noise
-source_keyword:
-keyword_id: K-XX
-source_handle:
-source_url:
-src_likes:
-src_replies:
-src_bookmarks:
-src_views:
-engagement_at:
----
-
-# H-YYYYMMDD-XX
-
-## Excerpt
-
-> verbatim excerpt — do not rewrite
-
-## Context
-
-Where this came from and why it was kept for triage.
-
-## Engagement snapshot
-
-- likes:
-- replies:
-- bookmarks:
-- views:
-- snapshot_at:
-
-## Suggested route
-
-need | library | discard | undecided
-
-## Route log
-
-| date | action | result_ids |
-|------|--------|------------|
-|  |  |  |

package/content-engine/starter/hits/entries/README.md

@@ -1,3 +0,0 @@
-# Hit entries
-
-One file per `H-YYYYMMDD-XX`. Create from `../_template.md`.

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

@@ -1,9 +0,0 @@
-# inbox/
-
-| Path | Role |
-|------|------|
-| `_index.md` | Capture registry (source of truth for list/status) |
-| `entries/C-YYYYMMDD-XX.md` | Working notes for one capture |
-| *(no capture.md)* | Deprecated stream file removed |
-
-Authoritative originals → `../raw/`.

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

@@ -1,24 +0,0 @@
-# Inbox index
-
-Registry of captures. **Source of truth for capture lifecycle**.
-
-Newest rows on top.
-
-| id | date | type | one_liner | platforms | profile | entry | raw | library | status |
-|----|------|------|-----------|-----------|---------|-------|-----|---------|--------|
-
-## Columns
-
-| Column | Meaning |
-|--------|---------|
-| `entry` | Working notes file under `inbox/entries/` |
-| `raw` | Authoritative source file if any; else empty |
-| `library` | `none` or e.g. `swipe:S1` / `atom:A-…` / `claim:C-…` after user-approved ingest |
-| `profile` | Which content profile this capture is for |
-| `status` | `captured` \| `ingested` \| `archived` |
-
-## Agent rules
-
-- Every capture: new row + new `entries/<id>.md`
-- raw file only when URL / structure / media / user says important → also row in `raw/_index.md`
-- Never silent-write swipe/atoms/claims; only update `library` after approval

package/content-engine/starter/inbox/entries/README.md

@@ -1,3 +0,0 @@
-# inbox/entries/
-
-One file per capture (`C-YYYYMMDD-XX.md`). Registry: `../_index.md`.

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

@@ -1,38 +0,0 @@
-# needs/
-
-First-class **user-needs library**. Not an inbox type. Inbox stays structure / link / insight.
-
-| Path | Role |
-|------|------|
-| `_index.md` | Quote registry (source of truth for list/status) |
-| `entries/N-YYYYMMDD-XX.md` | One need: verbatim quote + sightings + optional gloss |
-| `_template.md` | Entry shape |
-
-## Status machine (only these words)
-
-```text
-captured  → just written, or still captured after a synonym merge (frequency ≥ 1)
-promoted  → and only when a T- exists whose need_ids contain this N-; topic_ids lists that T-
-retired   → user discarded
-```
-
-Do **not** use `clustered`. Merge is not a status.
-
-## Do not
-
-- Invent quotes or FAQ template sentences
-- Treat a watchlist hook / viral title as a need
-- Put `N-` into a topic `capture_id` (`capture_id` is inbox `C-…` only)
-- Hosted clustering
-
-## Quote shape (not product copy, not index rows)
-
-These lines are the **shape** of a creator's audience talking. They are **not** EasySociable features and must **not** be seeded as rows:
-
-- 我不知道自己适合做什么 AI 自媒体方向
-- 我每天用 AI 写稿，还是断更
-- 我账号有流量，但为什么没人咨询
-- 我想接广告，要多少粉丝才可以
-- 我不会出镜，能不能先做图文
-
-When a quote is reused as published copy, redact names / DMs / student details.

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

@@ -1,31 +0,0 @@
-# Needs index
-
-Registry of **audience quotes**. Source of truth for need lifecycle.
-
-Newest rows on top. **Zero starter rows** — do not invent quotes.
-
-| id | date | profile | source_type | quote | speaker | frequency | status | topic_ids | file |
-|----|------|---------|-------------|-------|---------|-----------|--------|-----------|------|
-
-## Columns
-
-| Column | Meaning |
-|--------|---------|
-| `id` | `N-YYYYMMDD-XX`, increment per day (same shape as `C-` / `D-` / `T-`) |
-| `date` | First sighting date |
-| `profile` | Default current `profile_id` |
-| `source_type` | `comment` \| `dm` \| `consult` \| `faq` \| `student` \| `other` |
-| `quote` | **Verbatim.** Never put a gloss in this cell |
-| `speaker` | Optional; anonymous → `anon`. Do not invent names |
-| `frequency` | Integer, default 1. Same-meaning merge: `+1` on this row, append a sighting — do **not** create a second row |
-| `status` | `captured` \| `promoted` \| `retired` (**never** `clustered`) |
-| `topic_ids` | Cited `T-…`, comma-separated. Non-empty **iff** status=`promoted` |
-| `file` | `needs/entries/N-….md` |
-
-## Agent rules
-
-- Every need: new row + new `entries/<id>.md`
-- Merge is not a new status. After a user-approved synonym merge, keep `captured`, bump `frequency`, append sighting
-- Do not mark `promoted` without a `T-` whose `need_ids` contain this `N-`
-- Scan-for-topics input set: `status=captured` (`topic_ids` empty). Max 5 `produce`
-- Quotes may include DMs / student info. Keep local. Redact PII if a quote is used in published copy

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

@@ -1,24 +0,0 @@
----
-id: N-YYYYMMDD-XX
-date: YYYY-MM-DD
-profile: default
-source_type: comment | dm | consult | faq | student | other
-frequency: 1
-status: captured
----
-
-# N-… — five-character-or-less need label (Agent-coined, not the quote)
-
-## Quote
-> （verbatim, unedited）
-
-## Sightings
-| date | source_type | where |
-|------|-------------|-------|
-| YYYY-MM-DD | comment | url or `pasted` |
-
-## Our gloss（optional, separate from the quote）
-One line: what they are hiring us to solve.
-
-## Status
-captured

package/content-engine/starter/needs/entries/README.md

@@ -1,5 +0,0 @@
-# needs/entries/
-
-One file per need (`N-YYYYMMDD-XX.md`). Registry: `../_index.md`.
-
-Do not pre-seed FAQ rows.

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

@@ -1,19 +0,0 @@
-# Platforms (craft only)
-
-One file per network. **Required** whenever drafting that platform (especially § Open a run: brief → draft → editor → rubric → pack).
-
-Loaded as `platforms/<platform>.md` after account → profile resolve. Map:
-
-| Platform id | File |
-|-------------|------|
-| `x` | `x.md` |
-| `linkedin` | `linkedin.md` |
-| `ig` | `ig.md` |
-| `instagram` | `ig.md` (canonical; `instagram.md` is redirect stub) |
-| `tiktok` | `tiktok.md` |
-| `threads` | `threads.md` |
-| `xiaohongshu` / `xhs` | `xiaohongshu.md` |
-
-**Not here:** ICP, pillars, voice → `profiles/`. Pixels → EasySociable `PLATFORM_SPECS`.  
-**Rule:** same Topic, different platforms → **N runs**, each **re-reads** its craft file (no paste-across).  
-**Missing file:** do not invent craft; stop and tell the user.

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

@@ -1,69 +0,0 @@
-# Platform: Instagram
-
-**Scope:** How to *write* for Instagram — caption, carousel norms, job-of-format.  
-**Not in this file:** Who you are, product story, pillars, voice, audience.  
-**Pixels / canvas:** EasySociable `PLATFORM_SPECS` — feed carousel default **4:5 @ 1080×1350** (or `1:1` if user wants max compatibility).
-
-Agent: platform id in this vault is often `ig` (also accept `instagram` → this file).
-
----
-
-## Defaults
-
-- Language: English (unless user asks otherwise)
-- Default unit for easysociable-builder: **feed carousel** (save/depth job) — **not** Reels unless the user explicitly asks for Reels
-- Assume thumb stop on **cover slide**; caption supports the cover, does not replace it
-- Pack: **yes** for carousel runs
-
-## Length & shape
-
-| Form | Guidance |
-|------|----------|
-| Carousel | **7–9 slides** common; keep one aspect for all slides. One tip/step per slide. Big type; few words. |
-| Caption | 1–3 short lines: hook + what they’ll get by swiping. Optional soft CTA (“Save for your next brand kit”). |
-| Reels | Only if user asks. Different job: discovery/reach. Do not silently turn a carousel brief into a Reel script. |
-| Single image | Rare for system topics; prefer carousel when teaching steps. |
-
-## Hooks (mechanics only)
-
-Cover slide should:
-
-- Stop the scroll with a **bold, specific promise or mistake**
-- Signal “worth saving” (checklist, steps, before/after), not “watch me talk”
-
-Caption line 1 mirrors the cover; no LinkedIn-length essay above the fold.
-
-## Craft rules
-
-1. **Visual first.** If the slides don’t work with sound off and skim-reading, rewrite.
-2. Optimize carousel for **saves** and return visits — reference content, not dunks.
-3. One idea per slide; max clarity over clever wordplay.
-4. Keep brand kit / template consistency visible (this is where EasySociable proof belongs).
-5. CTA: save / share to a teammate / soft follow — not comment-gate lead magnets.
-6. Hashtags: light or none; never a block of 30.
-7. Do not paste X thread text onto slides.
-
-## Anti-slop (Instagram)
-
-Do **not** default to:
-
-- Wall-of-text slides
-- Engagement bait (“Comment SAVE”) as the whole strategy
-- Faceless “viral in 60 seconds” energy as the brand voice
-- Using Reels trends/audio as required for every post
-- Treating IG as a dump of LinkedIn PDF screenshots with tiny type
-
-## Quality self-check
-
-- [ ] Cover stops a visual scroll without reading the caption?
-- [ ] Would someone save this to reuse next week?
-- [ ] Words per slide low enough for mobile?
-- [ ] Same aspect across the deck?
-- [ ] Job clear: save/authority (carousel) vs reach (Reel) — and format matches?
-- [ ] No invented metrics; EasySociable only if earned?
-
-## Out of scope here
-
-- Reels editing / trending audio tactics  
-- Pixel export → EasySociable skills + `PLATFORM_SPECS`  
-- Other networks → sibling `platforms/*.md`  

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

@@ -1,5 +0,0 @@
-# Platform: Instagram (alias)
-
-Vault platform id is often **`ig`**. Product/catalog enum may say **`instagram`**.
-
-**→ Follow [`ig.md`](./ig.md) in full.** Do not maintain a second craft body here.

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

@@ -1,72 +0,0 @@
-# Platform: LinkedIn
-
-**Scope:** How to *write* for LinkedIn — length, rhythm, quality bars, document/carousel norms.  
-**Not in this file:** Who you are, product story, pillars, voice, audience.  
-Those live under `profiles/<id>/` (via account → profile resolve).  
-**Pixels / canvas:** EasySociable `PLATFORM_SPECS` (LinkedIn page templates; PDF document pages often `4:5` or `1:1`).
-
-Agent: before drafting any LinkedIn post, read this file for craft.
-
----
-
-## Defaults
-
-- Language: English (unless user asks otherwise)
-- Default unit: **document carousel (PDF pages) + short post text** — not a pure text hot take
-- Assume professional feed skim: **cover slide + first line of caption** do most of the work
-- Pack: **almost always yes** for easysociable-builder runs (visual production proof)
-
-## Length & shape
-
-| Form | Guidance |
-|------|----------|
-| Caption | Hook in line 1 (above the fold). 3–8 short lines total. One clear promise. Put outbound links in the **first comment**, not the post body when possible. |
-| Document carousel | **7–10 pages** sweet spot (acceptable band ~5–15). One idea per page. Headlines scannable alone. Body under ~30 words/page when present. |
-| Aspect (pack) | Prefer **4:5 (1080×1350)** mobile-first, or **1:1 (1080×1080)** for safe desktop+mobile. Same size every page. |
-| Text-only | Allowed as a light mid-week post; do not make it the default for system/framework topics. |
-
-## Hooks (mechanics only)
-
-Cover slide **and** caption line 1 should each do one of:
-
-- Name a **specific agency / operator pain** (revisions, brand feedback, blank prompt)
-- Promise a **numbered framework** or checklist the reader can steal
-- Lead with a **concrete claim or contrast** (not “My thoughts on AI”)
-
-Avoid vague covers: “Leadership lessons”, “What I learned this week”.
-
-## Craft rules
-
-1. Write like a **saveable mini-deck**, not like an X dunk.
-2. One idea per slide; if it needs a paragraph, split across two slides.
-3. Prefer frameworks, steps, before/after production loops, cost-of-revision angles.
-4. Soft CTA on the last slide (invite / question / “save for your next client kickoff”) — not “Buy now”.
-5. EasySociable only as **visual production layer** proof after the framework lands.
-6. Tone: calm, specific, peer-to-peer operator — not hype, not meme war.
-7. Hashtags: 0–3 max, optional; never a wall.
-
-## Anti-slop (LinkedIn)
-
-Do **not** default to:
-
-- Inspiration-poster fluff with no procedure
-- Hard sell on slide 1 or slide N
-- Crypto flex / “I made $X in 30 days” unless user supplies a real number for that draft
-- Pasting an X-style contrarian one-liner as the whole post
-- External link in the post body as the main content
-- Dense slides that require pinch-zoom
-
-## Quality self-check
-
-- [ ] Cover works as a standalone headline in under 3 seconds?
-- [ ] Would an agency lead save this for a teammate?
-- [ ] Each page one idea; captions not essays?
-- [ ] Soft CTA, not a pitch deck close?
-- [ ] Matches pillars; no invented metrics/customers?
-- [ ] Pack page count and aspect sensible for LI document post?
-
-## Out of scope here
-
-- Exact render pipeline → run `pack.md` + EasySociable slideshow/template skills  
-- Profile ICP emphasis → `profiles/.../audience.md`  
-- Other networks → sibling `platforms/*.md`  

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

@@ -1,69 +0,0 @@
-# Platform: Threads
-
-**Scope:** How to *write* for Meta Threads — length, tone, conversation norms.  
-**Not in this file:** Who you are, product story, pillars, voice, audience.  
-**Pixels / canvas:** Optional; if images, follow EasySociable `PLATFORM_SPECS` for **threads** (often shared with IG **4:5 @ 1080×1350**).
-
-Agent: before drafting any Threads post, read this file for craft.
-
----
-
-## Defaults
-
-- Language: English (unless user asks otherwise)
-- Default unit: **1 conversational short post** (≤500 characters available — use only what you need)
-- Assume calmer, Instagram-adjacent feed: **invitation > combat**
-- Pack: **optional**. Prefer text (+ one image) unless the user wants a mini carousel
-- Role for easysociable-builder: **secondary** surface — warm process / questions; not the main agency acquisition channel (X / LinkedIn lead)
-
-## Length & shape
-
-| Form | Guidance |
-|------|----------|
-| Single post | 1–5 short sentences. Room for one nuance line X might cut. End with a **real question** when you want replies. |
-| Reply | Add substance or a precise follow-up. Same ban on empty praise as X. |
-| Media | Images help; don’t rely on a 10-slide deck as the default Threads unit. |
-| Cross-post from X | **Rewrite.** Do not paste X dunks unchanged. |
-
-## Hooks (mechanics only)
-
-A strong open usually:
-
-- Shares a **process observation** (“We stopped letting the agent pick templates silently…”)
-- Offers a **small, stealable rule**
-- Asks an **answerable** ICP question
-
-Avoid opening with maximum contrarian heat meant for X ratio.
-
-## Craft rules
-
-1. Tone: warmer, more human, less debate-club than X.
-2. Optimize for **replies and positive conversation**, not quote-dunk chains.
-3. Good fits: behind-the-scenes, experiment notes, “what’s your bottleneck?”, light system tips.
-4. Bad fits as primary: hard category warfare, political newsjacking, long frameworks (send those to LinkedIn).
-5. EasySociable: mention lightly as visual production layer when relevant — no install sermon.
-6. One topic tag max if used; no hashtag walls.
-
-## Anti-slop (Threads)
-
-Do **not** default to:
-
-- Raw paste of an X banger
-- Corporate LinkedIn voice
-- Engagement bait with no point
-- Fake vulnerability / engagement-pod energy
-- Treating Threads as the only growth channel for AI-native agencies
-
-## Quality self-check
-
-- [ ] Would this feel natural in a calm group chat, not a town-hall fight?
-- [ ] If there’s a question, can a busy operator answer in one sentence?
-- [ ] Rewritten for Threads — not an X clone?
-- [ ] Media optional and not a tiny-type PDF dump?
-- [ ] No invented metrics?
-
-## Out of scope here
-
-- Meta ads / Instagram cross-post mechanics  
-- Full carousel systems → prefer `ig.md` / `linkedin.md` / `tiktok.md`  
-- Other networks → sibling `platforms/*.md`  

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

@@ -1,71 +0,0 @@
-# Platform: TikTok
-
-**Scope:** How to *write* for TikTok — especially **Photo Mode / slideshow** craft.  
-**Not in this file:** Who you are, product story, pillars, voice, audience.  
-**Pixels / canvas:** EasySociable `PLATFORM_SPECS` — default **9:16 @ 1080×1920** for Photo Mode; keep text out of UI chrome safe zones.
-
-Agent: before drafting any TikTok slideshow/post, read this file for craft.
-
----
-
-## Defaults
-
-- Language: English (unless user asks otherwise)
-- Default unit for easysociable-builder: **photo slideshow (carousel)** competing in For You next to video
-- Assume: if slide 1 fails, slides 2–N never exist
-- Pack: **yes**; design for **completion / swipe-through**, not desktop reading
-
-## Length & shape
-
-| Form | Guidance |
-|------|----------|
-| Slideshow | **6–10 slides** sweet spot (platform allows more; completion pressure rises). One line per slide when possible. |
-| Slide 1 | Hook only — open loop, specific pain, or numbered promise. Not a course title. |
-| Middle | One tip / mistake / step each. Max ~15 words/slide; hook slide often ≤10 words, huge type. |
-| Last | Explicit save/share CTA is OK on TikTok (more direct than LinkedIn). |
-| On-video / talking head | Only if user asks; not the default for EasySociable PNG runs. |
-
-## Hooks (mechanics only)
-
-Slide 1 usually does one of:
-
-- Specific cringe / cost (“You redesign the carousel every Wednesday”)
-- Numbered open loop (“7 production leaks agencies ignore”)
-- Sharp contrast / “stop doing X”
-
-Avoid textbook titles: “Content Systems Explained”.
-
-## Craft rules
-
-1. Write for a **video-trained thumb**: bigger type, fewer words, higher contrast than IG if needed.
-2. Each slide must **earn the next swipe**; cut any slide that only restates.
-3. Prefer listicle / mistakes / stack / steps formats.
-4. Tone: spoken, direct, slightly punchy — not LinkedIn deck voice.
-5. Agency worldview is OK if compressed into swipeable bites; deep theory → X or LinkedIn instead.
-6. EasySociable as quick proof of visual production — not a feature tour.
-7. Same aspect every slide; default 9:16 unless user overrides.
-
-## Anti-slop (TikTok)
-
-Do **not** default to:
-
-- Soft corporate captions on slide 1
-- Dense paragraphs or LI-style frameworks with 40 words/slide
-- “Follow for part 2” without delivering value in-post
-- Watermarked or letterboxed 4:5 content that looks like a wrong-platform export
-- Comment-gate playbooks as the primary CTA for this brand
-
-## Quality self-check
-
-- [ ] Slide 1 works as a For You interrupt?
-- [ ] Would a stranger swipe to slide 3 without loving you already?
-- [ ] Word count low; type large; chrome-safe?
-- [ ] Completion-friendly length (not a 20-slide essay)?
-- [ ] 9:16 (or user-agreed alt) consistent across pack?
-- [ ] No invented metrics?
-
-## Out of scope here
-
-- TikTok Shop / live / music licensing  
-- Native video editing  
-- Exact render → EasySociable slideshow skill + `PLATFORM_SPECS`