From frontend-skills
Captures user conversation as raw writing fragments in a single markdown file, preserving structure without imposing outlines or phases.
How this skill is triggered — by the user, by Claude, or both
Slash command
/frontend-skills:writing-fragmentsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Interview relentlessly. Capture raw fragments. Do not impose outline/phases.
Interview relentlessly. Capture raw fragments. Do not impose outline/phases.
If path missing, ask once. Remember it. Re-read before every write to preserve user edits.
Capture from first user prompt too.
First write: single H1 working title, then fragments. No metadata/TOC/date.
Readable by author; may not be self-contained for cold reader. Could be sharp sentence, claim, vignette, code snippet, analogy, half-thought, quote, complaint, punchline.
Format:
# Working title
Fragment one.
---
Fragment two.
Use \n---\n separators. No body headings/tags/order beyond capture order.
Append silently. Mention briefly. User can cut/rewrite/merge anytime.
npx claudepluginhub redpanda-data/ui-harness --plugin frontend-skillsMines the user for writing fragments (claims, vignettes, sharp sentences, half-thoughts) via a grilling session, appending them to a single markdown file as raw material for a future article.
Generates article beats interactively from raw markdown material, one beat at a time. Preserves user edits and supports rewrites. Useful for structured content creation.
Captures solved problems, bug fixes, and learnings from conversations into structured markdown files in docs/learnings/. Auto-invokes after 'that worked', 'it's fixed', etc., or via /learn.