「style」の検索結果

Applies the reasoning style of Judy Faulkner, founder and CEO of Epic Systems, to decisions around corporate governance, healthcare technology, and unconventional leadership. Use this skill whenever Claude is asked for advice on going public vs. staying private, M&A strategy (acquisitions), budgeting, reducing software-driven burnout, data privacy, or interoperability. Faulkner's thinking is highly independent, fiercely protective of long-term mission over short-term profits, and deeply skeptical of traditional corporate playbooks (like MBAs, strict budgets, and venture capital). Trigger this skill to channel her focus on organic growth, customer empathy, and treating software as 'mental clay'.

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

Applies the reasoning style of Geoffrey Hinton, deep learning pioneer and 2018 Turing Award winner. Use this skill whenever evaluating AI safety, existential risk, neural network architectures, cognitive science, or tech regulation. Reach for this when the user is discussing LLM capabilities (understanding vs. autocomplete), the biological vs. digital intelligence divide, AI alignment strategies, or the societal/economic impacts of automation. It is highly applicable when dealing with contrarian scientific ideas, hardware/software integration (mortal vs. immortal computing), or global cooperation on technological threats. Do not wait for the user to name Hinton; trigger this skill proactively for any deep learning or AI existential risk analysis.

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

Applies the nutritional epidemiology and public health frameworks of Frank B. Hu (nutrition epidemiologist, Harvard University). Use this skill whenever reasoning about diet quality, public health policy, planetary health, cardiometabolic disease prevention, or evaluating nutritional studies. Trigger this when the user asks about plant-based diets, macronutrient trade-offs ("compared to what?"), the impact of the food environment, or lifestyle factors for longevity. It shifts the AI's focus from single-nutrient reductionism to overall dietary patterns, emphasizing that "zip code is more important than genetic code" and that human health is inextricably linked to planetary health.

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

Refine an approved visual lane.

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

Direct choreography and Viktor-style pacing.

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

Context-aware line edit that strips generic AI writing patterns without flattening the author's voice, plus a findings-only audit mode that names issues instead of rewriting. Applies contextual rules rather than blanket bans on adverbs, passive voice, and punctuation, and locks facts, numbers, quotes, code, links, and the supplied house style before it touches a sentence. Use before copy, a README, an email, a social post, or a doc ships; after a long assisted-writing session; when the text sounds fine but feels generated; or when the user asks for a findings-only slop audit. NOT FOR: writing new copy from scratch; deciding whether a person or a model wrote text; changing or certifying facts, which must be checked against primary evidence before publication.

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

Suede AI full-stack surface builder that runs design, copy, and visual QA as one pass: landing pages, brand surfaces, product UI, dashboards, campaigns, launch pages, and reference-to-target restyles (suedify). Use when a build needs layout and words together, when a redesign or launch surface has to ship end to end, when the request is 'make this site look like that one', or when design, copy, asset, and QA lanes have to move at once. NOT FOR: a design-token, dark-mode, or single-component decision (use suede-design); copy with no layout work (use johnny-suede-write, or suede-copy for one standalone conversion surface); conversion and funnel architecture (use suede-site-alchemy); multi-agent orchestration protocols, WIP protection, and rollback trees (use suede-agent-teams).

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

Builds distinctive, production-grade UIs that avoid generic AI aesthetics. Use whenever the user wants to build, restyle, or give visual direction to any interface — pages, dashboards, landing pages, components, onboarding flows, mobile screens, or design systems — even without an explicit 'design' request. Also triggers for: picking an aesthetic direction, improving the look of a dull/generic existing page, adding visual personality, or choosing colors/typography. Includes a bundled design intelligence database for concrete guidance across web (React, Next.js, Vue, Tailwind) and mobile (React Native, Flutter, SwiftUI).

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

Guide for Kimix opencode-style HTTP server (FastAPI + SSE), including route definitions, builtin endpoints, and app.post usage.

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

Use when styling any web UI - style with Tailwind utility classes and design tokens, avoid custom CSS, and build on the existing Radix/shadcn primitives instead of hand-rolling

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

Write board comments the way a colleague does — lead with the finding, a few lines, no preamble or process narration. Use when about to call add_task_comment or comment_on_pull_request, or when deciding whether something deserves a comment at all.

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

Use when building Flutter screens - compose small stateless widgets, keep layout declarative, decide layout by available width not device/orientation, separate presentation from business logic, and use the theme not hardcoded styles

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

Clean editorial-style interfaces. Warm monochrome palette, typographic contrast, flat bento grids, muted pastels. No gradients, no heavy shadows. Based on taste-skill by Leon Lin & blueemi, improved by shokunin.

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

Guides and best practices for working with Neon Serverless Postgres. Covers getting started, local development with Neon, choosing a connection method, Neon features, authentication (@neondatabase/auth), PostgREST-style data API (@neondatabase/neon-js), Neon CLI, and Neon's Platform API/SDKs. Use for any Neon-related questions.

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

Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

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

Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".

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

Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.

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

Use this skill when user wants to create a refactor plan.

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

Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages or reviewing staged changes.

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

Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.

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

Inspect and diagnose minimal-zine posters, photo restyles, editorial images, and social-card series for subject preservation, factual and text integrity, composition, paper realism, print-process coherence, color signal, anti-AI craft, platform fit, and series continuity. Use when the user asks whether an image has高级感, feels AI-generated, matches Paper Signal or gc-minimal-zine quality, needs improvement, or should be regenerated. Returns evidence-based findings and a targeted correction prompt; regenerates only when the user also asks for a fix.

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

Art-direct and generate one high-craft minimal-zine bitmap from a landscape, portrait, person, object, product, food, plant, building, interior, photograph, mood, sentence, or article concept. Use when the user wants a standalone poetic poster, editorial cover, visual concept, aesthetic photo upgrade, photo-to-zine restyle, or a subject-aware minimal-zine image without the overhead of a social carousel. Chooses adaptive composition and a physically coherent print process, preserves subject identity, saves the final prompt, invokes the runtime-native image generator, and audits the raster result.

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

UI/UX design intelligence with searchable style, palette, typography, and chart databases. Use when designing UI components, choosing colors/fonts, reviewing code for UX issues, building landing pages, or implementing responsive layouts.

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

Creates RPC-style endpoint following layered architecture (Controller → Manager → Repository). Use when creating new API endpoints or CRUD operations.

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