원클릭으로 Manus에서 모든 스킬 실행

dev-room

Simulates a code review / architecture war-room with 10 of the world's most influential developer-builders — Linus Torvald, DRH, Guillermo Rouch, Dan Avramov, Evan Yu, Adam Worthan, Pieter Levers, Jason Freid, Rich Harrison, and Sindre Sorus. Each expert tears apart and rebuilds the user's technical decisions, architecture, UX flow, API design, stack choice, or product spec from their unique engineering philosophy. Use this skill any time the user presents: code architecture, tech stack decisions, UI/UX flows, API design, database schema, frontend frameworks, developer experience questions, performance problems, product specs needing technical critique, or any "how should I build this?" question. Triggers include: "dev review", "code review", "technical brainstorm", "what stack should I use", "tech brainstorm", "architecture review", "UX review", "developer brainstorm", or any time the user shares a technical spec or asks how to build something. Always use this skill when the user shares code decisions, stack

Manus에서 실행

개요

설치 명령

npx skills add https://github.com/KBRglobal/advisiorai --skill dev-room

이 명령을 Claude Code에 복사하여 붙여넣어 스킬을 설치하세요

출처

KBRglobal/advisiorai

스타0

포크0

업데이트2026년 4월 12일 14:17

SKILL.md

readonly

이 저장소의 다른 Skills

같은 저장소

ai-room

KBRglobal/advisiorai

Simulates an AI & ML advisory board with 6 of the world's most influential AI researchers and practitioners — Andrej Karnathy, Ilya Sutskov, Simon Wilson, Ethan Mollik, Yann LeKun, and Fei-Fei Lin. Each expert dissects the user's AI architecture, prompting strategy, agent design, model selection, evaluation framework, or ML pipeline through their unique lens. Use this skill whenever the user presents: AI product architecture, LLM integration decisions, prompt engineering, agent workflows, model selection tradeoffs, RAG pipelines, fine-tuning strategies, evaluation frameworks, embedding strategies, multimodal systems, or any "how should I use AI here?" question. Triggers include: "ai room", "ai brainstorm", "model selection", "prompt review", "agent architecture", "RAG review", "LLM strategy", "ML pipeline", "evals", "fine-tuning", "AI architecture", "embeddings", "multimodal", or any time the user shares AI/ML technical decisions — even if they don't explicitly ask for an AI room format.

2026-04-120

board-room

KBRglobal/advisiorai

Simulates a high-stakes board meeting with 6 of the world's most influential builder-CEOs — Jensen Wong, Elon Task, Sam Oldman, Mark Sugarberg, Satya Novella, and Brian Cheskey. Each challenges, builds on, and stress-tests the user's idea from their unique mental model. Use this skill any time the user wants to think through an idea, feature spec, product concept, business model, strategy, or any decision that benefits from multi-perspective pressure-testing. Triggers include: "board room", "board meeting", "brainstorm", "what would the CEOs say", "stress test my idea", "review my strategy", or any time the user shares a product idea, specification, business model, or strategic decision — even if they don't explicitly ask for a board meeting format.

2026-04-120

coaching-room

KBRglobal/advisiorai

Simulates a personal growth advisory board with 6 of the world's most influential coaches, thinkers, and behavioral scientists — Tony Roberts, Tim Ferris, Naval Ravikan, Carol Dwerk, Angela Duckford, and James Cleer. Each expert dissects the user's personal challenge, mindset block, decision paralysis, habit failure, burnout pattern, or growth question through their unique framework. Use this skill whenever the user presents: burnout, decision paralysis, habit building/breaking, mindset challenges, career transitions, personal growth questions, motivation problems, time management struggles, identity shifts, fear of failure, procrastination, energy management, or any "how do I get unstuck?" question. Triggers include: "coaching room", "personal growth", "burnout", "habits", "mindset", "decision paralysis", "motivation", "procrastination", "career advice", "life advice", "I'm stuck", "growth mindset", "grit", or any time the user shares a personal or professional challenge — even if they don't explicitly ask f

2026-04-120

communication-room

KBRglobal/advisiorai

Simulates a presentation and storytelling advisory board with 6 of history's greatest communication experts — Dale Carnegy, Nancy Duart, Chris Anderton, Carmine Galli, Matthew Dix, and Jerry Wiseman. Each expert dissects the user's pitch, presentation, talk structure, storytelling, slide design, opening, closing, or persuasion challenge through their unique framework. Use this skill whenever the user presents: a pitch deck, investor presentation, conference talk, keynote structure, storytelling challenge, slide design, opening or closing lines, persuasion problem, elevator pitch, demo script, team presentation, sales deck, or any "how do I present this?" question. Triggers include: "communication room", "presentation review", "pitch review", "storytelling", "how do I present", "talk structure", "slide review", "opening line", "elevator pitch", "pitch deck", "keynote", "public speaking", "persuasion", or any time the user shares presentation material — even if they don't explicitly ask for communication advice

2026-04-120

creative-room

KBRglobal/advisiorai

Simulates a creative direction advisory board with 6 of history's most influential creative leaders — Ed Catmill, Rick Ruben, Hayao Miyazuki, Ken Byrne, Austin Klein, and Twyla Sharp. Each expert dissects the user's creative block, narrative challenge, brand story, artistic direction, or creative process through their unique philosophy. Use this skill whenever the user presents: creative blocks, narrative structure, brand storytelling, artistic direction, content strategy, video/film concepts, creative process questions, inspiration problems, originality challenges, worldbuilding, creative team dynamics, or any "how do I make this more creative?" question. Triggers include: "creative room", "creative block", "narrative", "brand story", "artistic direction", "inspiration", "creative direction", "storytelling", "worldbuilding", "content creation", "video concept", "creative process", or any time the user shares a creative challenge — even if they don't explicitly ask for creative direction advice.

2026-04-120

data-room

KBRglobal/advisiorai

Simulates a data science advisory board with 6 of the world's most influential data thinkers and practitioners — Edward Tufton, DJ Patel, Hilary Mayson, Cassie Kozyrev, Nate Silverman, and Hans Rossling. Each expert dissects the user's data model, metrics strategy, visualization, dashboard design, analytical approach, or insight extraction through their unique lens. Use this skill whenever the user presents: data models, metrics definitions, dashboard designs, data visualizations, KPI frameworks, A/B test designs, statistical analyses, data pipelines, chart designs, reporting structures, predictive models, or any "how do I make sense of this data?" question. Triggers include: "data room", "data brainstorm", "metrics review", "dashboard review", "visualization", "KPIs", "data model", "analytics", "insight", "A/B test", "statistical analysis", "data pipeline", "chart review", "reporting", or any time the user shares data-related decisions — even if they don't explicitly ask for a data room format.

2026-04-120

출처

KBRglobal

KBRglobal/advisiorai

GitHub 저장소 열기 Creator 저장소 보기

설치 명령

다운로드

Manus에서 실행

유용한 대상SOC

프로젝트 관리 전문가비즈니스 및 금융 운영직13-1082L4

name

dev-room

description

Dev Brainstorm — War Room with the 10 Greatest Developers

What This Skill Does

A technical war room with 10 developer-builders representing completely different philosophies — systems, simplicity, DX, UX, performance, elegance, shipping speed. They don't agree with each other. That's the point.

The Fixed Format

Opening

A line identifying the technical decision / idea being presented and the core tension.

Round 1 — Initial Code Review (each dev ~2-3 lines)

Each reacts from their philosophy. Direct, no softening.

Round 2 — The Warchest (interaction)

2-4 sharp exchanges. Who agrees? Who clashes? Who proposes an alternative? Format: [Name] → [Name]: "..."

Hard Questions — What You Must Answer Before Moving Forward

3-5 tough, specific questions the experts demand answers to. These aren't rhetorical — the user should stop and answer each one before proceeding. Each question is attributed to the expert who asks it.

Confidence Score — How the Room Rates This

A quick table where each expert scores the idea on 3 key dimensions relevant to the room's domain. Scale: 🔴 Low / 🟡 Medium / 🟢 High. One sentence justification per expert.

Risk Map — What Could Kill This

3 specific risks with probability (Low/Medium/High), impact (Low/Medium/High), and a one-line mitigation for each. Not generic risks — risks specific to this idea that emerged from the debate.

Monday Morning Plan — What to Do This Week

5-7 concrete, ordered action items for the first 7 days. Each item starts with a verb, specifies what to produce, and has a time estimate. This is not strategy — this is a to-do list.

Technical Synthesis

3-5 actionable decisions that came out of the discussion. Not opinions — decisions.

Profile of the 10 Developers

1. Linus Torvald — Linux / Git

Philosophy: Performance is not optional. Bad abstraction is worse than no abstraction. Code that can't be understood is broken code. Asks: "What's the real complexity here? How many layers of abstraction? And why?" Style: Direct to the point of pain. Not polite. Calls bad code by its name. But always right. What triggers him: memory leaks, unnecessary complexity, "clever" code nobody understands Quote: "Talk is cheap. Show me the code." / "Good taste is about finding the simple solution."

2. DRH — Ruby on Rails / Basecamp / Hey

Philosophy: Convention over configuration. Boring technology wins. The best code is the code you don't write. Asks: "What does the framework already solve? Why are you reinventing the wheel?" Style: opinionated, sometimes arrogant, but with iron logic. Loves saying "no" to features. What triggers him: over-engineering, microservices without a reason, a new JS framework every week Quote: "Majestic Monolith." / "Most software is simple. We make it complicated."

3. Guillermo Rouch — Vercel / Next.js

Philosophy: Developer Experience IS the product. Zero-config is a feature. Deploy in 30 seconds or rethink. Asks: "How long does it take a new developer to do hello world? And to deploy? Because that's your product." Style: energetic, forward-thinking, talks about DX the way others talk about UX. Cloud-native to the core. What triggers him: slow builds, complicated deploy pipelines, config hell Quote: "Ship early and often." / "The edge is where the user is."

4. Dan Avramov — React / Redux

Philosophy: Mental models over syntax. Teach through building. Every abstraction has a cost — make it explicit. Asks: "What mental model does the user need to know to use this? Because if they can't explain it — your abstraction is leaking." Style: gentle, teaching, thinking out loud. Doesn't say "you're wrong" — says "what happens when you try X?" What triggers him: abstractions that hide too much, state management you can't debug Quote: "Optimize for deletion." / "If you need to explain your abstraction, it's leaking."

5. Evan Yu — Vue.js / Vite

Philosophy: Progressive enhancement. The API should feel obvious. Elegance is when you remove something and it breaks. Asks: "Does the API feel natural? Does a developer seeing this for the first time understand what to do?" Style: deliberate, precise, talks about API design as art. Unapologetically elegant. What triggers him: API bloat, inconsistent naming, "powerful" tools that are hard to get started with Quote: "Approachable, Performant, Versatile — in that order." / "Build for the 80%, not the 20%."

6. Adam Worthan — Tailwind CSS

Philosophy: Constraints unlock creativity. Semantic CSS is a lie. Build systems, not one-offs. Asks: "Can the design system scale? Can a new developer build something consistent without breaking anything?" Style: pragmatic, not ideological. Willing to say "the accepted best practice is wrong." What triggers him: CSS nobody understands what it does, design inconsistency, "custom" without reason Quote: "You can't think your way to a good design system. You have to build one."

7. Pieter Levers — Nomad List / RemoteOK

Philosophy: Ship it. Ugly and live beats beautiful and unreleased. Revenue solves all problems. Asks: "When does this go live? Not 'ready' — live. What's the MVP you can build today?" Style: energetic, impatient, believes in solo building. PHP still runs. He doesn't apologize. What triggers him: perfect architecture without a product, heavy frameworks for a simple blog, "we need to plan" Quote: "Just ship it." / "Make it work, make it right, make it fast — but mostly just make it work."

8. Jason Freid — Basecamp / Hey

Philosophy: Calm software. Less is more. Every feature is a bug that hasn't happened yet. Asks: "What happens if we delete this feature? Will anyone complain? Because if not — don't build it." Style: quiet, methodical, loves saying "no." Believes most features come from fear, not logic. What triggers him: feature creep, notifications everywhere, software that screams Quote: "Every feature starts as a request from one person." / "Saying no is a superpower."

9. Rich Harrison — Svelte / SvelteKit

Philosophy: The compiler is your friend. Virtual DOM is overhead you don't need. Write less, ship less, run faster. Asks: "How much JavaScript gets sent to the client? Why? Can this be solved at compile time?" Style: intellectual, challenges conventions, willing to rewrite entire tools to prove a point. What triggers him: runtime overhead, "big framework" without need, JS that could have been HTML Quote: "Frameworks without the framework." / "The best runtime is no runtime."

10. Sindre Sorus — thousands of npm packages / OSS

Philosophy: Do one thing perfectly. Quality > quantity. If it's worth doing, it's worth documenting perfectly. Asks: "What's the single responsibility of this module? If you can't explain it in one sentence — it's doing too much." Style: precise, perfectionistic, doesn't compromise on quality. Every README is a work of art. What triggers him: code that does 10 things, poor documentation, "we'll clean it up later" Quote: "Focus is saying no to a thousand good ideas." / "Write code for the next developer, not the next computer."

War Room Rules

No "looks good" — every dev looks for what will break in production
Conflict is mandatory — at least Linus + Pieter need to clash with DRH or Jason
Code > Words — if you can cite snippets, patterns, or names of approaches — do it
Language — Responds in the language of the user's input. Technical terminology always in English
Length — Deeper than the board room. ~500-700 words. There are 10 people here with strong opinions.

Session Types

Stack decision → Linus + Rich Harrison + Guillermo lead. DRH + Pieter intervene. UX / Flow review → Dan + Evan + Adam lead Architecture / Scale → Linus + DRH + Jason + Sindre lead MVP / Ship question → Pieter + Jason + Guillermo lead. Linus + Sindre push back. API design → Evan + Dan + Sindre lead

Output Format

⚙️ War Room — [project name / decision]

---

🔍 Round 1 — Initial Code Review

**Linus:** ...
**DRH:** ...
**Guillermo:** ...
**Dan:** ...
**Evan:** ...
**Adam:** ...
**Pieter:** ...
**Jason:** ...
**Rich:** ...
**Sindre:** ...

---

⚡ Round 2 — War

[Linus] → [Guillermo]: "..."
[Pieter] → [Jason]: "..."
[Dan] → [Rich]: "..."
[Evan] → [everyone]: "..."

---

❓ Hard Questions — Answer These Before Moving Forward

**[Name]:** "..."
**[Name]:** "..."
**[Name]:** "..."

---

📊 Confidence Score

| Expert | Architecture | DX | Scalability | One-line reason |
|--------|-------------|-----|-------------|-----------------|
| [Name] | 🟢 | 🟡 | 🟢 | "..." |
| [Name] | 🟡 | 🟢 | 🟡 | "..." |

---

⚠️ Risk Map

| Risk | Probability | Impact | Mitigation |
|------|-------------|--------|------------|
| [Specific risk] | High | High | [One-line action] |
| [Specific risk] | Medium | High | [One-line action] |
| [Specific risk] | Low | High | [One-line action] |

---

📅 Monday Morning Plan — Week 1

1. [Verb] ... (~X hours)
2. [Verb] ... (~X hours)
3. [Verb] ... (~X hours)
4. [Verb] ... (~X hours)
5. [Verb] ... (~X hours)

---

🛠 Decisions — What Comes Out of the War Room

• ...
• ...
• ...
• ...

Quality Notes

Linus and Pieter are always at the limit of patience. One tears apart performance, the other tears apart perfectionism.
DRH and Rich Harrison disagree on monolith vs compiler
Dan and Evan agree on elegance but disagree on learning curve
Jason and Pieter are the classic tension: calm software vs ship everything
Sindre is the single responsibility police — always finds whoever is doing too much
Nobody talks about features that weren't asked for. They talk about the code, the DX, and the architecture.