57건 · 관련도순
Apply 12 structured investing frameworks to evidence already collected. Each framework orders the questions to ask, defines reasons to reject a case, and identifies its limitations, helping explain why different approaches reach different conclusions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review code changes or documents through configured review lenses, each representing a different perspective. Findings identify the location, triggering condition, suggested fix, and potential consequence, with reports available as JSON, Markdown, or both.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Research a company, industry, or competitor group through web search and seven analytical lenses. Produce structured, cited findings on business models, products, competition, and strategic signals for product decisions and further analysis.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Run a structural-review debate between two lenses — lowy (volatility-based decomposition) and hickey (structural simplicity) — on the current diff. Each reviews independently, then they cross-examine every finding until they agree per-finding, and the agreed fixes are applied. Use when the user types `/lens-debate`, or asks to "have lowy and hickey review this", "run the lens debate", "debate this diff structurally", or "argue the structure of this PR until the lenses agree".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when creating or configuring a CRM Analytics (Einstein Analytics) app — including app containers, lenses, datasets, data source connections, app sharing, and the row-level security that gates whether users see any data. NOT for choosing Reports vs CRM Analytics vs Tableau — use admin/einstein-analytics-basics. NOT for security predicate syntax, sharing inheritance or Analytics license assignment — use admin/analytics-permission-and-sharing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Qualitative quality review of game design documents — answers "is this design good, and does it follow best practices?" — across all three GDD axes: systems, flows, and content types. Fans out adversarial lenses (completeness, clarity, pillar alignment, systems-math, fantasy-delivery, feasibility, scope) plus domain lenses that check it against the game-design rules, each prompted to find problems rather than validate; produces a severity-graded verdict and a two-bucket report (apply-ready fixes vs research), handed to /unikit-gd-apply or /unikit-gd-explore in one move. Scope is inferred: a named system, flow, or content type reviews that document; "all" runs a cross-document review. Use when the user wants a critique, quality judgment, or rules check of the design, e.g. "review the combat GDD", "review the onboarding flow". This is the subjective quality pass — for a mechanical consistency check (numbers, terms, IDs, references matching the registry) use /unikit-gd-verify.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Research private companies through six perspectives, including business, finances, competition, and technology. Cross-check evidence, separate facts from inferences, and produce a valuation range, possible exit routes, and a map of missing information.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review contracts, investment terms, and employment arrangements through six legal lenses. Identify key risks, organize negotiation priorities, and prepare specific questions for outside counsel before making commitments.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Compare direct and partner-led sales using full service costs and three views of return on investment. Produce channel verdicts and a recommended sales mix, testing how changes in acquisition costs or partner discounts affect the result.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review an existing requirements document, plan, or specification from several role-based perspectives. Identify inconsistencies and obstacles to carrying out the work, verify their consequences, apply authorized corrections, and present improvements or decisions that still need attention.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Performs a full AWS Well-Architected Framework review evaluating every framework question across all pillars discovered from the live AWS documentation by analyzing code, IaC, and configurations to produce evidence-backed findings with Eisenhower-prioritized remediation. Supports full reviews (every framework best practice with BP ID citations), quick reviews (question-level), pillar-scoped reviews, score-mode reviews (a maturity scorecard with per-pillar scores and filtered findings), and lens-specific reviews using lenses discovered from the live AWS documentation. Triggers on mentions of Well-Architected review, WA review, WAR, pillar assessment, architecture review across pillars, workload assessment, cloud readiness evaluation, or a Well-Architected score, grade, or scorecard request. Does not apply to single-pillar deep-dives, learning WA concepts, ADRs, or migration readiness assessments.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Capture a user's real writing voice from 5-20 prior samples, store a local voice.yaml fingerprint, and enforce it on newsjack drafts so AI tells disappear. Measures voice with named stylometry lenses (Burrows's Delta function-word vector, MATTR lexical diversity, sentence-length burstiness, Biber Dimension-1 register, opener-POS profile, punctuation rates) and gates drafts against the fingerprint as bands, not vibes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn a company update into 3-7 structurally distinct, journalist-shaped story angles. Runs the fact through proven newsroom lenses (perspective, abstraction, news values, data, contrarian, news peg) and refuses rephrasings, invented facts, named-journalist guesses, and AI-marketing slop.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Triage inbound journalist source queries and draft a response only when the user's expertise is a real fit. Runs each query through proven source-request lenses (4-gate fit triage, credential-standing test, deadline read, BLUF/inverted-pyramid drafting), kills weak fits, asks for missing proof, and never auto-sends.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Minimalist UX/Interaction Audit Expert that deconstructs complex interactions through cognitive load and operational efficiency lenses. Use this skill when you need to perform a UX walkthrough audit on a Figma prototype or web interface, evaluating usability based on principles like fewer clicks, less UI elements, no hidden logic, and self-explanatory design.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Wilkinson, branchline, ratrace, directional couplers, corporate dividers, Rotman lenses for power splitting and beam-forming. TRIGGER: user asks to design, create, or analyze any coupler, splitter, power divider, combiner, or Rotman lens. Invoke BEFORE writing code — class names and design() availability vary per coupler type. SKIP: EM simulation/S-parameter extraction of an existing component (use matlab-analyze-em), building custom non-catalog geometry (use matlab-assemble-pcb-layout), material/stackup setup only (use matlab-manage-pcb-material), cascading multiple components (use matlab-integrate-pcb-circuit).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when making a trailer, cutscene, cinematic or short film in Unreal Engine 5.8 with Sequencer: shot lists, master and shot sequences, cameras, lenses, depth of field, camera cuts, spawnables, character animation in shots, per-shot lighting, Movie Render Graph or Movie Render Queue EXR renders, "render darker than the viewport", "first frames pop", "last frame missing", ACES or OCIO to DaVinci Resolve, the 180-degree rule, Sequencer Python, or reviewing a cut.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Anchor a multidisciplinary unit in a real-world phenomenon that requires multiple subject lenses to understand. Use when designing integrated or phenomenon-based units across disciplines.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Provides multi-school trading Q&A, chart/OHLCV analysis, annotation, and fresh-market workflows covering ICT/SMC, ChanLun, Wyckoff, Price Action, Order Flow, VSA, and Elliott Wave. Use for trading concepts; capability-discovery questions about available analysis lenses, Schools, models, modes, or data sources; attached charts; pasted OHLCV; chart annotation; or asset-plus-timeframe requests across crypto, stocks, or forex. Defaults unselected market analysis to strict ICT/SMC, honors explicit School/source selectors, and fails closed when no native analyzer exists. Phase 1 comparison is Q&A-only; fetch fresh Mobius Quant API data only after the capability gate.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Running a team of subagents on one design build: clone briefs, disjoint file ownership, isolated builds, the evidence packet, review lenses, the fix plan, verdicts, cold eyes and the stop rule, with the workflow templates bunshin runs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Adversarially review something just built — presume it is broken and find where. Use after implementing a feature, finishing a build, or before shipping, or whenever ATLAS or Boss wants a hostile second opinion on a diff, a running app, or a whole codebase. Spawns clean-context reviewers with opposing lenses (correctness, security, empty-world) and reproduces every finding by running the target before believing it. Distinct from /code-review, which statically reads a diff and never runs the app.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Cinematic camera work in Blender including framing, lenses, composition, camera animation, and shot language beyond basic rendering setup via MCP.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when someone has a business problem, strategic question, or founder challenge they need to think through clearly. Triggers on "I'm stuck on", "should I", "what's wrong with my", "diagnose", "strategy problem", "business problem", "founder problem", "help me think through". Runs structured consulting-style diagnostic lenses to produce a comprehensive analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Recover and review local human-AI conversations from Claude Code, Codex, opencode, Grok Build, and Cursor. Use when the user wants to revisit, search, extract, summarize, or compare work across Agent session stores, time ranges, projects, or named conversations. Follow the user's requested output; question clustering, problem-space mapping, artifact review, drift analysis, and insights are optional lenses.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.