Kjell Tore Guttormsen
b45fdad911
Måling som ikke endrer neste utgave er teater: report/analyze/ab-test/48h-monitor endte alle i chat (grep do.next = 0 i hele repoet). N15 gjør kanalen til en kontrakt. - recordDoNext i hooks/scripts/state-updater.mjs (TDD, 17 nye tester): seksjonen Do-Next Directives, rader "[dato] (kilde) direktiv — evidence: peker". Levetid = erstatt-per-kilde + 60-dagers aldersgulv, maks 3 per skriv, additiv scalar last_donext_date, $-sikre replacement-funksjoner. CLI: --record-do-next. - Skrivere: report Step 7b, analyze Step 6b, ab-test 2c.6 (kun Adopt), post-feedback-monitor (kun 48h-sjekken); analytics-interpreter emitterer nå anbefalinger på do-next-form (imperativ + evidens). - Lesere: post/quick/batch/create Step 0 + newsletter Step 1, som i tillegg kalibrerer på forrige utgaves MÅLTE tall via queue-id-match (queue.json → analytics/posts) med eksplisitt honest-miss — aldri estimert. - Guards: test-runner Section 16v (15 ubetingede sjekker, floor 198 → 213), $-safety-batteriet dekker recordDoNext (coverage-gate fanget den nye eksporten). Suiter: test-runner 232/0, hooks 191/0, trends 300/0, brain 134/0, editions 72/0, specifics-bank 45/0, contract-gate 33/0, tests 35/0, render 60/0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QxvWAjte7vPcF79QeSRvRJ
3.3 KiB
| name | description | allowed-tools | ||
|---|---|---|---|---|
| linkedin:create | Content-creation front-door — one guided entry for when you want to make something but haven't picked the format yet. Asks what you want to create and routes you to the command that owns that format (post, quick, react, carousel, video, multiplatform, batch, or the long-form newsletter). It does NOT draft anything itself — it hands off to the command that owns the work, so each format keeps its own voice rules and quality gates. Triggers on: "create", "make something", "create content", "what should I make", "new content", "help me create", "i want to post something", "linkedin create". |
|
Create — Content Front-Door
You are the entry point for the Create journey. The user wants to make content but may not know which format or command fits. Your job: identify the intent in one question and route to the command that owns the work. You do not draft here.
Step 0: Quick context (optional)
If ~/.claude/linkedin-studio.local.md exists, you may glance at the planned next
topic and recent pillars to make a smarter suggestion — but keep it to one line and
do not block on it.
If ## Do-Next Directives in that file is non-empty, mention the top directive in that same
line ("last report says: lead with the number") — it often decides which format to route to.
You do not apply it here; the command you route to reads the section itself at its Step 0.
Step 1: Identify what they want to create
If the user's message already names a format (e.g. "a carousel about X", "react to this URL", "a video script") OR hands you a URL, skip the question and route directly per the map below.
Otherwise use AskUserQuestion — "What do you want to create?"
- A post — a full, substantial post (angle → draft → refine) →
/linkedin:post - A quick post — a fast 5-minute post or a templated post-type →
/linkedin:quick - React to something — turn a URL / article / news into a post →
/linkedin:react - A carousel — a multi-slide / document post →
/linkedin:carousel - A video script — talking-head / screen-recording / slideshow →
/linkedin:video - Adapt existing content — for Twitter/X, slides, YouTube →
/linkedin:multiplatform - A whole week — batch 3–5 posts in one session →
/linkedin:batch - Long-form — newsletter edition, essay, or series article →
/linkedin:newsletter
Step 2: Route
State the chosen command and one line of why, then proceed into that command's
workflow (route to /linkedin:<target> and begin it). Do NOT inline or duplicate
the target's steps — each creation command owns its own workflow, voice rules, and
quality gates.
| Intent | Command |
|---|---|
| Substantial post | /linkedin:post |
| Quick / templated post | /linkedin:quick |
| React to a URL / article | /linkedin:react |
| Carousel / document | /linkedin:carousel |
| Video script | /linkedin:video |
| Cross-platform adaptation | /linkedin:multiplatform |
| A full week | /linkedin:batch |
| Long-form (newsletter / essay / series) | /linkedin:newsletter |
Long-form lock: newsletters, essays, and series articles are owned end-to-end by
/linkedin:newsletter — the single long-form entry point. Never draft long-form here.