freemcplab / 디렉터리 / 플레이그라운드 / design-cognition-skill

● 커뮤니티 S0ulFood ⚡ 바로 사용

design-cognition-skill

Name: design-cognition-skill (Claude Skill)
Author: S0ulFood

제작: 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.

▶ 데모 보기 📦 설치 💡 사용 사례

왜 쓰나요

핵심 기능

4-role structured thinking
Domain-agnostic — works for product, eng, writing, strategy
Critic role forces honest self-assessment
Each role produces an artifact
Roles can be invoked individually for targeted help

라이브 데모

실제 사용 모습

design-cognition-skill.replay ▶ 준비됨

0/0

설치

작성자 저장소 · Claude Skills 공식 문서

사용 사례

실전 활용법: design-cognition-skill

Decide whether and how to ship a feature

👤 Product managers, founders ⏱ ~60 min intermediate

언제 쓸까: You're weighing a feature and the team's split.

흐름

Strategist

Use design-cognition-skill. Strategist role: should we build [feature]? What are the strategic tradeoffs?✓ 복사됨

→ Strategic framing — not just pros/cons, but tradeoffs against stated goals
Researcher

Researcher role: what's known from our data, users, competitors?✓ 복사됨

→ Evidence summary with gaps noted
Executor

Executor role: if we build it, what's the smallest valuable version?✓ 복사됨

→ Concrete MVP definition
Critic

Critic role: what's wrong with this plan? Be harsh.✓ 복사됨

→ Specific pushback, not generic risk flags

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

함정

Roles blur together — Run each role in its own prompt; don't ask for all four at once

함께 쓰기: filesystem

Get four kinds of feedback on a draft essay

👤 Writers ⏱ ~20 min beginner

언제 쓸까: Your essay needs more than 'looks good' or copy-editing.

흐름

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?).✓ 복사됨

→ Four distinct critiques

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

조합

다른 MCP와 조합해 10배 효율

design-cognition-skill + filesystem

Save each role's output as a separate doc

Save outputs to decision/<topic>/<role>.md for each role.✓ 복사됨

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.✓ 복사됨

도구

이 MCP가 노출하는 것

도구	입력	언제 호출
strategist	question	What matters here
researcher	question + context	What's true
executor	direction	What to build
critic	plan or artifact	What's wrong

비용 및 제한

운영 비용

API 쿼터: None
호출당 토큰: Moderate — 4 roles, each non-trivial
금액: Free
팁: Invoke single roles when you only need one lens.

보안

권한, 시크릿, 파급범위

자격 증명 저장: None

데이터 외부 송신: None from skill

문제 해결

자주 발생하는 오류와 해결

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

대안