247건 · 관련도순
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Work on C# and .NET-adjacent mixed-reality solutions around HoloLens, MRTK, OpenXR, Azure services, and integration boundaries where .NET participates in the stack. USE FOR: building or integrating mixed-reality solutions with C#; working on HoloLens, MRTK, Azure mixed-reality services, or OpenXR-related code; reviewing how .NET services. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply a UX lens to a user-facing change: whether it serves the user's real goal and whether the path through it holds together, using the Understanding, Bridging, and Flowing contexts. Use when scoping, planning, or assessing any change that affects what a user sees or does. Loaded as a lens during planning and assessment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Think and work like an expert Laser Physicist. Use when a task calls for Laser Physicist judgment. Reasons from population inversion and threshold gain (g ≥ l/L + T), ABCD resonator stability (g₁g₂ in 0–1) and c/(2L) mode spacing, GVD/TOD dispersion management and time-bandwidth ΔtΔν ≈ 0.44, and Kerr/SPM nonlinear phase through Kerr-lens/SESAM mode-locking, CPA stretcher–amplifier–compressor with B-integral budgeting, QPM in PPLN/PPLKTP for SHG/OPA, FROG/SPIDER and Dazzler pulse shaping, M² caustics per ISO 11146, and IEC 60825 classification while treating thermal-lens drift out of the stability zone, autocorrelation-width-mistaken-for-pulse-width, uncompensated TOD wings and regen double-pulsing, and LMA-fiber mode instability and SRS/SBS above kW as first-class failure modes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when one reviewer is not enough because failure modes are heterogeneous, or a claim needs cross-lens pressure before it ships. Not for collapsing a decision field: use converge.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Invoke only when the user explicitly asks to review code through the "single level of abstraction / layered error handling" lens — a function does only its own layer's business logic while errors are handled above or below. The agent reports detections, raw-count measurements, and move directions. Apply only when the user explicitly requests this lens.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when deciding whether Salesforce Reports, CRM Analytics, or Tableau is the right level of analytics tooling, and when reviewing or troubleshooting basic CRM Analytics designs. Triggers: 'CRM Analytics', 'Einstein Analytics', 'Tableau CRM', 'lens', 'dataset', 'dataflow', 'analytics dashboard', 'license requirement'. NOT for a detailed CRM Analytics vs Tableau licensing and platform comparison — use architect/crm-analytics-vs-tableau-decision. NOT for building the app, lenses and datasets — use admin/crm-analytics-app-creation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill to define, document, and validate KPI metrics for CRM Analytics — covering metric formula design, dimension selection, target-dataset modeling, benchmark setting, and the KPI register that must exist before any dashboard or lens is built. Trigger keywords: KPI definition CRM Analytics, analytics metric design, analytics target attainment, CRM Analytics measures vs dimensions, analytics benchmark. NOT for laying out the dashboard or lens itself — use admin/analytics-dashboard-design. NOT for scoping data sources, audiences, and drill-down paths — use admin/analytics-requirements-gathering.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run before building anything new — a pre-build gate that decides whether an idea deserves its own tool, judged from both the agent lens (legible, drivable, automatable) and the human lens (will I touch it, do I want to maintain it). Trigger on "should I build X", "starting a new project / app / tool / repo", "is this worth making", "want to spin up", or any new-build intent — even if the word "checklist" never appears. Outputs a backed GATE.md with checkmarks and a one-line verdict note in the project root docs. Do NOT load for small config tweaks, one-off scripts, bug fixes on existing things, or anything that is clearly a feature of something you already run.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run on an existing project to decide KEEP / MERGE / ARCHIVE — never limbo. Forces a call on tools that already exist and may have stopped earning their keep. Trigger on "is this still worth keeping", "audit this repo", "tech-debt cleanup", "sweep the folder", "what's dead here", or any signal that something hasn't been touched in months. Judged from both the agent lens (still legible, still drivable, still safe) and the human lens (do I still reach for it, does it nag). Includes a non-negotiable footgun check for stale pipelines that can overwrite live data. Outputs a backed AUDIT.md and a one-line verdict note in the project root docs. Do NOT load for greenfield projects (use new-project-gate), one-off bug fixes, or when the answer is already obvious.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Draws an interactive HTML Architecture Viewer for any code flow the user names. Walks through seven research-driven steps (flow, name, repo research, lens colors, evidence flags, lens+mechanism per stop, build) and verifies links, claims, and generated artifacts before delivery.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Research and stress-test open-source project names, from collision checks to launch-ready decisions. Use when the user asks to name or rename a project, compare candidate names, screen GitHub or package namespace risk, verify language or mythology claims, or improve SEO/GEO clarity. Perform live web and registry research, separate brand from category descriptor, classify collisions, and return one evidence-backed recommendation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Claude Code の過去セッション（transcript JSONL）・設定・運用パターンを cclens と同梱スクリプトで収集し、指定された分析観点に沿って傾向分析と改善案を出す。/session-insights で明示起動されたときのみ使用する。キーワードマッチによる自動起動はしない。起動時に分析観点の指定が必須。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Provides guidance for training and analyzing Sparse Autoencoders (SAEs) using SAELens to decompose neural network activations into interpretable features. Use when discovering interpretable features, analyzing superposition, or studying monosemantic representations in language models.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Navigate and understand codebases using agentlens hierarchical documentation. Use when exploring new projects, finding modules, locating symbols in large files, finding TODOs/warnings, or understanding code structure.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
개발 전에 제품의 목적을 검토하고 추진 여부, 첫 사용의 장애물, 기능 우선순위를 정리합니다. 근거와 다음 행동을 담은 기획서나 로드맵을 작성합니다.
제공한 HTML과 텍스트, 데이터를 iPhone과 MacBook 화면에 배치합니다. 유리 느낌의 하이라이트와 바닥 반사를 더해 입체적인 제품 소개 페이지를 만듭니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Read a book, article, transcript, or case study against a specific strategic problem. The skill turns relevant passages into practical actions, countermeasures, and warning signs, with source evidence and recommendations for the short, medium, and long term.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Reviews code changes through documented engineering and product principles associated with named practitioners. Combines two engineering perspectives and one product perspective to produce findings with severity, attribution confidence, and technical reasoning for architecture, performance, or user experience issues.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.