'focus' 검색 결과

Perform a thorough code review focused on correctness, maintainability, performance, and best practices.

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

GitHub Actions security review for workflow exploitation vulnerabilities. Use when asked to "review GitHub Actions", "audit workflows", "check CI security", "GHA security", "workflow security review", or review .github/workflows/ for pwn requests, expression injection, credential theft, and supply chain attacks. Exploitation-focused with concrete PoC scenarios.

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

Guides a user from "I want to watch recordings but don't know which ones" to a short, high-signal list of sessions worth watching. Use when the user asks which sessions or replays to watch, wants help finding interesting / useful recordings, says they don't know where to start in session replay, or wants to watch sessions about a goal (signup, pricing, onboarding, checkout, a feature, rageclicks, errors, mobile, a specific person) without naming exact filters. Turns a vague intent into a focused RecordingsQuery via `query-session-recordings-list`, then deep-links the best few and hands off to `investigating-replay`. Do NOT use when the user already has a recording/session ID (use investigating-replay) or wants the replay for a known error issue (use finding-replay-for-issue).

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

Diagnose why a PostHog endpoint is slow or expensive and propose a concrete fix — bump the cache TTL, enable materialisation, restructure variables, or rewrite the query. Use when the user says "this endpoint is slow", "my endpoint times out", "we're hitting the cost cap on this one", or asks "should I materialise this?". Focuses on a single named endpoint, not a project-wide audit.

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

Explore and diagnose a PostHog endpoint's execution logs — error messages, failed runs, cache misses, slow runs, or unexpected row counts during endpoint invocations. Use when the user says "my endpoint is failing", "show me the logs for endpoint X", "what error did endpoint Y produce", "why did endpoint Z return no rows", "is this endpoint hitting cache", or "check the last N runs". Focused on a single named endpoint's runtime log entries, not project-wide auditing or query performance profiling.

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

Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.

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

End-to-end post-GWAS causal inference pipeline orchestrating heritability partitioning, genetic correlation, Mendelian randomization with CHP-aware sensitivity (CAUSE / LHC-MR), colocalization, fine-mapping with SuSiE / FOCUS, mediation, TWAS triangulation, cis-pQTL drug-target MR, effector-gene prioritization (L2G / PoPS / cS2G), and GenomicSEM common-factor GWAS. Use when triangulating causal inference across multiple complementary methods, prioritizing tissues via stratified LDSC, nominating or de-risking drug targets, mapping a lead SNP to a candidate effector gene, modeling shared genetic architecture across correlated traits, or producing a STROBE-MR-compliant publication-grade evidence battery from GWAS summary statistics.

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

Design focused empty states for zero-data, no-results, permission, and error situations with clear value framing, strong CTAs, and less dead chrome. Use when the user mentions blank pages, zero-data screens, no results, permission states, or dead controls—not broader onboarding strategy.

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

Systematically audit and remediate accessibility issues in UI, focusing on keyboard navigation, screen reader support, color contrast, semantic HTML, ARIA usage, and motion sensitivity. Use when the user wants to improve accessibility, make a component accessible, fix WCAG violations, add keyboard support, or ensure screen reader compatibility.

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

Three-axis orchestrator: (1) clean section boundaries — naming, routes, views, ViewModels, DB ownership, cross-section access; (2) internal cohesion — no EF in service layer, caching in service only, proper interfaces, reusable ViewComponents, architecture-test coverage; (3) focused tests — grouped under the section, covering invariants/negatives/triggers, pruned of redundancy. Push-and-bot-review loop. Use when a sizable PR landed, a section shows arch drift, or /pr-review returned a non-trivial violation list. Camps is the gold-standard reference.

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

Autonomous Reforge-guided refactor workflow for the Humans repository. Use when the user wants Codex to target a section such as Shifts, Users, Teams, Tickets, Camps, or Store, create a dedicated worktree/branch from origin/main, run iterative architecture-focused improvements, score each stage with Reforge, gate commits through a score-blind read-only architecture review, append score and verdict details to commit messages after review acceptance, push progress, and open a PR when the loop reaches stasis.

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

When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' or 'copy sweep.' This skill provides a systematic approach to editing marketing copy through multiple focused passes.

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

When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," or "in-app pricing." Distinct from public pricing pages (see page-cro) — this skill focuses on in-product upgrade moments where the user has already experienced value.

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

Windows アプリ開発 (Fluent Design / WinUI 3) のデザインガイドライン。 layout, alignment, spacing, geometry, elevation, breakpoints, Color, materials, Mica, Acrylic, Smoke, Reveal Focus, Reveal Highlight (非推奨), typography, Segoe Fluent Icons, app icons, motion, easing, page transitions, connected animation, parallax, reduce motion, haptics, NavigationView, TitleBar, TabView, CommandBar, menus, keyboard accelerators, access keys, accessibility, high contrast, globalization, RTL, widgets design。

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

Windows アプリ開発 (Windows App SDK / WinRT) の OS 統合 API リファレンス。 DeviceInformation, DeviceWatcher, センサー (Accelerometer, Gyrometer, Pedometer, Compass, OrientationSensor, ActivitySensor), Bluetooth LE, USB, Serial, HID, Battery, HttpClient, StreamSocket, WebSocket, BackgroundDownloader/Uploader, NetworkInformation, PointerInput, KeyboardInput, IME/TextInput, FocusManager, DragAndDrop, ResourceLoader (多言語化・地域化), Calendar, DateTimeFormatter, CurrencyFormatter, PasswordVault, OAuth2Manager, Web Account Manager (WAM) / MSAL, WebAuthenticationBroker, WindowsHello/Passkeys, Age signals, CryptographicBuffer, Clipboard, DataTransferManager, Launcher, ProtocolActivation, JumpList, TaskbarManager, SecondaryTile, StartupTask, Smart App Control, Phone Link。

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

Generate ideas that don't sound logical, then validate them with cheap behavioural experiments — Rory Sutherland's 'the opposite of a good idea can be a good idea' plus revealed-preference testing. Use when the obvious/logical solution is saturated and the user wants genuinely different options, asks 'what's a creative/unconventional angle', 'how do we stand out', 'should we run a test/experiment', 'how do we know what people actually want', or is about to trust a survey/focus group. Covers deliberate inversion of the obvious move, why stated preferences lie, and designing small reversible experiments that watch behaviour. Inspired by Rory Sutherland's *Alchemy*. Routed to from psycho-logic. 日本語の相談（「競合と同じ案しか出ない」「アンケートは好評なのに売れない」「思い切った案を安く試したい」）にも使う。中文咨询（“只能想出和竞品一样的方案”“问卷好评却卖不动”）也适用。

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

Bring the Unity Editor window to front. Use when Unity must be visible for visual checks or user-facing interaction.

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

DON'T USE THAT SKILL. IT'S JUST AN EXAMPLE. Summarize today's Gmail inbox by category with anonymized senders and subjects, then surface the top 3 emails to focus on next. Run only when the user types /email-summary.

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

Harden IAM, storage, keys, and org policies in cloud accounts you administer. Focus on identity, logging, and public-exposure controls.

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

Resolves GWAS associations to candidate causal variants and credible sets via SuSiE, susie_rss, FINEMAP, CAVIAR, DAP-G, PAINTOR, PolyFun, SuSiEx, MultiSuSiE, and FOCUS. Use when narrowing a GWAS lead SNP to a 95 percent credible set, choosing between in-sample and reference LD, calibrating non-sparse loci with SuSiE-inf or FINEMAP-inf, integrating functional priors via PolyFun, fine-mapping across ancestries with SuSiEx, diagnosing LD mismatch via estimate_s_rss and kriging_rss, handling HLA or long-range LD, or feeding credible sets into coloc.susie for colocalization.

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

Provides and generates complete CRUD workflows for Spring Boot 3 services. Creates feature-focused architecture with Spring Data JPA aggregates, repositories, DTOs, controllers, and REST APIs. Validates domain invariants and transaction boundaries. Use when modeling Java backend services, REST API endpoints, database operations, web service patterns, or JPA entities for Spring Boot applications.

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

Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused.

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

Build content-focused websites with Astro — zero JS by default, islands architecture, multi-framework components, and Markdown/MDX support.

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

Expert in building products that wrap AI APIs (OpenAI, Anthropic, etc. ) into focused tools people will pay for. Not just "ChatGPT but different" - products that solve specific problems with AI.

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