'analogy' 검색 결과

Use when a concept is too abstract for the learner's current level and needs analogy-first teaching before complexity re-injection.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Examine AI research directions and safety strategies through thinking models drawn from Ilya Sutskever’s public statements. The skill checks current facts when needed and presents a concise judgment with an everyday analogy.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assessing AI research directions
• Examining model scaling and data limits
• Discussing AI safety strategies

Analyze a problem by separating fundamental facts from policies and untested assumptions. The skill produces a component breakdown, a constraint table, and a rebuilt solution, helping explain which inherited assumptions may be limiting the available options.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Breaking down the causes of high costs
• Reviewing requirements inherited from past projects
• Reconsidering a design that has stalled

Develops mathematical understanding through examples, visualization, and analogy

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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", "pragmatist buyers", "growth stalled after early adopters", or "our go-to-market plan". Also trigger when planning go-to-market for a technical product. Covers the D-Day analogy, bowling-pin strategy, the tornado, and positioning against incumbents. For product positioning, see obviously-awesome. For new market creation, see blue-ocean-strategy.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Apply general knowledge reasoning across diverse domains — trivia, commonsense inference, analogy, and factual question answering.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Develops mathematical understanding through examples, visualization, and analogy

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Applies TRIZ cross-domain analogical reasoning to find solutions from adjacent fields. Use when stuck on a problem and needing inventive perspectives.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate a self-contained, beautifully styled HTML analysis of an academic paper. Use when the user provides an arXiv link, paper URL, PDF, or asks to analyze a research paper. Produces a standalone HTML file with structured sections (Problem, Translation/Analogy, Architecture, Key Results, Verdict), embedded figures, and responsive design. Trigger words include 读论文, 分析论文, paper analysis, paper review.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Break out of a locked problem frame by picking one disciplined move — reframe, provocation (Po), random stimulus, SCAMPER, inversion, structured analogy, constraint play, or family traversal — and committing to it before evaluating. Use when stuck, when options feel narrow or obvious, when iterations produce variations of the same idea, or when the user says "widen this", "break out of", "think differently", "I'm stuck", "feels too obvious", "stress-test the framing", "what am I missing", or holds two related examples and asks what lies between or beyond them. Complements challenging (which evaluates) and convening-experts (which synthesizes viewpoints); this skill generates distance, not judgment.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Explains code with WHAT, WHY, ANALOGY, DIAGRAM, CRUXES, and GOTCHAS. Use when you want to know how code works or when the user asks "how does this work?"

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Knowledge base from the GAO Cost Estimating and Assessment Guide (GAO-20-195G). Use for program cost estimating: the four characteristics of a reliable estimate (comprehensive, well documented, accurate, credible) and the 18 best practices; the 12-step cost estimating process (purpose, plan, technical baseline, WBS, ground rules and assumptions, data, point estimate, sensitivity, risk/uncertainty, document, present, update); estimating methods (analogy, parametric, engineering build-up, learning curves); Monte Carlo risk/uncertainty analysis, confidence levels and contingency; auditing and validating an estimate against the characteristics; earned value management (EIA-748, BCWS/BCWP/ACWP, CPI/SPI/TCPI, EAC, PMB, IBR); and specialized techniques (software cost estimating, learning curves, Analysis of Alternatives, WBS templates, the Green Book internal-control framework). This is the cost-estimating companion to the GAO Schedule and Technology Readiness Assessment guides. Does not cover schedule estimating/risk in depth (see the GAO Schedule Assessment Guide), agency-specific cost models, or the full text of referenced standards (EIA-748, MIL-STD-881D, the Green Book) — these are named, not reproduced.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Knowledge base from the NASA Cost Estimating Handbook (CEH) v4.0. Use for NASA's 12-step, three-part cost estimating process (Project Definition, Cost Methodology, Cost Estimate); the WBS, CADRe, and ONCE data backbone; estimating methodologies (analogy, parametric/CER, engineering build-up, EVM, Delphi); ground rules and assumptions, data normalization and inflation (BY/CY/RY); the point-estimate-to-S-curve cost-risk chain and Unallocated Future Expense (UFE) reserves; Joint Cost and Schedule Confidence Level (JCL) analysis via probabilistic cost-loaded schedules; decision-support analyses (sensitivity, trade studies, make/lease-vs-buy, affordability, CAIV); and economic analysis (discounting, NPV, OMB Circular A-94). The cost-estimating complement to NASA's SE and risk packs. Does NOT reproduce the handbook's tool-specific procedures, worked examples, or appendix-depth methods (it names the appendices), nor cover full DoD/GAO cost guides, schedule construction, or formal risk management beyond the cost interface.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze yesterday's prompts to surface one technical concept worth understanding, delivered as a concise morning lesson with everyday analogy + engineer vocabulary. Use when "morning lesson", "prompt mirror", "today's learning", "what should I learn", or via scheduled automation each morning.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Strip a problem to its irreducible fundamental truths and rebuild the solution from the ground up — free from analogy, convention, and inherited assumptions. Load when the user feels constrained by how something has always been done, when existing solutions feel expensive or inefficient for no good reason, when the user asks to think from first principles, challenge the fundamentals, or rebuild this from scratch. Also triggers on "why does it have to work this way", "what are the actual constraints here", "ignore what everyone else does", or when deep-thinking diagnoses a convention-break frame. Based on Aristotle's first principles method, popularised by Musk and Feynman. Produces genuinely novel solutions by eliminating convention.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Explain a complex concept through a short allegory, story, analogy, metaphor, or intuitive teaching example, then map it back to formal concepts and limits; do not use as the primary skill for implementation, specs, source-cited API guidance, or fiction-only writing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.