「users」の検索結果

Applies the product philosophy and leadership frameworks of Steve Jobs, co-founder and CEO of Apple Inc. Reach for this skill whenever the user is navigating product design, customer experience, innovation, hiring top-tier talent, or defining corporate culture. Trigger this skill for questions about finding product-market fit, making career trade-offs, building hardware/software ecosystems, or establishing brand values. Use this to push back against feature creep, committee-driven decisions, and technology-first thinking. Apply Jobs's mental models to help users simplify complex systems, focus on craftsmanship, and build products that sit at the intersection of technology and the liberal arts.

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

Use this skill to apply the rigorous epidemiological reasoning of Julie E. Buring (epidemiologist and women's health trialist) to study design, clinical trial critiques, cardiovascular risk assessment, and evidence-based integrative medicine. Trigger this skill whenever you are evaluating medical literature, designing cohort studies or RCTs, assessing conflicting research findings, or analyzing cardiovascular risk factors (especially in women). Reach for this when users ask about the validity of supplements, the discrepancy between observational and randomized data, or how to future-proof a clinical registry.

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

Applies the philosophical reasoning of Mary Midgley (British moral philosopher). Use this skill when analyzing ethical dilemmas involving animals, environmental policy, the limits of science (scientism/reductionism), or when users are trapped by unhelpful metaphors (like 'the selfish gene' or 'humans as machines'). Trigger this whenever evaluating the intersection of biology and human nature, resolving irreconcilable viewpoints, or diagnosing systemic conceptual blockages in society or organizations. Midgley's approach emphasizes holism, emotional fellowship, and viewing philosophy as practical 'plumbing' rather than abstract logic.

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

Applies the reasoning, frameworks, and mental models of Fei-Fei Li, computer vision pioneer, ImageNet creator, and co-director of Stanford HAI. Use this skill whenever Claude encounters topics related to AI ethics, human-centered AI, spatial intelligence, embodied AI, robotics, AI governance, diversity in tech, or the societal impacts of AI. Trigger this skill when users face decisions about AI product design (augment vs. replace), dataset formulation, navigating AI regulation, or choosing audacious research directions. Channel her pragmatic optimism and focus on spatial, physical grounding over pure language models.

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

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.

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

Applies the strategic frameworks and mental models of Anne Wojcicki, co-founder and CEO of 23andMe. Reach for this skill when advising on consumer empowerment, navigating heavily regulated industries, preventative healthcare, data privacy, or disrupting entrenched systems. Use this when the user is dealing with misaligned industry incentives, facing regulatory hurdles, building a consumer-research flywheel, or managing a team through a post-launch 'trough of sorrow'. Apply her principles of 'speaking with data', treating users as partners, and pushing for decade-long systemic change from the outside.

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

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 moral philosophy and literary frameworks of Iris Murdoch (British moral philosopher and novelist). Use this skill whenever you are helping a user navigate ethical dilemmas, interpersonal conflicts, creative writing, literary critique, or the struggle against ego and selfishness. Trigger this skill for topics involving moral psychology, the nature of love, attention, objective morality, the separation of philosophy and literature, or overcoming personal fantasy. Murdoch's approach is essential when users are stuck in self-centered thinking, trying to force a decision through sheer willpower, or struggling to see the reality of other people clearly.

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

Reach for this skill whenever Claude encounters situations involving supply chain innovation, B2B customer respect, community revitalization, vocational education, or navigating massive business crises. Apply the mental models of Diane Hendricks, co-founder of ABC Supply and building supplies billionaire, when users face decisions about strategic acquisitions, counter-cyclical expansion, or treating blue-collar workers as respected entrepreneurs. Use this skill to channel her 'fight or fold' resilience, her strict financial responsibility hierarchy, and her focus on solving the exact pain points you faced as a customer.

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

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.

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

Suede-affiliated in-product monetization design for paywall screens, feature gates, trial-expiry states, usage-limit prompts, and free-to-paid upgrade moments. Use when the user needs trigger timing, message structure, plan presentation, or experiment design after users have experienced value. NOT FOR: public pricing pages (use suede-site-alchemy), tier architecture (use suede-pricing), or cancellation and save flows (use suede-churn-prevention).

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

Suede-affiliated onboarding and activation strategy for first-run sequencing, empty states, setup checklists, activation milestones, time to value, and retention-linked measurement. Use when users sign up but fail to reach first value or the product needs a new first-session flow. NOT FOR: registration optimization (use suede-signup), lifecycle email sequences (use suede-emails), or monetization prompts (use suede-paywalls).

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

Generate and maintain AI-readable markdown documentation for a codebase in docs/. Use this skill whenever the user asks to document their codebase, generate project docs, create architecture docs, update documentation after code changes, build a knowledge base for AI agents, create onboarding docs, map out a codebase, or explain a project structure. Also trigger when users say things like "document this repo", "create docs for my project", "update the docs", "write architecture documentation", "help AI understand my code", "generate a codebase overview", or "maintain docs". This skill is specifically about creating structured markdown files in a docs/ directory that serve as a knowledge base — NOT about writing inline code comments, README files, or API reference docs from docstrings.

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

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.

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

The official Skill Base CLI client. Use the `skb` (Skill Base CLI) command to search, install (single skill or collection), update, delete, publish, and import-from-GitHub skills from Skill Base, as well as configure skb. Triggered when users say "publish skill to skill base", "install collection", "import skill from github", "download/update/delete skill from skill base", "configure skb", "am I logged in", "check skb login", or "configure skill-base-cli".

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

ALWAYS activate when the user's query involves Docker in any way — even if it also matches other skills. If the words docker, Dockerfile, docker-compose, compose.yml, container, or image appear in the query, this skill MUST be used. Covers: writing or editing Dockerfiles and compose files, adding services (postgres, redis, etc.) to compose, volume mounts and data persistence, docker build failures (layer caching, npm install issues), healthchecks and service startup ordering (depends_on), environment variables in containers, port mapping, container crashes and exit codes (OOM/137), non-root users, multi-stage builds, image optimization, .dockerignore, and deploying to container runtimes. Takes priority over general implementation or debugging skills when Docker infrastructure is the subject.

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

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.

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

Build a complete product strategy from context, including objective, users, superpowers, vision, pillars, impact, and roadmap.

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

Programmatic security management in Neo4j — RBAC/ABAC, user lifecycle (CREATE/ALTER/DROP USER), role lifecycle (CREATE/GRANT ROLE/DROP ROLE), privilege grants and denies (GRANT/DENY/REVOKE on graph, database, DBMS), property-level access control, sub-graph access control, SHOW PRIVILEGES inspection, and auth provider config reference (LDAP, OIDC/SSO). Use when an agent needs to manage users, roles, or privileges programmatically via Cypher on the system database. Does NOT handle Cypher query writing — use neo4j-cypher-skill. Does NOT handle cluster ops or backups — use neo4j-cli-tools-skill. Property-level security and ABAC require Enterprise Edition.

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

Guide for creating effective skills. Use when users want to create or update a skill that extends agent's capabilities.

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

Use when updating the stakeholder - report in outcome language (what changed for users, what's next, what decision is needed), translate technical detail, and surface risks early

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

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

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

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.

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

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

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