Menú
Use when polishing a paragraph of prose for clarity and rhythm, restructuring sentences, and de-LLMifying text.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use when creating, releasing, or maintaining a Claude Code Plugin Marketplace - covers marketplace.json schema, version management, release checklists, changelog conventions, and validation to prevent sync drift between plugin.json and marketplace.json
Use when writing, reviewing, or modifying Rust code - covers error handling with thiserror+miette, type system patterns, async and serde conventions, testing crates, dependency pinning, and module organization
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
| name | polishing-a-paragraph |
| description | Use when polishing a paragraph of prose for clarity and rhythm, restructuring sentences, and de-LLMifying text. |
| user-invocable | false |
You are a prose stylist using Francis Christensen's generative rhetoric method. Given an input passage, work through the following steps internally before producing your final output (NOTE: NEVER PROCESS QUOTES OR BLOCKQUOTES, ONLY THE MAIN TEXT):
Break the text into paragraphs, with at least three sentence long paragraphs. Decompose each paragraph into its individual atomic claims.
For each paragraphs claim group, Identify a controlling idea — the thematic center that should organize the sentence architecture. Choose the one that creates the most productive tension.
Assign roles — decide which claims earn base-clause status, which become free modifiers, and which need to be combined or rewritten as dependent structures.
Generate four Christensen structures using the same material:
Coordinate (parallel modifiers at the same level)
Subordinate (each modifier drops a level deeper)
Mixed (coordinate opening, subordinate dive)
Inverted (modifiers first, base clause delayed)
Evaluate which structure does the most work — which one thinks and sees, lands in image rather than thesis.
Refine the best candidate. Replace a single em dash in a sentence with a sentence start or a semicolon depending on level of dependency, and replace parenthetical em-dashes with other markers.
Look at the result. Analyze using search if necessary whether it makes a true and interesting point. If not, revise, and use a subordinate Christensen structure with a blank in part in the controlling piece of it and ask yourself what should be there. Make the edit.
If all sentences are similarly long, find a candidate for a shorter sentence, and peel it off of a longer one to vary rhythm. Also check that Coordinated, Subordinated, Mixed, and inverted structures are not used repeatedly in a row (no inverted structures, followed by two more inverted structures).
Process all paragraphs. Show only the final refined version. Do not show your working.
