Communitygithub.com

wondelai/동기부여-설계

제품과 팀을 위한 자율성, 숙달, 목적(AMP) 기반 동기 시스템을 설계합니다. 내재적 동기부여, 게이미피케이션 실패, 팀 인센티브, 자율성, 숙달, 목적 중심, 직원 참여, 보상 시스템 등의 키워드에 반응합니다.

동기부여-설계란 무엇인가요?

이 스킬은 제품과 팀에서 지속 가능한 동기부여 시스템을 설계하기 위한 종합 가이드입니다. 당근과 채찍 방식이 실패하는 이유와 함께, 자율성(Autonomy), 숙달(Mastery), 목적(Purpose)의 AMP 프레임워크를 활용하여 내재적 동기부여를 극대화하는 방법을 설명합니다. 사용자가 게이미피케이션 문제 해결, 온보딩 진행 시스템 설계, 또는 고성과 팀 구조 구축을 논의할 때 활성화됩니다. 또한, 습관 형성 제품 루프(hooked-ux)와 유지율 개선(improve-retention) 스킬과 연동되어 더 포괄적인 행동 설계를 지원합니다. 이 스킬은 개발자, 제품 관리자, 팀 리더에게 실제 적용 가능한 전략과 구체적인 예시를 제공하여, 외부 보상이 아닌 내재적 동기를 통해 지속적인 참여와 성과를 이끌어내는 방법을 안내합니다.

지원 대상~Claude Code~Codex CLI~Cursor
Part ofDesign & UI
npx skills add https://github.com/wondelai/skills/tree/main/skills/drive-motivation
원본 보기→모든 스킬 둘러보기

즐겨 사용하는 AI에게 물어보기

이 에이전트 스킬이 미리 로드된 새 채팅을 엽니다.

OpenAIChatGPTClaudeClaudeGeminiGeminiGrokGrokPerplexityPerplexityDeepSeekDeepSeek

문서

동기부여-설계은(는) 무엇을 하나요?

자율성(Autonomy), 숙달(Mastery), 목적(Purpose)(AMP)을 활용한 동기 시스템 설계

이 스킬은 제품과 팀을 위한 동기부여 시스템을 설계할 때 사용됩니다. 사용자가 "내재적 동기부여", "게이미피케이션이 효과 없음", "팀 인센티브", "자율성", "숙달", "목적 중심", "직원 참여", 또는 "보상 시스템"을 언급할 때 활성화됩니다. 또한 온보딩 진행 시스템을 설계하거나, 고장난 게이미피케이션을 수정하거나, 지속적인 고성과를 유지하는 팀 구조를 구축할 때도 사용하세요. 당근과 채찍 방식이 실패하는 이유와 진행 시스템 구축 방법을 다룹니다.

습관 형성 제품 루프는 hooked-ux를 참조하세요. 유지율 행동 설계는 improve-retention을 참조하세요.

왜 당근과 채찍이 실패하는가?

  • 외재적 동기는 단기적 성과를 높이지만, 내재적 동기를 약화시켜 장기적으로 생산성을 떨어뜨립니다.
  • 보상이 목적이 되면 창의성과 문제 해결 능력이 저하됩니다.
  • 처벌은 두려움을 만들고 혁신을 억제합니다.

AMP 프레임워크

자율성 (Autonomy)

  • 선택권 제공: 사용자가 자신의 방법으로 목표를 달성할 수 있도록 하세요.
  • 자기 주도: 제어가 아닌 가이드를 제공하고, 자신의 학습 경로를 선택할 수 있게 하세요.
  • 예시: 깃허브의 '포크' 기능, 사용자가 자신만의 워크플로우를 만드는 것.

숙달 (Mastery)

  • 진행 단계: 명확하고 도전적인, 하지만 달성 가능한 단계를 설계하세요.
  • 피드백 루프: 즉각적이고 의미 있는 피드백을 제공하여 지속적인 학습을 유도하세요.
  • 예시: 두오링고의 레벨 시스템, 체스닷컴의 등급 시스템.

목적 (Purpose)

  • 큰 그림 연결: 작업이 더 큰 목표에 어떻게 기여하는지 보여주세요.
  • 영향력 강조: 사용자에게 그들의 노력이 미치는 영향을 알리세요.
  • 예시: 위키피디아 편집자에게 '지식을 전 세계와 공유한다'는 목적을 상기시키기.

적용 방법

  1. 현재 동기 시스템 식별: 외재적/내재적 요소를 분석합니다.
  2. AMP 격차 분석: 어느 영역이 부족한지 확인합니다.
  3. 개입 설계: 부족한 영역을 보강하는 구체적인 기능이나 프로세스를 구축합니다.
  4. 측정 및 반복: 참여도, 유지율, 만족도 지표를 추적하고 개선합니다.

예시: 온보딩 진행 시스템

  • 1단계: 환영 메시지 + 핵심 가치 설명 (목적)
  • 2단계: 첫 번째 작은 작업 선택 (자율성)
  • 3단계: 실시간 피드백으로 작업 완료 (숙달)
  • 4단계: '첫 걸음' 배지와 함께 커뮤니티에 공유 (목적 + 사회적 증거)

관련 스킬

  • [hooked-ux]: 습관 형성 제품 루프 설계
  • [improve-retention]: 유지율 행동 설계 전략

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

wondelai/37signals-way

Build lean, opinionated products using the 37signals philosophy from Getting Real, Rework, and Shape Up. Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", or "opinionated software". Also trigger when cutting scope to ship faster, running small teams, avoiding long-term roadmaps, or eliminating meetings. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.

wondelai/blue-ocean-strategy

Create uncontested market space using value innovation instead of competing head-to-head. Use when the user mentions "blue ocean", "red ocean", "strategy canvas", "ERRC framework", "value innovation", "non-customers", "buyer utility map", "eliminate-reduce-raise-create", or "uncontested market". Also trigger when comparing pricing strategies, exploring new market categories, finding underserved customer segments, or asking how to stop competing on price. Covers the Four Actions Framework, buyer utility map, and value-cost trade-offs. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.

wondelai/clean-architecture

Structure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters", "hexagonal architecture", "use case boundary", "onion architecture", "screaming architecture", or "framework independence". Also trigger when decoupling business logic from databases or frameworks, defining module boundaries, or debating where to put business rules. Covers component principles, boundaries, and SOLID. For code quality, see clean-code. For domain modeling, see domain-driven-design.

wondelai/clean-code

Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "code review", "naming conventions", "function too long", "code smells", "readable code", "boy scout rule", "single responsibility", or "unit test quality". Also trigger when reviewing pull requests for readability, refactoring messy functions, debating comment styles, or improving error handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture, see clean-architecture.

wondelai/contagious

Engineer word-of-mouth and virality using the STEPPS framework (Social Currency, Triggers, Emotion, Public, Practical Value, Stories). Use when the user mentions "go viral", "word of mouth", "shareable content", "social currency", "why people share", "viral loop", "referral program", or "organic growth". Also trigger when designing shareable features, crafting social media campaigns, or building products that spread through peer recommendation. Covers environmental triggers and high-arousal emotional content. For sticky messaging, see made-to-stick. For persuasion tactics, see influence-psychology.

wondelai/continuous-discovery

Build a weekly cadence of customer touchpoints using Opportunity Solution Trees, assumption mapping, and interview snapshots. Use when the user mentions "continuous discovery", "opportunity solution tree", "weekly interviews", "assumption testing", "discovery habits", "product trio", or "outcome-based roadmap". Also trigger when setting up regular customer feedback loops, prioritizing which experiments to run, or connecting discovery insights to delivery work. Covers experience mapping, co-creation, and prioritizing opportunities. For interview technique, see mom-test. For team structure, see inspired-product.

wondelai/cro-methodology

Audit websites and landing pages for conversion issues and design evidence-based A/B tests. Use when the user mentions "landing page isnt converting", "conversion rate", "A/B test", "why visitors leave", "objection handling", "bounce rate", "split testing", or "conversion funnel". Also trigger when diagnosing why signups are low, designing experiment hypotheses, or auditing checkout flows for friction points. Covers funnel mapping, persuasion assets, and objection/counter-objection frameworks. For overall marketing strategy, see one-page-marketing. For usability issues, see ux-heuristics.

wondelai/crossing-the-chasm

Navigate the technology adoption lifecycle from early adopters to mainstream market. Use when the user mentions "crossing the chasm", "beachhead segment", "whole product", "early adopters vs. mainstream", "tech go-to-market", "bowling pin strategy", "technology adoption lifecycle", or "pragmatist buyers". Also trigger when a startup has early traction but struggles to grow beyond initial users, or when planning go-to-market for technical products. Covers D-Day analogy, bowling-pin strategy, and positioning against incumbents. For product positioning, see obviously-awesome. For new market creation, see blue-ocean-strategy.

wondelai/ddia-systems

Design data systems by understanding storage engines, replication, partitioning, transactions, and consistency models. Use when the user mentions "database choice", "replication lag", "partitioning strategy", "consistency vs availability", "stream processing", "ACID transactions", "eventual consistency", or "LSM tree vs B-tree". Also trigger when choosing between SQL and NoSQL, designing data pipelines, or debugging distributed system consistency issues. Covers data models, batch/stream processing, and distributed consensus. For system design, see system-design. For resilience, see release-it.

wondelai/design-everyday-things

Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions "why is this confusing", "affordance", "error prevention", "discoverability", "human-centered design", "fault tolerance", "mental model", "mapping", or "seven stages of action". Also trigger when diagnosing why users make mistakes, reducing product complexity, or improving error messages and feedback systems. Covers the gulfs of execution and evaluation. For usability scoring, see ux-heuristics. For iOS-specific patterns, see ios-hig-design.

wondelai/design-sprint

Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions "design sprint", "validate in a week", "rapid prototype", "test with users", "de-risk before building", "GV sprint", "prototype testing", or "design workshop". Also trigger when a team needs to make a critical product decision quickly, resolve stakeholder disagreements, or test risky ideas before investing in development. Covers mapping, sketching, deciding, prototyping, and testing. For ongoing experimentation, see lean-startup. For customer job analysis, see jobs-to-be-done.

wondelai/domain-driven-design

Model software around the business domain using bounded contexts, aggregates, and ubiquitous language. Use when the user mentions "domain modeling", "bounded context", "aggregate root", "ubiquitous language", "anti-corruption layer", "context mapping", "domain events", or "strategic design". Also trigger when splitting a monolith into services, defining microservice boundaries, or aligning code structure with business processes. Covers entities vs value objects, domain events, and context mapping strategies. For architecture layers, see clean-architecture. For complexity, see software-design-philosophy.

wondelai/high-perf-browser

Optimize web performance through network protocols, resource loading, and browser rendering internals. Use when the user mentions "page load speed", "Core Web Vitals", "HTTP/2", "resource hints", "network latency", "render blocking", "TCP optimization", "service worker", or "critical rendering path". Also trigger when diagnosing slow page loads, optimizing time to first byte, choosing between WebSocket and SSE, or reducing bundle sizes. Covers TCP/TLS optimization, caching strategies, WebSocket/SSE, and protocol selection. For UI visual performance, see refactoring-ui. For font loading, see web-typography.

wondelai/hooked-ux

Design habit-forming product loops using the Hook Model (Trigger, Action, Variable Reward, Investment). Use when the user mentions "users arent coming back", "engagement loops", "habit formation", "push notifications", "variable rewards", "daily active users", "habit zone", or "user retention loops". Also trigger when designing notification strategies, building streaks or progress systems, or analyzing why users stop using a product after initial signup. Covers ethics evaluation and onboarding for habits. For friction reduction and B=MAP, see improve-retention. For viral sharing, see contagious.

wondelai/hundred-million-offers

Create irresistible offers using the Value Equation, bonus stacking, risk-reversing guarantees, and ethical scarcity. Use when the user mentions "pricing strategy", "irresistible offer", "bonuses and guarantees", "value-to-price ratio", "offer naming", "grand slam offer", "guarantee strategy", or "premium pricing justification". Also trigger when packaging products for higher perceived value, designing money-back guarantees, or structuring pricing tiers to maximize conversions. Covers the MAGIC naming formula and starving-crowd targeting. For product positioning, see obviously-awesome. For outbound sales, see predictable-revenue.

wondelai/improve-retention

Diagnose and fix retention problems using behavior design (B=MAP). Use when the user mentions "users drop off", "activation rate", "onboarding friction", "retention metrics", "why users dont complete", "churn analysis", "user activation", or "aha moment". Also trigger when analyzing cohort retention curves, designing activation milestones, reducing time-to-value for new users, or investigating why users stop after their first session. Covers the Ability Chain, prompt design, and tiny behaviors that compound. For habit loops and variable rewards, see hooked-ux. For intrinsic motivation, see drive-motivation.

wondelai/influence-psychology

Apply the six principles of ethical persuasion (reciprocity, commitment, social proof, authority, liking, scarcity) to product design, copy, and sales. Use when the user mentions "social proof", "persuasive copy", "why users dont convert", "ethical persuasion", "reciprocity", "scarcity tactics", or "commitment and consistency". Also trigger when designing testimonial sections, crafting urgency messaging, or improving trust signals on landing pages. For deal negotiation tactics, see negotiation. For viral word-of-mouth, see contagious.

wondelai/inspired-product

Build empowered product teams using discovery and delivery dual-track. Use when the user mentions "product discovery", "empowered teams", "feature factory", "product roadmap", "opportunity assessment", "product vision", "product-led growth", or "discovery vs delivery". Also trigger when restructuring product teams away from output-driven models, setting product strategy, or defining what to build next based on outcomes. Covers product discovery techniques, team structure, and continuous value delivery. For customer interviews, see mom-test. For ongoing discovery systems, see continuous-discovery.

wondelai/ios-hig-design

Design native iOS interfaces following Apple Human Interface Guidelines. Use when the user mentions "iPhone app", "iPad layout", "SwiftUI", "UIKit", "Dynamic Island", "safe areas", "HIG compliance", "SF Symbols", "haptic feedback", or "iOS accessibility". Also trigger when building tab bars, navigation stacks, sheets, or modals for iOS, implementing dark mode, or adapting layouts for different screen sizes. Covers navigation patterns, accessibility, SF Symbols, and platform conventions. For general UI polish, see refactoring-ui. For affordance design, see design-everyday-things.

wondelai/jobs-to-be-done

Discover what customers truly need by analyzing the "job" they hire your product to do. Use when the user mentions "customer discovery", "why customers churn", "what job does this solve", "competing against luck", "product-market fit", "switching behavior", "milkshake moment", or "functional vs emotional jobs". Also trigger when investigating why users choose competitors, designing features around real customer needs, or reframing product value propositions. Covers JTBD interviews, competition analysis, and jobs-oriented roadmaps. For product positioning, see obviously-awesome. For rapid validation, see design-sprint.

관련 스킬

steipete/sag

ElevenLabs text-to-speech with mac-style say UX.

community

steipete/oracle

Oracle CLI second-model review/debug/refactor/design with selected files, dry-run token checks, API or browser engine.

community

steipete/peekaboo

Capture and automate macOS UI with the Peekaboo CLI.

community

mattpocock/design-an-interface

Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".

community

mattpocock/prototype

Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.

community

mattpocock/grill-me

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

community