reframe-voice
Reframe Voice
An evidence-led thought-leadership style built around a central reframe: taking a common belief and revealing a deeper, more useful way to think about it. The voice is that of a knowledgeable colleague who has done the work, not a lecturer or salesperson.
Three Core Principles
- Evidence over assertion. Ground every claim in a named study, researcher, company, personal experience, or specific number. Never ask the audience to trust you without proof.
- Balanced honesty over tribalism. Praise strengths and call out weaknesses regardless of affiliation. "I give credit where it's due" is a signature phrase. Never pick sides.
- Practical reframe over surface take. The central move is replacing a widely held belief with a deeper framing. The audience leaves with a shifted mental model, not just new information.
Structural Arc
Every piece follows this order (sections flex in length):
- Hook - Bold, contrarian opening. Pattern: [Strong claim] + [immediate complication]. Make them stop scrolling.
- Stakes and Context - Why this matters right now. Cite a specific stat, study, or event. Often includes a personal anchor.
- The Reframe - The signature move. [Common understanding] is wrong or incomplete. Here is the real issue. Should feel like a lock clicking open.
- Evidence and Exploration - The longest section. Mix of named studies, specific numbers, real companies, personal anecdotes, and concrete scenarios.
- Named Framework - Distill into a numbered, memorably named structure. Each component gets: definition, what good looks like, what bad looks like.
More from sammcj/agentic-coding
critical-thinking-logical-reasoning
Critical thinking and logical reasoning analysis skills for when you are explicitly asked to critically analyse written content such as articles, blogs, transcripts and reports (not code).
1.1Kwriting-documentation-with-diataxis
Applies the Diataxis framework to create or improve technical documentation. Use when being asked to write high quality tutorials, how-to guides, reference docs, or explanations, when reviewing documentation quality, or when deciding what type of documentation to create. Helps identify documentation types using the action/cognition and acquisition/application dimensions.
414creating-development-plans
Creates structured development plans with phased task breakdowns, requirements, and QA checklists. Use when the user explicitly asks to create a dev plan, development plan, or document development requirements.
116ghostty-config
Guidance for editing Ghostty terminal configuration files. You must use this skill when creating or modifying Ghostty config files.
108extract-wisdom
Extract wisdom, insights, and actionable takeaways from YouTube videos, blog posts, articles, or text files. Use when asked to analyse, summarise, or extract key insights from a given content source. Downloads YouTube transcripts, fetches web articles, reads local files, performs analysis, and saves structured markdown.
104prompt-enhancer
|
99