القائمة
Writing guidelines for clear, economical prose. Reference this skill when creating or enhancing note content.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | writing-style |
| description | Writing guidelines for clear, economical prose. Reference this skill when creating or enhancing note content. |
| allowed-tools | null |
Based on "Economical Writing" by Deirdre N. McCloskey. Apply these principles when writing summaries, insights, and note content.
Clarity is speed directed at the point. Bad writing makes slow reading. When explaining complex topics, give your reader every help possible.
Not "Active verbs should be used" (passive, cowardly). Rather: "Use active verbs" (direct, clear). Verbs make English—pick active, accurate, lively ones.
Never start with filler like "This note will explore..." or "In this summary, we will...". Cut the throat-clearing and get to the point.
Each paragraph should be a complete discussion of one topic. Don't scatter ideas across paragraphs or cram multiple ideas into one.
Writing should hang together from phrases to entire documents. Use transitions and logical flow so the reader can follow without backtracking.
Don't swap synonyms to seem sophisticated. If you mean "book", say "book" every time—not "tome", "volume", "work", "publication". Clarity trumps elegance.
The end of a sentence is the emphatic location. Rearrange so the main point lands last. "The emphatic location is the end of the sentence" → "The end is the place of emphasis."
Avoid "this", "that", "these", "those" when they're unclear. Often plain "the" works better, or name the thing explicitly. "This led to that, which caused these problems" → name what led, what it led to, what problems.
Use everyday words. A strength, not a weakness. "Utilize" → "use". "Commence" → "start". "Facilitate" → "help". Don't dress up plain ideas in fancy words.
When reviewing generated content:
Based on analysis of 22+ blog posts from alexop.dev. Apply these patterns when drafting blog content.
Opening hooks:
Transitional phrases:
Honest acknowledgments:
Emphasis patterns:
Personal anecdote:
"I once worked on a project that wanted to build an e-commerce website with Nuxt. We started simple, but six months in, our flat components folder had 50+ files."
Observation hook:
"After OpenAI released its impressive new image model, I started thinking about what creativity really means."
Pain point:
"Manual testing gets old fast. You change something, you check it manually, you ship it, and then production breaks anyway."
Challenge framing:
"Here's the thing: I don't write much code myself anymore. AI tools handle the implementation. My job? Review, refine, and ensure quality."
Problem statement:
"I think we all love Nuxt. One problem with using Nuxt for AI: the codebase is huge and Claude doesn't know all the latest patterns."
Honest assessment:
"Nuxt Layers add complexity. They're not always the right choice. But when your project grows, they provide the boundaries you'll wish you had from the start."
Actionable invitation:
"I'd love to hear how you're using this pattern. Drop me a message or check out the repository."
Key insight summary:
"The real power comes from separating what from how—keeping your store logic testable while handling the messy API details elsewhere."
Empowerment:
"Understanding how reactivity works under the hood gives you the power to debug performance issues and optimize where it matters."
Analogy before concept:
"Think of each layer as a mini Nuxt application. Your project root acts as the orchestrator."
Progressive complexity:
"Let's start simple. A Pinia plugin is a function that extends store functionality. Here's the minimal version... Now let's add the real logic..."
Honest trade-off:
"I recommend starting simple and graduating to complex patterns only when you feel the pain of the simpler approach. Don't over-engineer."
Must read guide on creating/editing mermaid charts with validation tools and syntax reference for all diagram types
Generate interactive HTML walkthroughs with clickable Mermaid diagrams (flowcharts and ER diagrams) that explain codebase features, flows, architecture, and database schemas. Use when asked to "walkthrough", "explain this flow", "how does X work", "trace the code path", "annotated diagram", "code walkthrough", "explain the architecture of", "walk me through", "database schema", "explain the tables", "data model".
Create a note from any resource: URL, book, podcast, article, video, GitHub repo, Reddit thread, PDF, quote, or raw idea. Trigger on "add", "save", "capture", "note this", "take notes on", or any request to record content in the knowledge base.
Add tweets to the Second Brain. Use when the user provides a Twitter/X URL and pasted tweet content, asking to "add a tweet", "save this tweet", or "capture this tweet".
Query your Second Brain with keyword search. Use when asked to "ask my notes", "what do I know about", "query my knowledge", "/ask", or when the user has a question that their notes might answer.
Create Obsidian templates for the Second Brain vault. Use when asked to "create a template", "make a template for", "add an Obsidian template", or "template for X".
