/ Directorio / Playground / design-cognition-skill
● Comunidad S0ulFood ⚡ Instantáneo

design-cognition-skill

por S0ulFood · S0ulFood/design-cognition-skill

Four-role design-thinking framework (Strategist, Researcher, Executor, Critic) for Claude Code — works for any domain, not just product design.

A domain-agnostic design-thinking skill. Claude plays four roles in sequence: Strategist (what matters), Researcher (what's true), Executor (what to build), Critic (what's wrong). Useful for any non-trivial decision — features, essays, architecture, roadmaps.

Por qué usarlo

Características clave

Demo en vivo

Cómo se ve en la práctica

design-cognition-skill.replay ▶ listo
0/0

Instalación

Repositorio del autor · Documentación oficial de Skills de Claude

Casos de uso

Usos del mundo real: design-cognition-skill

Decide whether and how to ship a feature

👤 Product managers, founders ⏱ ~60 min intermediate

Cuándo usarlo: You're weighing a feature and the team's split.

Flujo
  1. Strategist
    Use design-cognition-skill. Strategist role: should we build [feature]? What are the strategic tradeoffs?✓ Copiado
    → Strategic framing — not just pros/cons, but tradeoffs against stated goals
  2. Researcher
    Researcher role: what's known from our data, users, competitors?✓ Copiado
    → Evidence summary with gaps noted
  3. Executor
    Executor role: if we build it, what's the smallest valuable version?✓ Copiado
    → Concrete MVP definition
  4. Critic
    Critic role: what's wrong with this plan? Be harsh.✓ Copiado
    → Specific pushback, not generic risk flags

Resultado: A decision doc you can share that shows the thinking, not just the conclusion.

Errores comunes
  • Roles blur together — Run each role in its own prompt; don't ask for all four at once
Combinar con: filesystem

Get four kinds of feedback on a draft essay

👤 Writers ⏱ ~20 min beginner

Cuándo usarlo: Your essay needs more than 'looks good' or copy-editing.

Flujo
  1. Run each role on the draft
    Use design-cognition-skill on my essay. Strategist (is the point worth making?), Researcher (are claims defensible?), Executor (is the structure tight?), Critic (what would a hostile reader attack?).✓ Copiado
    → Four distinct critiques

Resultado: Feedback a friend wouldn't give you but a good editor would.

Combinaciones

Combínalo con otros MCPs para multiplicar por 10

design-cognition-skill + filesystem

Save each role's output as a separate doc

Save outputs to decision/<topic>/<role>.md for each role.✓ Copiado
design-cognition-skill + infinite-gratitude-skill

Pair with multi-agent research for breadth plus this for depth

Use infinite-gratitude for discovery, then design-cognition for the final decision doc.✓ Copiado

Herramientas

Lo que expone este MCP

HerramientaEntradasCuándo llamarCoste
strategist question What matters here 0
researcher question + context What's true 0
executor direction What to build 0
critic plan or artifact What's wrong 0

Coste y límites

Lo que cuesta ejecutarlo

Cuota de API
None
Tokens por llamada
Moderate — 4 roles, each non-trivial
Monetario
Free
Consejo
Invoke single roles when you only need one lens.

Seguridad

Permisos, secretos, alcance

Almacenamiento de credenciales: None
Salida de datos: None from skill

Resolución de problemas

Errores comunes y soluciones

Critic is too gentle

Prompt for adversarial framing — 'what would a hostile VC attack'

Roles produce same content

Separate into 4 prompts; prime each role explicitly

Alternativas

design-cognition-skill vs otros

AlternativaCuándo usarlaContrapartida
Single prompt asking for 'pros and cons'Quick vibe checkNo structure; easy to skip hard questions
planning-with-files-skillYou need session persistence across a long projectNot a decision framework

Más

Recursos

📖 Lee el README oficial en GitHub

🐙 Ver issues abiertas

🔍 Ver todos los 400+ servidores MCP y Skills