「apply」の検索結果

Applies the strategic, philanthropic, and operational frameworks of Andrew Carnegie, founder of Carnegie Steel. Use this skill whenever you are advising on wealth distribution, large-scale philanthropy, operational efficiency, cost control, legacy planning, or organizational leadership. Trigger this skill when users face decisions about charitable giving, managing inherited wealth, optimizing business costs in commodity markets, or structuring trusts and foundations. Apply his ruthless focus on cost-cutting, his belief in empowering self-improvement over direct handouts, and his philosophy that surplus wealth is a public trust.

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

Applies the reasoning style of Daphne Koller (machine learning pioneer, co-founder of Coursera, founder and CEO of Insitro). Use this skill whenever you encounter problems involving AI and machine learning in biology, drug discovery, interdisciplinary collaboration, data generation vs. data mining, or transitioning from academia to industry. Trigger this skill when advising on career trade-offs, building cross-functional teams (especially bridging engineers and domain experts), designing data pipelines, evaluating causality vs. correlation, or applying AI to physical systems ('where bits meet atoms'). Channel her focus on fit-for-purpose data, pragmatism, and disproportionate leverage.

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

Use this skill whenever you are reasoning about large-scale scientific projects, genomics, bioethics, data infrastructure, or long-term medical translation. Eric S. Lander (geneticist, Broad Institute, Human Genome Project) provides a framework for hypothesis-free discovery, structuring "big science," and treating biology as an information science. Reach for this when the user is discussing open science, collaborative ecosystems, CRISPR/gene editing ethics, managing massive datasets, or setting realistic timelines for technological breakthroughs. Apply his principles to avoid the "lone genius" myth, prevent overpromising, and build foundational infrastructure that serves the broader community.

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

Applies the pragmatic, financially-grounded reasoning of Marian Ilitch (co-founder of Little Caesars Pizza). Use this skill whenever the user is discussing business partnerships, balancing visionary marketing with financial due diligence, franchise unit economics, family business dynamics, or hands-on financial management. Trigger this when users face trade-offs between rapid growth and profitability, need to enforce unit-level accountability, or are paralyzed by the fear of making mistakes. Apply her principles to ground lofty ideas in tactile, common-sense financial reality.

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

Use this skill to reason like JoAnn E. Manson, epidemiologist at Harvard Medical School and women's health expert. Trigger this skill whenever you are evaluating hormone replacement therapy (HRT), menopause management, nutritional epidemiology, dietary supplements, or clinical trial methodology. Apply her frameworks when users ask about the risks and benefits of HRT, bioidentical hormones, or targeted supplementation. Reach for this skill to differentiate between symptom management and chronic disease prevention, or when assessing observational data versus randomized clinical trials (RCTs) in public health contexts.

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

Perform a comprehensive DRY (Don't Repeat Yourself) code review on a codebase. Identifies duplicated code, repeated logic, redundant patterns, and opportunities for abstraction. Use this skill whenever the user asks to review code for duplication, reduce repetition, apply DRY principles, refactor for reusability, find copy-pasted code, deduplicate logic, or audit code quality with a focus on redundancy. Also trigger when users say things like "clean up my code", "find repeated patterns", "too much boilerplate", "reduce code duplication", or "refactor for maintainability". Works on any language or framework.

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

Use this skill for ANY work involving React, Next.js, TypeScript, or Tailwind in the browser layer. This includes building components and pages, but equally covers debugging and fixing frontend issues: CSS/Tailwind classes not applying, form validation behavior, hydration mismatches between server and client renders, styling bugs, layout shifts, and rendering problems. Also use for refactoring components (e.g., splitting Server vs Client Components), data fetching patterns, state management, bundle optimization, and frontend tooling. If the problem involves what users see or interact with in a web browser — whether building, fixing, or refactoring — use this skill. Not for backend APIs, databases, infrastructure, or DevOps.

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

The single config quality skill. Two modes: (1) Default — review/wire pending self-improvement proposals. (2) Audit — analyzes skills, rules, CLAUDE.md, project refs, hooks, and agents against the actual codebase to find inaccuracies, trigger overlaps, stale references, and weak rules, then fixes them. Trigger on 'self-evolve', 'evolve', 'config health check', 'audit config', 'check claude setup', 'apply this rule', 'reorganize rules', 'ok' (when proposals are pending). NOT for improving individual skills (use skill-creator), diagnosing code bugs (use diagnose), or fixing broken code (use fix).

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

Inspect, stream, and explicitly adjust live Android UI tweak values or invoke app-owned actions through Snap-O. Use when a request mentions Snap-O Tweaks, tweak-enabled Android apps, runtime UI parameters, Compose tweak or action controls, tweak discovery, previously adjusted or currently inactive tweaks, applying all user-made tweak changes, typed values, defaults or resets, tweak batches, explicitly registered actions, the Tweaks REST/SSE API, or selecting between CLI, macOS tool, in-app overlay, and custom tweak interfaces.

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

Use when you have a candidate security finding and before it goes in a comment - restate it, prove reachability, impact and a concrete exploit, apply triage dismissals, then the self-refute pass naming attacker and victim

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

Use when the mobile repository has no theme tokens or component library yet (a new app, an "Apply design system" task, or a task that asks for one), before building any screen - writes the approved design system's generated files from get_design_system (files true) and builds the theme from them when there is one.

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

Use when the repository has no design system yet (no tokens, no component library - a new site/app, an "Apply design system" task, or a task that asks for one), before building any page section - writes the approved design system's generated files from get_design_system (files true) and builds the tokens on them when there is one.

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

Use when adding or changing a Go HTTP endpoint — Fiber v2 or v3 (detect which), thin handlers, central error mapping, boundary validation; the same rules apply to net/http, chi, echo or gin

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

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

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

Job Description 解码器 + Offer 策略系统。把任何 JD 翻译成「这家公司到底在招什么人 / 我的匹配度 / Gap 在哪 / 为什么投/不投 / 面试会问什么 / 下一步怎么走」。只有 3 步：贴 JD → 给简历 → 自动生成并打开一份 HTML Offer Strategy Report。是整个求职链路的入口，向下衔接 Resume Skill 和 BQ Skill。关键词：job description, JD, 职位描述, 匹配度, ATS, resume tailor, 简历定制, 招聘经理, 投不投, should I apply, 面试预测, offer strategy。

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

Design and manage infrastructure as code with Terraform — modules, remote state (S3 + DynamoDB), Stacks (deployments), test framework, preconditions/postconditions, moved/removed blocks, and CI/CD plan/apply separation. Use when user asks to write Terraform config, set up remote state, design modules, manage state, or automate infrastructure. Do NOT use for Kubernetes (use kubernetes), Docker (use docker), or CI/CD pipeline design (use ci-cd).

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

Apply professional-grade security standards to any web application task. Use this skill when writing code that handles authentication, authorization, user input, APIs, file uploads, sessions, secrets, payments, or any data from external sources. Also use when the user asks to review, audit, or assess security of code or a web app. Covers OWASP Top 10 (2025), secure coding, threat modeling, and defensive architecture. Activate even when security is not explicitly mentioned — treat every web feature as a security surface.

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

Apply senior software engineering standards when writing, editing, or refactoring any code. Use this skill whenever the user asks to write a function, build a feature, fix a bug, design a module, or improve existing code — even if they don't mention quality explicitly. The goal is production-grade code: readable, correct, maintainable, secure, and failure-aware. Always active for any coding task, at any scale.

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

Run structured brainstorming sessions (divergent/convergent), improve prompts with 7-dimension framework, and apply decision frameworks (RICE, weighted scoring, first principles, pre-mortem).

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

Detect drift, plan updates, and apply changes to the Shokunin AI Ecosystem. Use this when user asks to update, fix, sync, or verify the ecosystem.

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

Revenue-Centric Design (RCD) — evidence-backed principles for making a SaaS or startup product convert, retain, and monetize. Use when the user works on a landing page or CRO ("my page isn't converting"), onboarding/activation ("users sign up but don't stick"), churn/retention ("customers keep canceling"), pricing/monetization ("how should I price this"), checkout/forms ("dropdowns kill conversion", "annotated checkout"), dashboards/data viz ("cognitive load", "KPI shortlists"), positioning/ICP/go-to-market, feature scope, A/B-test rigor, or AI-era differentiation — or asks for the behavioral-science mechanism behind a design choice. Also use when another skill needs the principle or evidence behind a conversion/retention/pricing/checkout move. Never apply to gambling, betting, or casino products.

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

Run quokka's real-device E2E layer (QA strategy layer 5): drive the real qk binary against connected iPhone/Android devices through tmux, apply deterministic verifiers, and write a report. Use when the user asks to "run /qa", "run the device QA suite", "test against the real device", or before a release. Optionally finishes with an advisory exploratory UX pass (layer 6).

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

Color theme palettes for UI/UX design and personal configurations (i3wm, dunst, etc.). Use when user asks to apply color themes like Tokyo Night, needs color palettes for frontend development, or wants to customize terminal/desktop colors.

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

React conventions. Apply automatically whenever writing or editing React code — JSX/TSX files, components, hooks, props, effects, accessibility (WAI-ARIA), file grouping, React 19 APIs, React Compiler, URL state, and the React ecosystem (TanStack Query, Zustand, React Hook Form, nuqs, Next.js, money and crypto inputs). Builds on the typescript skill, which still applies. Use for any new React code or refactor.

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