/ Annuaire / Playground / design-cognition-skill
● Communauté S0ulFood ⚡ Instantané

design-cognition-skill

par 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.

Pourquoi l'utiliser

Fonctionnalités clés

Démo en direct

Aperçu en pratique

design-cognition-skill.replay ▶ prêt
0/0

Installation

Dépôt de l’auteur · Documentation officielle des Skills Claude

Cas d'usage

Usages concrets : design-cognition-skill

Decide whether and how to ship a feature

👤 Product managers, founders ⏱ ~60 min intermediate

Quand l'utiliser : You're weighing a feature and the team's split.

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

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

Pièges
  • Roles blur together — Run each role in its own prompt; don't ask for all four at once
Combiner avec : filesystem

Get four kinds of feedback on a draft essay

👤 Writers ⏱ ~20 min beginner

Quand l'utiliser : Your essay needs more than 'looks good' or copy-editing.

Déroulement
  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?).✓ Copié
    → Four distinct critiques

Résultat : Feedback a friend wouldn't give you but a good editor would.

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

design-cognition-skill + filesystem

Save each role's output as a separate doc

Save outputs to decision/<topic>/<role>.md for each role.✓ Copié
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.✓ Copié

Outils

Ce que ce MCP expose

OutilEntréesQuand appelerCoût
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

Coût et limites

Coût d'exécution

Quota d'API
None
Tokens par appel
Moderate — 4 roles, each non-trivial
Monétaire
Free
Astuce
Invoke single roles when you only need one lens.

Sécurité

Permissions, secrets, portée

Stockage des identifiants : None
Sortie de données : None from skill

Dépannage

Erreurs courantes et correctifs

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

Alternatives

design-cognition-skill vs autres

AlternativeQuand l'utiliserCompromis
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

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills