「focus」の検索結果

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Stripped-back design emphasizing whitespace, clean typography, and restrained color for maximum clarity and focus.

日本語の概要は準備中です。原文の説明を表示しています。

Conversion-focused design that removes friction and guides users toward action through clarity, trust, and speed.

日本語の概要は準備中です。原文の説明を表示しています。

Structured, enterprise-focused design system emphasizing clarity, consistency, and efficiency for data-dense web applications.

日本語の概要は準備中です。原文の説明を表示しています。

Simplicity-focused design with ample whitespace, legible typography, and a limited color palette to reduce visual clutter.

日本語の概要は準備中です。原文の説明を表示しています。

Canonical design token registry — colors, typography, spacing, sizing, border radius, shadows, z-index, breakpoints, motion, and focus tokens. Used by ui-best-practices rules and all agents that implement or review UI components. Includes CSS variable template for quick project setup.

日本語の概要は準備中です。原文の説明を表示しています。

Design traceable accessibility checks that combine scanners with observable keyboard, focus, semantic, and assistive-technology behavior.

日本語の概要は準備中です。原文の説明を表示しています。

Discover and approve feature requirements through focused interviewing and repository research. Use when the user has a feature idea, unclear scope, conflicting requirements, or needs Flow context artifacts before design.

日本語の概要は準備中です。原文の説明を表示しています。

Build accessible web applications following WCAG 2.1/2.2 guidelines with proper semantic HTML, ARIA attributes, keyboard navigation, screen reader support, and inclusive design. Use when implementing ARIA labels and roles, ensuring keyboard navigation, supporting screen readers, providing text alternatives for images, managing focus, creating accessible forms, building inclusive UI components, testing with accessibility tools, meeting WCAG compliance levels, or designing for users with disabilities.

日本語の概要は準備中です。原文の説明を表示しています。

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 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," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see page-cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing-strategy.

日本語の概要は準備中です。原文の説明を表示しています。

Route architecture, shell, MCP, prototyping, planning, issue, and release-maintenance work to focused engineering skills. Use for specialized engineering workflows that are not language-stack specific.

日本語の概要は準備中です。原文の説明を表示しています。

Route visual design, frontend art direction, motion, image generation, branding, and redesign work to focused design skills. Use when the task is primarily about how an interface or brand should look and feel.

日本語の概要は準備中です。原文の説明を表示しています。

Route code cleanup, maintainability, React diagnostics, and over-engineering review to focused review modes. Use when auditing code quality or asking for a particular review lens.

日本語の概要は準備中です。原文の説明を表示しています。

Route communication modes, learning workflows, retrospectives, output discipline, and perspective shifts to focused productivity skills.

日本語の概要は準備中です。原文の説明を表示しています。

Route Expo application, EAS, native module, styling, deployment, and upgrade work to focused Expo skills. Use when building or operating an Expo or Expo Router project.

日本語の概要は準備中です。原文の説明を表示しています。