r-bart

Short-form numbered list post for X / LinkedIn / Threads. "X things I learned doing Y", "X mistakes that cost me Z", "X principles for Z". Use when the user has a small set (3–10) of crisp, parallel points worth shipping as a standalone short-form piece — or when distilling a how-to / launch-retro long-form into a list.

Actionable guide (~1500-3500 words). Teaches the reader to do something specific you've actually done end-to-end. Use when you've completed a process, project, or workflow worth teaching — and you can ship a worked example, not just theory.

Introduces the scribetronic project layout, CLI, and skills to AI agents working ON this codebase.

Read-and-revise pass for any drafted post. Applies writing-style.md checklist, tightens prose, kills filler. Run after drafting and before ai-slop-check.

Post-launch breakdown (~800-1500 words). What you shipped, the numbers (good or bad), what worked, what didn't, what you'd change next time. Use after every product/launch/release where you have real numbers to share — including (especially) when the numbers are embarrassing.

Monthly devlog — longer, more reflective recap. ~1200-2000 words. Stitches together the month's work, names the pattern, draws a non-obvious lesson. Goes deeper than a weekly recap.

Derives an X thread (and optionally LinkedIn post + Threads post) from a long-form piece. Repurposing engine — chops one published long-form into 2-4 short-form derivatives so the writing system stays sustainable. Use after a long-form is drafted (and ideally edited) when you want to extract its substance for social channels.

Voice deltas for short-form (X, LinkedIn, Threads). Inherits writing-style and overrides specific rules where short-form requires it. Always loaded by short-form skills.

Manages the writing cadence using per-ISO-week directories under scribetronic/calendar/. Combines recurring rules + per-week plan.md + history. Subcommands: show, plan-week, add, skip, done, rules. Used by /write router and /write-publish.

Detection pass for AI-generated patterns and clichés. Final check before publishing. Returns a list of detected issues with severity and fix suggestions.

Contrarian opinion piece (~800-1500 words). Stakes a position against conventional wisdom in your niche. Use when you have a real fight to pick — a widely-held belief in your space that you genuinely disagree with and can defend with evidence.

Actionable guide (~1500-3500 words). Teaches the reader to do something specific you've actually done end-to-end. Use when you've completed a process, project, or workflow worth teaching — and you can ship a worked example, not just theory.

Vision/strategy piece (~1500-3000 words). Rare format — once or twice a year. Names what you're building, why it matters, and how you'll get there. Use to plant a flag, reset direction, or invite people into a longer-term mission.

Weekly newsletter — the parent piece of the week. ~600-1200 words. Drafted Sunday. Spawns 5-7 derivative short-form pieces for X / LinkedIn / Threads via /write Phase 5. The recurring Sunday default.

Parallel review of a draft along multiple focuses (voice, structure, slop, hook, closer, optional factual). Spawns N subagents concurrently — each with a single focus and the user's writing-style — then aggregates findings into one severity-grouped report. Use full mode mid-draft or as a pre-publish gate; use delta mode (--since-last / --since <ref>) to review only what changed since the last snap

LinkedIn carousel — multi-slide PDF post (8–10 slides typical). Derives from a long-form piece OR a strong listicle / how-to topic. Use when repurposing a published long-form into LinkedIn's highest-engagement format, or when a user has a step-by-step / numbered insight that benefits from one-idea-per-slide pacing.

Short-form post (X single / LinkedIn / Threads) stating a single observation. No list, no contrast — just one thing noticed clearly and named. Use when the user has a one-line insight, pattern, or quiet contrarian take that doesn't need scaffolding to land.

Short-form (X / LinkedIn) comparison of how something is done today vs how it will be done in 1–5 years. Strong for tech / AI / tooling takes. Use when the user wants to frame a directional bet, a tooling shift, or an obsolescence call — anything where the punchline is "this is the present; here's the future".

Destila una guía de estilo de escritura desde 3-5 muestras de referencia y 1-2 textos propios. Genera `scribetronic/style/writing-style.md` con las 8 secciones (voice, structure, sentence-level, signature moves, anti-patterns, ejemplos +, ejemplos -, revision checklist). Usar cuando el usuario quiera crear o refrescar la guía de estilo de su blog/newsletter.

Propone deltas concretos a `scribetronic/style/writing-style.md` (la guía de voz personalizada del usuario) a partir del historial real de edición del usuario (draft vs publicado). No reescribe automáticamente — genera un documento de propuestas con evidencia textual obligatoria. Invocar tras 3+ piezas publicadas o cuando el usuario sienta drift de voz.

Short-form motivational post within your niche (X / LinkedIn / Threads). WARNING — easiest format to slide into AI slop / coach-speak. Use when you have a personal-stakes statement or hard truth tied to a specific moment in your work — never as generic inspiration. Hard quota: 1-2 per month max.

Short-form comparison post (X / LinkedIn / Threads). Two things contrasted to reveal a non-obvious preference. Use when the user wants to publish an "X vs Y" take — tools, approaches, mindsets, frameworks — and stake a side. Pairs well after a hot-take or how-to long-form piece.

The shared style guide every long-form and short-form post inherits. Reference for tone, structure, sentence rhythm, signature moves, and anti-patterns. Always loaded by drafting and editing skills. This is the only skill that should be personalized — every other skill stays format-only.

Publishes a `status: ready` draft from the weekly calendar to its configured target (Astro blog collection) and archives social derivatives. Reads scribetronic/publish-config.yaml. Updates calendar history and per-week plan. Optionally archives completed weeks. Does NOT push to social platforms (out of scope v1).

Master writing skill. Orchestrates the full pipeline (seed → draft → edit → slop-check → optional repurpose) for any post type — long-form (long-form-weekly-newsletter, long-form-monthly-devlog, long-form-hot-take, long-form-how-to, long-form-launch-retro, long-form-manifesto) or short-form (short-form-x-vs-y, short-form-listicle, short-form-observation, short-form-motivational, short-form-present

Detection pass for AI-generated patterns and clichés. Final check before publishing. Returns a list of detected issues with severity and fix suggestions.

Short-form (X / LinkedIn) comparison of how something is done today vs how it will be done in 1–5 years. Strong for tech / AI / tooling takes. Use when the user wants to frame a directional bet, a tooling shift, or an obsolescence call — anything where the punchline is "this is the present; here's the future".

Propone deltas concretos a `scribetronic/style/writing-style.md` (la guía de voz personalizada del usuario) a partir del historial real de edición del usuario (draft vs publicado). No reescribe automáticamente — genera un documento de propuestas con evidencia textual obligatoria. Invocar tras 3+ piezas publicadas o cuando el usuario sienta drift de voz.

The shared style guide every long-form and short-form post inherits. Reference for tone, structure, sentence rhythm, signature moves, and anti-patterns. Always loaded by drafting and editing skills. This is the only skill that should be personalized — every other skill stays format-only.

Manages the writing cadence using per-ISO-week directories under scribetronic/calendar/. Combines recurring rules + per-week plan.md + history. Subcommands: show, plan-week, add, skip, done, rules. Used by /write router and /write-publish.

Read-and-revise pass for any drafted post. Applies writing-style.md checklist, tightens prose, kills filler. Run after drafting and before ai-slop-check.

Contrarian opinion piece (~800-1500 words). Stakes a position against conventional wisdom in your niche. Use when you have a real fight to pick — a widely-held belief in your space that you genuinely disagree with and can defend with evidence.

Monthly devlog — longer, more reflective recap. ~1200-2000 words. Stitches together the month's work, names the pattern, draws a non-obvious lesson. Goes deeper than a weekly recap.

Short-form motivational post within your niche (X / LinkedIn / Threads). WARNING — easiest format to slide into AI slop / coach-speak. Use when you have a personal-stakes statement or hard truth tied to a specific moment in your work — never as generic inspiration. Hard quota: 1-2 per month max.

Voice deltas for short-form (X, LinkedIn, Threads). Inherits writing-style and overrides specific rules where short-form requires it. Always loaded by short-form skills.

Post-launch breakdown (~800-1500 words). What you shipped, the numbers (good or bad), what worked, what didn't, what you'd change next time. Use after every product/launch/release where you have real numbers to share — including (especially) when the numbers are embarrassing.

Vision/strategy piece (~1500-3000 words). Rare format — once or twice a year. Names what you're building, why it matters, and how you'll get there. Use to plant a flag, reset direction, or invite people into a longer-term mission.

Publishes a `status: ready` draft from the weekly calendar to its configured target (Astro blog collection) and archives social derivatives. Reads scribetronic/publish-config.yaml. Updates calendar history and per-week plan. Optionally archives completed weeks. Does NOT push to social platforms (out of scope v1).

Weekly newsletter — the parent piece of the week. ~600-1200 words. Drafted Sunday. Spawns 5-7 derivative short-form pieces for X / LinkedIn / Threads via /write Phase 5. The recurring Sunday default.

Parallel review of a draft along multiple focuses (voice, structure, slop, hook, closer, optional factual). Spawns N subagents concurrently — each with a single focus and the user's writing-style — then aggregates findings into one severity-grouped report. Use full mode mid-draft or as a pre-publish gate; use delta mode (--since-last / --since <ref>) to review only what changed since the last snap

Short-form post (X single / LinkedIn / Threads) stating a single observation. No list, no contrast — just one thing noticed clearly and named. Use when the user has a one-line insight, pattern, or quiet contrarian take that doesn't need scaffolding to land.

Derives an X thread (and optionally LinkedIn post + Threads post) from a long-form piece. Repurposing engine — chops one published long-form into 2-4 short-form derivatives so the writing system stays sustainable. Use after a long-form is drafted (and ideally edited) when you want to extract its substance for social channels.

LinkedIn carousel — multi-slide PDF post (8–10 slides typical). Derives from a long-form piece OR a strong listicle / how-to topic. Use when repurposing a published long-form into LinkedIn's highest-engagement format, or when a user has a step-by-step / numbered insight that benefits from one-idea-per-slide pacing.

Short-form numbered list post for X / LinkedIn / Threads. "X things I learned doing Y", "X mistakes that cost me Z", "X principles for Z". Use when the user has a small set (3–10) of crisp, parallel points worth shipping as a standalone short-form piece — or when distilling a how-to / launch-retro long-form into a list.

Master writing skill. Orchestrates the full pipeline (seed → draft → edit → slop-check → optional repurpose) for any post type — long-form (long-form-weekly-newsletter, long-form-monthly-devlog, long-form-hot-take, long-form-how-to, long-form-launch-retro, long-form-manifesto) or short-form (short-form-x-vs-y, short-form-listicle, short-form-observation, short-form-motivational, short-form-present

Short-form comparison post (X / LinkedIn / Threads). Two things contrasted to reveal a non-obvious preference. Use when the user wants to publish an "X vs Y" take — tools, approaches, mindsets, frameworks — and stake a side. Pairs well after a hot-take or how-to long-form piece.

Destila una guía de estilo de escritura desde 3-5 muestras de referencia y 1-2 textos propios. Genera `scribetronic/style/writing-style.md` con las 8 secciones (voice, structure, sentence-level, signature moves, anti-patterns, ejemplos +, ejemplos -, revision checklist). Usar cuando el usuario quiera crear o refrescar la guía de estilo de su blog/newsletter.