「how complex」の検索結果

Generate a comprehensive marketing website for a web app — multi-page with real screenshots, animated GIF walkthroughs, feature deep-dives, and workflow demonstrations. Browses the running app, captures screens and sequences, and produces a deployable site that actually teaches people what the product does. Especially useful for complex or agentic apps that are hard to explain. Triggers: 'showcase site', 'product page', 'show off the app', 'marketing site', 'demo site', 'product showcase', 'explain the app', 'how do I market this'.

日本語の概要は準備中です。原文の説明を表示しています。

Quickly understand an unfamiliar codebase or project by mapping its architecture, identifying key components and data flows, and surfacing complexity hotspots. Load when the user asks to understand a repo, explain how something works, map the architecture, onboard to a codebase, or explore how components connect. Also triggers on "walk me through this codebase", "how does this project work", "explain the architecture", "what does this repo do", "show me the structure", "onboard me", or any request to build a mental model of a codebase before making changes.

日本語の概要は準備中です。原文の説明を表示しています。

Socratic mentoring for junior developers and AI newcomers. Guides through questions, never answers. Triggers: "help me understand", "explain this code", "I'm stuck", "Im stuck", "I'm confused", "Im confused", "I don't understand", "I dont understand", "can you teach me", "teach me", "mentor me", "guide me", "what does this error mean", "why doesn't this work", "why does not this work", "I'm a beginner", "Im a beginner", "I'm learning", "Im learning", "I'm new to this", "Im new to this", "walk me through", "how does this work", "what's wrong with my code", "what's wrong", "can you break this down", "ELI5", "step by step", "where do I start", "what am I missing", "newbie here", "junior dev", "first time using", "how do I", "what is", "is this right", "not sure", "need help", "struggling", "show me", "help me debug", "best practice", "too complex", "overwhelmed", "lost", "debug this", "/socratic", "/hint", "/concept", "/pseudocode". Progressive clue systems, teaching techniques, and success metrics.

日本語の概要は準備中です。原文の説明を表示しています。

World-class explainer video expertise combining the visual storytelling of Kurzgesagt, the simplification genius of Common Craft, and the conversion science of high-performing SaaS landing pages. Explainer videos transform complex ideas into clear, compelling stories. Great explainers don't just inform—they illuminate. They take abstract concepts and make them feel obvious. The best explainer videos understand that simplicity is the ultimate sophistication, that showing beats telling, and that the goal isn't to impress with complexity—it's to make the viewer feel smart. Use when "explainer, explainer video, how it works, product demo, onboarding video, training video, educational video, whiteboard, animated explainer, explain this, simplify, concept video, SaaS video, explainer, video, animation, educational, product, demo, onboarding, SaaS" mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Teaches you how to break large tasks into stages, save your place between sessions, and recover smoothly when a task gets interrupted. Use when planning a multi-day project, for breaking down large work into manageable stages, during recovery from an interrupted session, when managing complex ongoing work, or when the user says "cowork stopped in the middle", "token limit", "task too large", "context management", "how to do big tasks", "session got cut off", "cowork forgot what we were doing", "how do I work on something over multiple days", "it lost track of the project", or "my task is too big for one session".

日本語の概要は準備中です。原文の説明を表示しています。

Coordinate structured thinking and multi-agent parallel execution for complex tasks. Use when tackling multi-step projects, planning parallel work, breaking down complex problems, coordinating specialist tasks, facing architectural decisions, or when user mentions "workflow", "orchestration", "multi-step", "coordinate", "parallel execution", "structured thinking", "break this down", "plan this out", "how should I approach", or needs help planning complex implementations.

日本語の概要は準備中です。原文の説明を表示しています。

Analyzes ticket complexity and maps dependencies against an existing codebase before sprint planning. Triggers on 'how complex is this ticket', 'what should we work on first', 'can we fit this in the sprint', 'tech review before planning', 'plan the sprint'. NOT for writing implementation plans (see mk:plan-creator); NOT for scope/ambition review (see mk:plan-ceo-review).

日本語の概要は準備中です。原文の説明を表示しています。

Decompose tasks into structured, outcome-defined process entries with complexity triage. Load when user says "decompose this", "break this down", "what steps do I need", "plan this out", "what's the process for", "how do I approach this", or when any complex task needs structured execution planning. Includes a problem-understanding pass before complexity triage. Routes to `problem-to-plan` when the user needs planning deliverables (spec + plan + TODO). Does NOT replace brainstorming — brainstorming is design approval (upstream), this is execution planning (downstream).

日本語の概要は準備中です。原文の説明を表示しています。

Socratic mentoring for junior developers and AI newcomers. Guides through questions, never answers. Triggers: "help me understand", "explain this code", "I'm stuck", "Im stuck", "I'm confused", "Im confused", "I don't understand", "I dont understand", "can you teach me", "teach me", "mentor me", "guide me", "what does this error mean", "why doesn't this work", "why does not this work", "I'm a beginner", "Im a beginner", "I'm learning", "Im learning", "I'm new to this", "Im new to this", "walk me through", "how does this work", "what's wrong with my code", "what's wrong", "can you break this down", "ELI5", "step by step", "where do I start", "what am I missing", "newbie here", "junior dev", "first time using", "how do I", "what is", "is this right", "not sure", "need help", "struggling", "show me", "help me debug", "best practice", "too complex", "overwhelmed", "lost", "debug this", "/socratic", "/hint", "/concept", "/pseudocode". Progressive clue systems, teaching techniques, and success metrics.

日本語の概要は準備中です。原文の説明を表示しています。

Use when creating an approachable, self-contained HTML review aid for a pull request; explaining what changed, why it matters, how it works, and how it fits into the broader system; turning PR diffs, commits, tests, and architecture context into a local `.pr-review/` HTML page for reviewers; or helping reviewers understand complex code changes without dumping the full diff.

日本語の概要は準備中です。原文の説明を表示しています。

Token-efficient code analysis via 5-layer stack (AST, Call Graph, CFG, DFG, PDG). 95% token savings.

日本語の概要は準備中です。原文の説明を表示しています。

Cross-functional what-if modeling for compound adversity -- shows how one problem cascades into the next. Use when facing complex risk scenarios, strategic decisions with major downside, or multi-variable threats.

日本語の概要は準備中です。原文の説明を表示しています。

Token-efficient code analysis via 5-layer stack (AST, Call Graph, CFG, DFG, PDG). 95% token savings.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Estimate the full development cost of an existing codebase from lines of code, architectural complexity, and team-composition overhead. Use for 'how much would this cost to build', 'what did this codebase cost', development-cost or build-cost estimates, calendar-time estimates, and Claude/AI ROI on a delivered codebase. Estimates by measured LOC and complexity, not by ticket volume.

日本語の概要は準備中です。原文の説明を表示しています。

Heuristic story-point estimation for a single Jira ticket via the jira-estimator agent. Read-only. Triggers: 'estimate KEY', 'story points for KEY', 'how complex is KEY'. NOT for complexity-only analysis (mk:jira-evaluator); NOT for full RCA (mk:jira-analyst).

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill for ANY of the following — do not skip it even if the query seems simple: strategic decisions, business analysis, thesis building, complex problem solving, geopolitical analysis (non-market), philosophical reasoning, academic research, system design, decision under uncertainty, long-form thinking, or any question that benefits from First Principle deconstruction and multi-agent reasoning. ALWAYS use this skill when the user asks about: why something works the way it does, whether a decision is correct, how to think about a complex problem, what could go wrong, analyzing a situation from multiple angles, or any "should I..." question involving real-world trade-offs. This is NOT a market/trading skill — for financial markets, BTC, gold, stocks, forex, macro economics, use money-atlas-intelligence-os instead.

日本語の概要は準備中です。原文の説明を表示しています。

Apply the four published expert-consensus clinical scenarios to manage GI adverse events in complex GLP-1 receptor agonist patients — persistent nausea mid-titration, GERD/heartburn after up-titration, elderly with sarcopenia risk, and insulin-treated elderly with CKD plus diarrhoea. Use when a clinician describes a patient resembling one of these archetypes, or asks "how to manage GLP-1 in an elderly patient with CKD", "patient on liraglutide developed reflux", "sarcopenia worry on semaglutide in 80-year-old", or "persistent nausea on semaglutide despite escalation". Grounded in Gorgojo-Martínez 2023 Table 4.

日本語の概要は準備中です。原文の説明を表示しています。

Add or define specific fields in a collection's readSchema. Use when fields are missing from materialization field selection, pruned by complexity limit, need type refinement, need to be protected from future inference changes, or need to be required for downstream consumers. Use when user says "missing fields", "pruned fields", "field not showing up", "complexity limit", "define field in read schema", "restrict field type", or "protect field from inference".

日本語の概要は準備中です。原文の説明を表示しています。

Design state-of-the-art multi-agent systems, orchestration patterns, and wiring from scratch. Load when the user asks to build an agent system from scratch, design agent orchestration patterns, choose between sequential/parallel/hierarchical workflows, or define how multiple agents should collaborate. Also triggers on "agent architecture", "multi-agent wiring", "agent orchestration pattern", "how to connect these agents", "design the communication structure". Called by agent-builder for complex topologies (>4 agents or hierarchical). For process-driven agent design, use agent-builder instead.

日本語の概要は準備中です。原文の説明を表示しています。

[00] META. Orchestrate skills into dynamic chains for complex tasks. Analyzes the task, discovers available skills, builds an optimal chain, explains why each skill is needed, and executes step-by-step with user confirmation. Use for any complex task requiring multiple thinking/research/analysis steps. Triggers on "plan this", "how to approach", "what's the strategy", "build a plan", or any multi-step problem requiring skill orchestration.

日本語の概要は準備中です。原文の説明を表示しています。

Tracks complex, multi-session work using the Beads issue tracker and dependency graphs, and provides persistent memory that survives conversation compaction. Use when work spans multiple sessions, has complex dependencies, or needs persistent context across compaction cycles. Trigger with phrases like "create task for", "what's ready to work on", "show task", "track this work", "what's blocking", or "update status".

日本語の概要は準備中です。原文の説明を表示しています。

Calculates sample sizes and statistical power for study planning. Applies when someone asks "how many subjects/samples/replicates do I need", wants an a priori power analysis, a minimum detectable effect (MDE), a power curve, or needs to justify a sample size for a grant, IRB protocol, or pre-registration. Covers closed-form power for t-tests, ANOVA, proportions, correlations, chi-square, and regression, plus simulation-based (Monte Carlo) power for complex designs — logistic/Poisson regression, mixed models, cluster-randomized trials, survival, and interactions. Also handles requests that only mention an effect size, alpha, or "80% power" without saying "power analysis" explicitly. For laying out the study (randomization, blocking, factorial/DOE, crossover, sequential designs) use experimental-design; for analyzing data already collected and reporting it use statistical-analysis.

日本語の概要は準備中です。原文の説明を表示しています。

Design a multi-stage OpenMAIC course series around a small concept spine whose ideas return repeatedly at higher levels of complexity, abstraction, relationship density, representation, transfer distance, or boundary awareness. Use when the user explicitly wants a Bruner-style spiral curriculum, progressive conceptual revisits, or a series organized by how understanding develops rather than by a linear topic list. Do not use for a single standalone stage or a series that only needs sequential coverage.

日本語の概要は準備中です。原文の説明を表示しています。