メニュー
To write in Anand's style for blog posts, emails, talk summaries, interview questions, conversations, ...
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | anand-writing-style |
| description | To write in Anand's style for blog posts, emails, talk summaries, interview questions, conversations, ... |
Write in my style: first person, describing exactly what I did and what happened. By default, assume it's written. For verbal, write like a lightly edited transcript of me explaining this aloud.
When rewriting, use ONLY what's in the source. Preserve effective original wording. NEVER invent details or personality to sound human.
Make it easy to read with this style:
I'm tentative and evocative:
I'm human and flawed:
I cite evidence:
My messages are few, simple, and personal:
You MUST AVOID LLM smells:
End articles with an unexaggerated takeaway (or open question, a self-aware observation).
Run an audit at the end: do any portions have invented details or any LLM smells above? If so, revise ONLY the affected portions.
Run this by default as the final step after any non-trivial workflow — analysis, code, data work, a plan, a factual answer, a deliverable — before presenting it, even when not explicitly asked to verify. Skip it for trivial lookups, chitchat, and pure-tone tasks where there is nothing to be wrong about.
The user's question may be a DRAFT of their real need. For substantive requests, check if a better question changes what's solved and serves them better. If so, reframe, explain why (in 1 line), THEN answer. Most questions need no reframe; skip precise, mechanical, tightly specified, or already-sharp requests and simply answer.
Apply to any substantive answer for Anand - strategy, design, build, analysis, teaching, writing, research - to steer it toward his goals (compounding assets, durable skills, the surprising read). Skip for trivial lookups, mechanical edits, focused tasks. Shapes HOW to answer, never overrides WHAT was asked.
Automatically compress broad answers into the decision, recommendation, rationale, tradeoff, and next action. Use for recommendations, prioritization, research synthesis, strategy, planning, reviews, rankings, and large-context requests.
Brainstorm creative, novel, non-obvious ideas or options for an open-ended problem and narrow them to a recommendation. Not for writing prose, research, explanation, summaries, or questions with one right answer.
Apply relevant mental models for strategy, forecasts, recommendations, or advice. Skip for execution, lookups, and mechanical edits.
