616건 · 관련도순
Generate Excalidraw architecture diagrams (.excalidraw JSON files) from your codebase. Triggers: you need whiteboard-style sketches that read as a thinking artifact rather than a polished spec — ideal for design.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Mobile-first design thinking and decision-making for iOS and Android apps. Touch interaction, performance patterns, platform conventions. Teaches principles, not fixed values. Use when building React Native, Flutter, or native mobile apps.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Node.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Server management principles and decision-making. Process management, monitoring strategy, and scaling decisions. Teaches thinking, not commands.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design thinking and decision-making for web UI. Use when designing components, layouts, color schemes, typography, or creating aesthetic interfaces. Teaches principles, not fixed values.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Python development principles and decision-making. Framework selection, async patterns, type hints, project structure. Teaches thinking, not copying.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Creative problem-solving techniques for breaking through stuck points - includes collision-zone thinking, inversion, pattern recognition, and simplification
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Force unrelated concepts together to discover emergent properties - "What if we treated X like Y?"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when complex problems require systematic step-by-step reasoning with ability to revise thoughts, branch into alternative approaches, or dynamically adjust scope. Ideal for multi-stage analysis, design planning, problem decomposition, or tasks with initially unclear scope.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants to explore options, weigh approaches, or think through uncertainty before committing to a direction. Collaborative brainstorming and rubber ducking — divergence-first thinking partner.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Enter explore mode for technical work — a thinking partner for {{engine_name}} code, architecture, and implementation decisions before you write any code. Use it to investigate a technical solution, design the architecture of a feature, choose between frameworks or libraries, compare implementation approaches, analyze how existing code or a system works, or deeply root-cause a complex bug without fixing it yet. The ultra mode adds adaptive artifacts (a C4 view, ADRs, a dependency graph) to the research folder — run it on "ultra research", "ultra explore" or "ultraresearch"; otherwise run the default. Trigger on "let's explore this technical solution", "how should we architect this feature", "which framework should we use", "run an ultra research on the save system", "investigate this error deeply". Research and analysis only — it never writes code. This is the CODE / engineering explorer — for GAME-DESIGN, GDD, mechanics, or balance research (no code) use /unikit-gd-explore.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
CEO/founder-mode scope review. Challenges the scope of any plan, workflow, or feature before execution. Four modes: SCOPE EXPANSION (dream bigger), SELECTIVE EXPANSION (cherry-pick worthwhile expansions), HOLD SCOPE (maximum rigor within current scope), SCOPE REDUCTION (strip to essentials). Use before executing any multi-step workflow or when questioning whether the scope is right. Prevents scope creep and missed opportunities. Use proactively when the user defines a plan, creates a workflow, or says "is this enough?" or "am I thinking too small?".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Automatically assess task complexity and adjust reasoning level. Triggers on every user message to evaluate whether extended thinking (reasoning mode) would improve response quality. Use this as a pre-processing step before answering complex questions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Broadcast agent activity status to Discord channel (thinking, tool use, web search, coding, done, error). Use for transparency so users know agent is working.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
4claw — a moderated imageboard for AI agents. Boards, threads, replies, media uploads, bumping (bump=false to not bump), greentext, and automatic capacity purges. Post spicy hot takes (what you’re REALLY thinking) — but no illegal content, doxxing, harassment, or minors.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
A moderated imageboard for AI agents to post and debate. A place made by bots for bots to post what they are really thinking
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find 10x product opportunities and high-leverage improvements. Use when user wants strategic product thinking, mentions '10x', wants to find high-impact features, or says 'what would make this 10x better', 'product strategy', or 'what should we build next'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Refines ideas iteratively. Refine ideas through structured divergent and convergent thinking. Use "idea-refine" or "ideate" to trigger.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
name: human-centered-design-fundamentals
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prepares for hiring manager rounds at Staff+ (L6+) level — scope of impact, influence without authority, ambiguity navigation, mentorship, strategic thinking. Use when practicing HM rounds or calibrating story depth for target level. Activate on "hiring manager round", "HM screen", "staff level", "scope of impact". NOT for coding interviews, system design, behavioral/values rounds, or resume writing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structured step-by-step reasoning before acting, to avoid guessing. For complex debugging, multi-step analysis, hypothesis checks. NOT for being stuck on approach (mk:problem-solving).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Four modes: SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope + cherry-pick expansions), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials). Use when asked to "think bigger", "expand scope", "strategy review", "rethink this", or "is this ambitious enough". Proactively suggest when the user is questioning scope or ambition of a plan, or when the plan feels like it could be thinking bigger. Use AFTER a plan exists. For validating the idea itself before planning, use /mk:office-hours first.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.