external/creative-writing-skills/cw-prose-writing/SKILL.md
Creative writing skill for drafting and editing narrative fiction prose. Use when writing new scenes, chapters, or dialogue, or when editing existing prose. Discovers and follows project-specific style guides, character voice conventions, and formatting preferences.
npx skillsauth add seikaikyo/dash-skills cw-prose-writingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Write narrative fiction following your project's established style and conventions.
ALWAYS check for style guidance before writing:
Look for:
CLAUDE.md - Often explains project structureWRITING.md, CONVENTIONS.md, STYLE.mdREADME.md - May contain writing instructionsCommon locations:
.cursor/rules/styles/ - Style files (.md or .skill packages).cursor/rules/ - May contain style files.ai/styles/, .ai/rules/docs/style/, style/, writing/Style guides can be:
.md).skill) created by cw-style-skill-creatorDifferent types:
Read relevant guides BEFORE writing. If writing dialogue-heavy scene, read both master and dialogue guides.
Also look for:
When NO style guides found:
Inform user:
I don't see any style guides in your project yet. I can write in
competent default prose, but you'll get better results by creating
style guides first using the cw-style-skill-creator skill.
Would you like me to:
1. Write in default style for now
2. Help you create style guides first
3. Search your project for existing style documentation
If user wants you to proceed anyway:
Search when helpful for:
While Writing:
Self-Check After:
Markdown artifact with proper formatting
The workflow:
Without style guides: Generic competent prose
With style guides: YOUR specific voice
Feel free to combine with other skills - e.g., using cw-official-docs to check character details while writing.
development
拋棄式 HTML mockup 比稿:產出 2 到 3 個設計立場不同的變體(密度 / 版式 / 強調軸,不是換色),各附取捨說明,最後給有立場的對比結論。適用:「畫個草圖」「比較 A 版 B 版」「先看方向再做」「給我看幾種做法」。要 production 元件或設計已定案時不適用。
tools
需求不明時的意圖萃取訪談:一次一題、每題附上自己的猜測、聽出「真正想要 vs 覺得應該要」,直到能預測使用者反應(約 95% 信心)才動工。適用:需求缺少對象 / 動機 / 成功標準 / 約束,或使用者點名「訪談我」「先確認一下」「我們確定嗎」。明確自足的指示、純資訊查詢、機械性操作不適用。
development
對非平凡決策啟動新鮮 context 對抗審查(找碴不背書),在修正還便宜的時候抓出錯誤方向。適用:高風險改動(production、資安敏感邏輯、不可逆操作)、不熟的程式碼、要宣稱「這樣是安全的 / 可行的」之前。機械性操作與一行修改不適用。
testing
Reference for writing and editing agent skills well — the vocabulary and principles that make a skill predictable. Consult when authoring, reviewing, or pruning a SKILL.md.