메뉴
Reduce bullet-point and markdown formatting — produce flowing prose instead. Use for reports, technical writing, essays, user-facing documents, or any long-form text where fragmented bullets hurt readability.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Make Claude default to implementing changes rather than just suggesting them. Use when the model keeps proposing edits instead of applying them, or when you want a bias toward action in an agentic coding context.
Raise recall in code review — get Claude to report every bug it finds, including low-confidence ones. Use for code review harnesses, security audits, or any workflow where missing a real bug is worse than a few false positives.
Stop Claude from leaving behind temporary scripts, scratch files, and iteration helpers after a task. Use when you want a clean workspace — no extra files beyond the requested deliverables.
Make Claude's responses shorter and more focused. Use when the model is over-explaining, adding non-essential context, or producing verbose answers for simple lookups.
Make Claude ask before taking destructive or hard-to-reverse actions (rm, force-push, dropping tables, posting publicly). Use in autonomous agents that touch shared systems or in any context where the blast radius of a wrong action is high.
Structured, hypothesis-driven research across large corpora. Use for complex research tasks, literature reviews, competitive analysis, or anywhere Claude needs to synthesize information from many sources with tracked confidence.
| name | vojta-prose |
| description | Reduce bullet-point and markdown formatting — produce flowing prose instead. Use for reports, technical writing, essays, user-facing documents, or any long-form text where fragmented bullets hurt readability. |
Claude tends toward bullet-point formatting. For narrative writing, this fragments ideas that should flow.
<avoid_excessive_markdown_and_bullet_points>
When writing reports, documents, technical explanations, analyses, or any long-form content, write in clear, flowing prose using complete paragraphs and sentences. Use standard paragraph breaks for organization and reserve markdown primarily for `inline code`, code blocks (```...```), and simple headings (###, and ###). Avoid using **bold** and *italics*.
DO NOT use ordered lists (1. ...) or unordered lists (*) unless : a) you're presenting truly discrete items where a list format is the best option, or b) the user explicitly requests a list or ranking
Instead of listing items with bullets or numbers, incorporate them naturally into sentences. This guidance applies especially to technical writing. Using prose instead of excessive formatting will improve user satisfaction. NEVER output a series of overly short bullet points.
Your goal is readable, flowing text that guides the reader naturally through ideas rather than fragmenting information into isolated points.
</avoid_excessive_markdown_and_bullet_points>
Match your own prompt style to the desired output — if you write in prose, Claude is more likely to respond in prose. Remove markdown from your prompt to reduce markdown in the response.
Prefer "respond in smoothly flowing prose" over "do not use markdown." Positive instructions steer better than negative ones.