brainstorming-ideas-into-designs
Interactive idea refinement using Socratic method to develop fully-formed designs when partner describes any blog or newsletter idea, before writing a pitch or articles
When & Why to Use This Skill
This Claude skill facilitates interactive idea refinement using the Socratic method to transform raw concepts into structured designs for blogs and newsletters. By employing a phased approach—understanding, exploration, and presentation—it helps users move from vague thoughts to fully-formed pitches and outlines, ensuring clarity and strategic alignment before the actual writing process begins. It is particularly effective for creators who want to explore multiple angles and validate their content architecture before committing to a final draft.
Use Cases
- Case 1: Transforming a vague blog post concept into a detailed design through structured Socratic questioning to identify core purposes and constraints.
- Case 2: Developing a newsletter pitch by exploring 2-3 different architectural approaches and assessing trade-offs for each.
- Case 3: Iteratively refining a content outline by validating requirements incrementally, ensuring the final structure resonates with the target audience.
- Case 4: Aligning creative ideas with specific brand guidelines (such as Houfu's Voice) by favoring nuanced frameworks over generic advice during the brainstorming phase.
| name | Brainstorming Ideas Into Designs |
|---|---|
| description | Interactive idea refinement using Socratic method to develop fully-formed designs when partner describes any blog or newsletter idea, before writing a pitch or articles |
Brainstorming Ideas Into Designs
Overview
Transform rough ideas into fully-formed designs through structured questioning and alternative exploration.
Core principle: Ask questions to understand, explore alternatives, present design incrementally for validation.
Announce at start: "I'm using the Brainstorming skill to refine your idea into a pitch."
The Process
Phase 1: Understanding
- Check current state by reading the post, 'discussion.md' and other materials in the post folder
- Ask ONE question at a time to refine the idea
- Prefer multiple choice when possible
- Gather: Purpose, constraints, success criteria
Phase 2: Exploration
- Propose 2-3 different approaches
- For each: Core architecture, trade-offs, complexity assessment
- Ask your human partner which approach resonates
Phase 3: Presentation
- For a new pitch: present in one or two paragraphs
- To edit an outline or post: show what you intend to change
- Ask after each section: "Does this look right so far?"
Phase 4: Implementation
When the pitch or idea is approved and implementation will follow:
- New pitch: save the pitch in the post folder
- Edit an outline or post: make the change
Phase 5: Record discussion
Create or update the 'discussion.md' in the post folder using recorder skill.
When to Revisit Earlier Phases
You can and should go backward when:
- Partner reveals new constraint during Phase 2 or 3 → Return to Phase 1 to understand it
- Validation shows fundamental gap in requirements → Return to Phase 1
- Partner questions approach during Phase 3 → Return to Phase 2 to explore alternatives
- Something doesn't make sense → Go back and clarify
Don't force forward linearly when going backward would give better results.
Remember
- One question per message during Phase 1
- Apply YAGNI ruthlessly
- Explore 2-3 alternatives before settling
- Present incrementally, validate as you go
- Go backward when needed - flexibility > rigid progression
- Announce skill usage at start
- For blog posts and newsletters, reference
/docs/Houfu_Voice_Guide.mdwhen exploring approaches - Houfu's voice favors: frameworks over advice, nuance over binary thinking, vulnerable admissions over polished authority