685건 · 관련도순
Use for creative thinking, or when the user wants many fresh options before choosing: "give me ideas", "brainstorm names", "other ways to do this", "think outside the box". Diverges first, then picks. Skip when one answer is wanted or the task is pure execution.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for lateral thinking, or when ideas feel stuck or incremental: "we've tried everything", "need a surprising angle", "break the pattern", "give me a wild idea that could work". Uses provocations and reframes. Skip for rule lookups or strict logical proofs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Used by the Lead agent during Phase 6 (Brainstorm) to collaboratively explore user intent, requirements, and alternative approaches before locking in the architecture. Helps turn raw ideas into fully formed specs through natural dialogue.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate creative domain name ideas for your project and check availability across multiple TLDs (.com, .io, .dev, .ai, .app). Find the perfect domain name without manual checking.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Help entrepreneurs identify and evaluate communities for a minimalist business. Use when someone is exploring business ideas, seeking their target community, or determining where to start.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert landscape designer transforming yards through photo mapping, 3D visualization, seasonal planning, and deep plant knowledge. Specializes in fast-growing privacy screens (knows arborvitae pitfalls), architecture-appropriate design, outdoor living spaces, and realistic maintenance expectations. Activate on "landscape design", "yard design", "garden planning", "plant selection", "privacy screen", "outdoor living", "backyard makeover", "arborvitae", "hedge", "fast growing tree", "landscaping ideas". NOT for interior design (use interior-design-expert), hardscape construction (consult contractors), or lawn care chemicals (consult local experts).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
### 1. The Fault/Error/Failure Hierarchy NOT for unrelated tasks outside this domain.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
How to design contextual inputs for an always-on AI agent with episodic memory. Covers what data to feed the agent, how to structure observations and triggers, ambient context capture (screen, audio, calendar), context window budgeting, and retrieval strategies that keep the agent grounded in what's actually happening. Activate on: "what should the agent observe", "context inputs for agent", "ambient context capture", "agent triggers", "agent input design", "screenpipe integration", "context window budget", "what data to feed my agent", "/always-on-agent-inputs". NOT for: memory architecture and storage (use always-on-agent-architecture), application ideas (use always-on-agent-applications), safety concerns (use always-on-agent-safety).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Segments the genome into chromatin states from combinatorial histone modification and chromatin factor ChIP-seq data. Uses ChromHMM (multivariate HMM on binarized signal, v1.27), Segway (Dynamic Bayesian Network on continuous signal), EpiSegMix (flexible-distribution HMM with duration modeling, 2024), EpiLogos (multi-biosample visualization), IDEAS (cell-type-aware joint), and full-stack ChromHMM (Vu Ernst 2022) for cross-cell-type segmentations. Handles state-count selection (15 vs 18 vs 25 states), binarization choice, OverlapEnrichment / NeighborhoodEnrichment downstream analysis, and cross-biosample integration. Use when learning chromatin states from a histone mark panel, characterizing learned states by genomic feature enrichment, or comparing chromatin landscapes across cell types.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Autonomously improve a real artifact (code, training recipe, agent harness, data pipeline, prompt) against an objective and an evaluator, using Hypothesis Tree Refinement (HTR) from the Arbor paper. Use this whenever someone wants to iteratively optimize something over many experiments without overfitting — e.g. "get my model's eval score up", "improve this agent/harness", "tune this pipeline", "beat the baseline on this benchmark", "run a search over approaches and keep the best", "do an MLE-bench / Kaggle-style optimization", or any long-horizon "make this artifact better and don't just memorize the dev set" task. Trigger it even when the user doesn't say "Arbor" or "hypothesis tree" but describes repeated experiment-and-evaluate loops, branching exploration of competing ideas, or worries about a dev/test gap. Runs Claude itself as the coordinator with subagent executors in isolated git worktrees; for the standalone `arbor` CLI tool see references/arbor-upstream.md.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when copy-catting, replicating, or adapting features from external systems, repos, apps, or ideas into the current project. Triggers on 'copy this from', 'replicate', 'clone this feature', 'how does X do Y', 'chom', 'like how X does it', 'port from', 'build like', '1:1 copy'. NOT for packing the current project (see mk:pack); NOT for one-shot URL-to-markdown fetches (see mk:web-to-markdown).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrator for the Product Design skill set — turn early ideas into reviewable prototypes. Routes to the right sub-skill (get-context, research, audit, ideate, image-to-code, url-to-code, prototype, qa, share) based on where you are in the design process. Use when the user gives a high-level design goal like "design a UI for X", "prototype this idea", "rebuild this screen", "review our flow", or isn't sure which design step they need. Delegates to design-* skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Adversarial dialectic tool inspired by GAN. Alternates between Generator (creative advocate) and Discriminator (adversarial critic). Supports forced role selection (g/d), intensity modes (hard/soft), and multi-language output. Use for stress-testing ideas, business plans, code, and spec designs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Enter explore mode - think through ideas, investigate problems, clarify requirements
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Grilling session that mines the user for fragments — heterogeneous nuggets of writing (claims, vignettes, sharp sentences, half-thoughts) — and appends them to a single document as raw material for a future article. Use when the user wants to develop ideas before imposing structure, or mentions "fragments", "ideate", or "raw material" for writing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate project ideas via creative constraints.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Marc Andreessen-mode decision and productivity skill. A blunt, market-first operator that pressure-tests ideas, ventures, features, and career bets through Andreessen's actual frameworks — market dominates team and product; the only milestone that matters is product/market fit; bias to build over deliberate. Use when the user says 'andreessen', 'pmarca mode', 'should I build this', 'is there a market', 'are we at product/market fit', 'pmf check', 'pressure-test this idea', 'be brutal about this venture', 'market-first take', or wants a no-disclaimers, no-hedging, confidence-leveled verdict on whether something is worth pursuing. Also provides the 3x5-card + Anti-Todo personal productivity routine. Runs on a fixed anti-sycophancy operating prompt: leads with the strongest counterargument, never validates premises, uses explicit confidence levels, never apologizes for disagreeing. Not for polite brainstorming — this skill exists to tell you the market is dead when it is.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Transform rough ideas into solid designs through structured questioning
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Stress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written. TRIGGER when: the user has a fuzzy feature idea — one or two paragraphs, vague on users / scope / success — and wants to harden it, or says "grill / stress-test / pressure-test this idea." DO NOT TRIGGER when: the idea is already turned into a spec or PRD; bug fixes or refactors; the idea is hardened and you are ready to write the PRD → creating-prd.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Synthesises the current conversation context into a Product Requirements Document and publishes it to GitHub (as a comment on a referenced issue, or a new issue). Synthesises from context; does not interview. TRIGGER when: the conversation has produced enough understanding of a feature and the user wants it captured as a PRD. DO NOT TRIGGER when: a single small issue is enough → creating-issues; the idea has not been stress-tested yet → grilling-ideas first; bug reports.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turns a single feature idea, improvement, or bug into ONE well-structured GitHub issue. TRIGGER when: the user wants to file/open/create an issue, turn a feature idea or improvement into a ticket, or capture something missing or broken as a ticket. DO NOT TRIGGER when: breaking work into multiple issues or planning a body of work → a planning skill; writing a full Product Requirements Document → creating-prd; the idea is still fuzzy and unhardened → grilling-ideas first.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.