'rspec' 검색 결과

This skill enables cross-model dialogue between Claude and Gemini with shared visual memory. Use when the user wants to generate images, have visual dialogues with AI, create scientific illustrations with continuity, or have multiple AI perspectives respond to the same prompt. Key trigger phrases: "generate an image", "visual dialogue", "ask the daimones", "resonance field", "Minoan tarot", "cross-model", "KV cache", "MESSAGE TO NEXT FRAME".

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

Evaluate design from a UX perspective with Nielsen's heuristics scoring, anti-pattern detection, persona-based testing, and actionable feedback. Report-only. Triggers on critique, UX review, design feedback, how does this look, evaluate the design, component review.

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

Generate physically-based atmospheric scattering shaders — sky domes, planetary atmospheres, LUT-optimized pipelines, depth-aware post-processing. Four modes — sky-dome, atmosphere-post, planet, lut. Triggers on atmospheric scattering, sky shader, sunset rendering, planet atmosphere, Rayleigh scattering, Mie scattering, volumetric sky, sky dome, atmosphere post-processing, aerial perspective, transmittance LUT, sky rendering, realistic sky, planetary rendering.

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

Use when an answer is wanted from one named seat only: breaking, business, career, codebase, human, impact, innovation, moat, rent-seeking, skeptic, or stability. Not for multi-lens synthesis: use prism. Not for rebuilding from primitives: use from-first-principle.

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

Use when the user asks for a code review by a fleet of specialized reviewer agents, wants multiple independent reviewer perspectives, or asks to run reviewers in single-pass or iterative fix-until-clean mode. Launches focused subagents for correctness, security, architecture, conventions, simplicity, UX, reliability, telemetry, testing, compatibility, and documentation review.

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

Route NowStack Mobile UI work to the right design/build skill while enforcing a clear, user-first UX bar. Use for any "build/design/redesign/polish the UI" request on the mobile app, web app, landing, or admin — when the surface or the right skill is underspecified.

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

Routes general Convex requests to the right project skill. Use when the user asks which Convex skill to use or gives an underspecified Convex app task.

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

Route NowStack Mobile Convex work to the right skill. Use for underspecified Convex backend, schema, auth, migration, performance, component, or env tasks.

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

当用户需要将产品/服务/个人的特点转化为对受众有吸引力的利益点时调用。 适用于：写产品文案不知从何下笔、准备销售话术、撰写简历或自我介绍、 做产品定位思考。核心信号：用户在列举产品特点但不清楚"别人为什么要在乎"。 不适用于：纯技术文档、产品规格说明（此时特色本身就是目的）。

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

Multi-agent orchestration patterns. Use when multiple independent tasks can run with different domain expertise or when comprehensive analysis requires multiple perspectives.

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

Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.

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

X/Twitter public sentiment research. Searches X for real-time perspectives, market sentiment, expert opinions, breaking news, and community discourse. Use when: user asks "what are people saying about", "X/Twitter sentiment", "check X for", "search twitter for", "what's CT saying about", or wants public opinion on a stock, sector, company, or market event.

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

Delegate coding tasks to Codex AI for implementation, analysis, and alternative solutions. Use when you need a second AI perspective, want to explore different approaches, or need specialized Codex capabilities for complex coding tasks.

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

AI-powered multi-agent code review. Simulates a team of Principal Engineers reviewing code from different perspectives. Use when asked to review code, check a PR, analyze changes, or perform code review.

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

"Apply phenomenological methods including bracketing (epoche), lived experience inquiry, and Interpretive Phenomenological Analysis (IPA) to uncover the essence of human experience. Use this skill when the user needs to study how people experience a phenomenon from the first-person perspective, apply Husserlian descriptive or Heideggerian interpretive phenomenology, conduct IPA with idiographic focus, or when they ask 'what is the lived experience of X', 'how do I bracket my assumptions', or 'how do I do IPA'.".

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

"Apply Affordance Theory (Gibson, 1979; Norman, 1988) to analyze the action possibilities that an artifact provides to an actor. Use this skill when the user needs to evaluate technology design from an affordance perspective, identify why users struggle with an interface, analyze IT-enabled organizational change through affordance actualization, or when they ask 'what does this technology afford', 'why can't users figure out this feature', or 'how does technology enable new practices'.".

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

Ask the minimum clarifying questions before implementing when scope, constraints, or success criteria are unclear. Use when a request has multiple plausible interpretations, missing acceptance criteria, or ambiguous environment constraints.

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

"Apply the Balanced Scorecard (BSC) framework to translate strategy into measurable objectives across Financial, Customer, Internal Process, and Learning & Growth perspectives. Use this skill when the user needs to set strategic KPIs, create a strategy map, align organizational goals, or connect daily operations to strategic vision — even if they say 'how do we measure strategy execution' or 'our KPIs feel disconnected'.".

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

Container and Kubernetes security assessment. Tests container escape vectors, Docker/containerd socket exposure, K8s RBAC misconfigurations, pod security violations, exposed API servers, etcd access, service account token abuse, image layer secrets, private registry attacks, SSRF to metadata services, cross-namespace network bypass, CIS benchmarks, crypto miner detection, resource exhaustion, and admission controller gaps. Both external and internal (compromised pod) perspectives. Uses trivy, kube-bench, kubectl, nuclei, dive, amicontained, and docker-bench-security. Covers OWASP Kubernetes Top 10 and all 22 Kubernetes Goat attack scenarios.

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

Fetch the latest AI/ML news, trending open-source projects, social media discussions, and KOL (Key Opinion Leader) perspectives from 370+ curated sources. Use when the user asks about recent AI news, AI trends, what's happening in machine learning, open-source AI projects, AI Twitter/Reddit discussions, or wants a daily AI briefing.

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

Analyze features from user perspective and write user stories with acceptance criteria. Use when defining requirements, writing user stories, validating scope against project state, prioritizing features by impact, comparing approaches, analyzing user needs, or planning next work. Triggers: "user story", "acceptance criteria", "scope", "prioritize", "compare requirements", "user needs", "what to build next".

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

Use when designing, reviewing, or debugging Salesforce Flows from an Admin perspective. Triggers: 'flow', 'automation', 'record-triggered flow', 'screen flow', 'scheduled flow', 'flow error', 'flow interview', 'before-save vs after-save', 'flow deployed as draft', 'entry criteria', 'fault connector', 'flow-meta.xml', 'FlowDefinitionView'. NOT for Flow debug mode, Run As user, or Flow test suites — use flow/flow-debugging. NOT for building an OmniStudio OmniScript — use omnistudio/omniscript-design-patterns.

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

Use when enabling, configuring, or monitoring Change Data Capture (CDC) entity selection, channel enrichment, and delivery usage limits from an admin perspective. Covers the PlatformEventChannel and PlatformEventChannelMember metadata, the standard ChangeEvents channel, custom __chn data channels, enrichedFields, filterExpression, destructive deselection, and PlatformEventUsageMetric / EventBusSubscriber monitoring. Trigger keywords: change data capture, CDC, entity selection, change event, platform event channel, channel member, enrichment, event delivery allocation. NOT for writing an Apex change-event trigger — use apex/change-data-capture-apex. NOT for subscribing an external system over Pub/Sub or CometD — use integration/change-data-capture-integration.

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

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

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