design-cognition-skill MCP — 사용 사례, 설치 & 라이브 데모

왜 쓰나요

핵심 기능

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

설치

클라이언트 선택

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "design-cognition-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/S0ulFood/design-cognition-skill",
        "~/.claude/skills/design-cognition-skill"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop → Settings → Developer → Edit Config 열기. 저장 후 앱 재시작.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "design-cognition-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/S0ulFood/design-cognition-skill",
        "~/.claude/skills/design-cognition-skill"
      ],
      "_inferred": true
    }
  }
}

Cursor는 Claude Desktop과 동일한 mcpServers 스키마 사용. 프로젝트 설정이 전역보다 우선.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "design-cognition-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/S0ulFood/design-cognition-skill",
        "~/.claude/skills/design-cognition-skill"
      ],
      "_inferred": true
    }
  }
}

Cline 사이드바의 MCP Servers 아이콘 클릭 후 "Edit Configuration" 선택.

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "design-cognition-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/S0ulFood/design-cognition-skill",
        "~/.claude/skills/design-cognition-skill"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop과 같은 형식. Windsurf 재시작 후 적용.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "design-cognition-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/S0ulFood/design-cognition-skill",
        "~/.claude/skills/design-cognition-skill"
      ]
    }
  ]
}

Continue는 맵이 아닌 서버 오브젝트 배열 사용.

~/.config/zed/settings.json

{
  "context_servers": {
    "design-cognition-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/S0ulFood/design-cognition-skill",
          "~/.claude/skills/design-cognition-skill"
        ]
      }
    }
  }
}

context_servers에 추가. 저장 시 Zed가 핫 리로드.

claude mcp add design-cognition-skill -- git clone https://github.com/S0ulFood/design-cognition-skill ~/.claude/skills/design-cognition-skill

한 줄 명령. claude mcp list로 확인, claude mcp remove로 제거.

사용 사례

실전 활용법: 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.

사전 조건

Skill installed — git clone https://github.com/S0ulFood/design-cognition-skill ~/.claude/skills/design-cognition-skill

흐름

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

대안

design-cognition-skill 다른 것과 비교

대안	언제 쓰나	단점/장점
Single prompt asking for 'pros and cons'	Quick vibe check	No structure; easy to skip hard questions
planning-with-files-skill	You need session persistence across a long project	Not a decision framework

design-cognition-skill