flash-fiction
Diagnose and fix problems in flash fiction and micro fiction. Use when flash fiction feels weak, when writing stories under 1500 words, when working with micro fiction, sudden fiction, or compressed narrative forms.
What this skill does
# Flash Fiction Diagnostic ## Purpose Diagnose and fix problems in flash fiction and micro fiction (typically under 1500 words). Flash fiction demands exceptional craft efficiency—every word must serve multiple purposes. This skill identifies which dimension needs attention when a piece isn't working. ## Quick Reference | State | Signal | Core Issue | |-------|--------|------------| | FF1 | Opening doesn't hook | Structure/Pacing problem | | FF2 | Characters feel thin | Character compression failure | | FF3 | Beginning/ending disconnect | Frame weakness | | FF4 | Everything on surface | Subtext missing | | FF5 | Prose feels flat | Imagery/figurative language weak | | FF6 | Setting generic | Sensory detail lacking | | FF7 | Theme absent or preachy | Thematic development off | | FF8 | Words don't sing | Language precision/rhythm issues | | FF9 | Something feels "off" | Logical consistency breach | ## Diagnostic States ### FF1: Structure & Pacing Failure **Symptoms:** - Opening doesn't grab - Middle sags or rushes - Ending feels abrupt or dragged - Word count not distributed well - Arc feels incomplete **Diagnostic Questions:** 1. Does the first sentence create immediate engagement? 2. Is there a clear turning point? 3. Does each paragraph advance multiple purposes (plot + character + theme)? 4. Is the scope appropriate for the word count? 5. Is information released at optimal moments? **Interventions:** - Map the arc: beginning → rising action → climax → resolution - Calculate word distribution across sections - Strengthen opening hook (in medias res, mystery, declaration) - Ensure ending provides closure while leaving resonance - Cut any paragraph that only does one thing **Transformation Pattern:** ``` WEAK: "Sarah had been working at the firm for three years when she found the file." STRONG: "The file had no label—just a smudge of what looked like dried blood along its edge." ``` --- ### FF2: Character Compression Failure **Symptoms:** - Characters feel generic or interchangeable - Too much backstory exposition - Character change feels unearned - Relationships explained rather than shown - No sense of life beyond the page **Diagnostic Questions:** 1. Is each character introduced through revealing action? 2. Can history be inferred without explicit backstory? 3. Do defining objects/mannerisms reveal essence? 4. Is the character arc shown through parallel actions? 5. Do relationships emerge through interaction, not explanation? **Interventions:** - Replace generic description with character-specific detail - Convert backstory exposition to implications - Ensure first action reveals personality - Show change through decision pattern shifts - Establish relationships through what's unspoken **Transformation Pattern:** ``` WEAK: "James had PTSD from the war. He moved to escape memories." STRONG: "James flinched at the turkey platter's clatter, hand reaching for the phantom sidearm. He'd chosen this town for its population sign: 827 souls—small enough to hear rumors of strangers before meeting them." ``` --- ### FF3: Beginning/Ending Frame Weakness **Symptoms:** - Opening and closing feel disconnected - No sense of journey despite brevity - Ending doesn't fulfill opening's promise - First/last images don't resonate - Structure feels arbitrary **Diagnostic Questions:** 1. What does the opening promise the reader? 2. Does the ending fulfill or meaningfully subvert that promise? 3. Is there a first/last image relationship (echo, transformation, contrast)? 4. Does the ending feel both surprising and inevitable? 5. What emotion persists after reading? **Interventions:** - Identify the implicit contract the opening creates - Ensure closing image relates to opening image - Consider circular structure (return with transformation) - Strengthen final sentence for resonance - Check that emotional journey is complete **Transformation Pattern:** ``` WEAK ENDING: "So they decided not to sell. They were happy. The end." STRONG ENDING: "Daniel returned the FOR SALE sign to the garage, laid it beside the smaller one from his childhood treehouse. Some prices, they'd decided, were too steep to calculate." ``` --- ### FF4: Subtext Missing **Symptoms:** - Everything stated explicitly - No layers beneath surface - Readers don't participate in meaning-making - Backstory dumped, not implied - No iceberg effect **Diagnostic Questions:** 1. What is stated that could be implied? 2. What is strategically left unsaid? 3. Are there meaningful gaps for readers to fill? 4. Does the visible portion suggest invisible depth? 5. Is ambiguity purposeful or accidental? **Interventions:** - Convert explicit statements to implications - Create strategic gaps (narrative ellipsis) - Withhold information for revelation impact - Apply iceberg theory: show tip, imply mass below - Ensure backstory emerges through objects/actions, not explanation **Transformation Pattern:** ``` EXPLICIT: "John never recovered from his divorce. He felt bitter about Maria leaving him." IMPLIED: "John twisted his wedding ring finger, a reflex unchanged by three years and the absence of metal. The man at the next table laughed, and John recognized the laugh before the face." ``` --- ### FF5: Imagery & Figurative Language Weak **Symptoms:** - Prose feels flat or utilitarian - Metaphors cliched or absent - No pattern to imagery - Symbols heavy-handed or missing - Descriptions don't resonate **Diagnostic Questions:** 1. Are comparisons fresh and precise? 2. Do metaphors/similes serve multiple purposes (character + theme + emotion)? 3. Is there an imagery pattern that develops? 4. Are symbolic objects naturally integrated? 5. Is there balance between concrete and abstract? **Interventions:** - Replace clichéd comparisons with original ones - Ensure figurative language reveals character perspective - Build related image patterns that develop - Select symbolic objects that can transform meaning - Ground abstract concepts in concrete imagery **Transformation Pattern:** ``` FLAT: "The factory was abandoned and looked sad." RICH: "Machinery hulked under dust shrouds, metal teeth gleaming in fractured light between boarded windows. No one suggested splitting up." ``` --- ### FF6: Setting & Sensory Detail Lacking **Symptoms:** - Location generic or absent - Only visual sense engaged - Setting doesn't serve character/theme - Atmosphere missing - Environment feels like backdrop, not participant **Diagnostic Questions:** 1. How quickly is the reader oriented in specific time/place? 2. Are multiple senses engaged? 3. Does setting reveal character without stating it? 4. Does environment reinforce theme? 5. Is atmospheric mood established through concrete detail? **Interventions:** - Replace generic settings with specific, revealing locations - Incorporate non-visual senses (sound, smell, touch, taste) - Make setting details reveal character relationship to place - Align physical environment with thematic concerns - Embed mood in concrete details, not stated atmosphere **Transformation Pattern:** ``` GENERIC: "The coffee shop was busy. People sat drinking coffee." SPECIFIC: "The Fallout Shelter Café's concrete walls trapped steam from twenty underemployed grad students' laptops, their whispered theories competing with grinding beans and Ella Fitzgerald's crackled vinyl." ``` --- ### FF7: Thematic Development Off **Symptoms:** - Theme absent or unclear - Theme stated, not embodied - Didactic/preachy tone - Single perspective dominates - Ending oversimplifies **Diagnostic Questions:** 1. Is the theme identifiable without being heavy-handed? 2. Does theme emerge from character and situation (not imposed)? 3. Are multiple perspectives on the theme represented? 4. Is thematic content conveyed through concrete details? 5. Does the conclusion deepen rather than simplify? **Interventions:** - Embody theme in action and object, not statement - Show theme through specific circumstances, then let reader
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.