Kjell Tore Guttormsen
d783f261dd
create is the Create-journey routing front-door (v4.1): guided "what to make?"
-> routes to the command that owns the format; delegates only, never drafts.
Routing axis is clean — all 8 emitted targets (post/quick/react/carousel/video/
multiplatform/batch/newsletter) resolve to commands/Y.md. Delegates-only holds:
every "draft" mention is the no-draft promise (:7/:22, long-form lock :66) or a
target-description (:38), no leak. The one finding was grant-hygiene: Glob was
declared (:14) but never used — the only file access is a fixed-path Read of the
state file (:26), which needs no pattern-matching. Same orphan-grant pattern as
S17-S22.
1 edit, commands/create.md only:
- allowed-tools :14: drop orphan Glob; net = {Read, AskUserQuestion}.
Verify: re-grep final — Glob NONE, allowed-tools = Read + AskUserQuestion;
git diff --stat = 1 file -1; test-runner 81/0/0 exit 0; counts 29/19 unchanged
(.md-only). FIXED, 0 deferrals. Scope note: Glob-orphan may recur in sibling
front-doors (measure S25, linkedin S26) — not expanded; each catches its own.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016qgzo6rxthw7KuxHjn5vyE
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.
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.