「format」の検索結果

Review a written plan or design doc through a designer's lens before implementation - seven passes over information architecture, interaction states, emotional arc, AI-slop risk, design-system alignment, responsive and accessibility coverage, and unresolved decisions. Each dimension is rated 0-10 with an explicit statement of what would make it a 10, then the plan is edited to get there. Use when a plan has a UI surface and you want the design gaps closed before code is written. Not for auditing a live site.

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

Frontend UI design, critique, audit, polish. Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.

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

Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, automated anti-pattern detection, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component.

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

Write clean, readable, and maintainable code following principles from Robert C. Martin's "Clean Code" and Object Calisthenics. Use when writing, reviewing, or refactoring code to improve naming, function design, formatting, error handling, and class structure. Includes code smell detection and refactoring guidance.

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

Use when selecting serialisation formats and contracts for APIs, messaging, caching, or persistence. Keywords: serialisation, System.Text.Json, source generator, protobuf, messagepack, wire compatibility, AOT.

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

Finalize code changes for production readiness by removing duplicate logic, auditing hardcoded values, verifying branch/worktree intent, verifying build integrity, structuring clean commits with Conventional Commits format, and forcing a post-publish branch/worktree cleanup decision.

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

Finalize documentation changes for production readiness by discovering existing conventions, verifying code-doc alignment, reviewing format/terminology/tone consistency, verifying branch/worktree intent, and structuring clean commits with a post-publish branch/worktree cleanup decision. Counterpart of finalize-and-commit for documentation projects.

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

Use when you need this project's coding standards (line length, quotes, import order, naming, commit format) — derive them from the REAL tooling config as a pointer + digest, never a guessed claim.

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

Use when designing product-led retention — habit formation, trigger-action-reward, network vs single-user loops. Triggers on 'why don't users come back', 'design a habit loop'.

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

Use BEFORE editing code that touches user data — traces the value from entry → validation → transformation → storage → egress, every hop cited with file:line.

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

Check any artifact against an explicit specification and report adherence using the add-comments workspace format. Use when validating plans, scripts, docs, or code changes against a source-of-truth spec.

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

Princípios de design de API e tomada de decisão. Seleção REST vs GraphQL vs tRPC, formatos de resposta, versionamento, paginação.

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

Aplica as cores oficiais da marca Anthropic e tipografia a qualquer tipo de artefato que possa se beneficiar da identidade visual da Anthropic. Use quando diretrizes de cores da marca ou padrões de design, formatação visual ou padrões de design corporativo se aplicarem.

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

Quando o usuário quer criar páginas de comparação com concorrentes ou alternativas para SEO e ativação de vendas. Use também quando o usuário menciona 'página de alternativas', 'página vs', 'comparação com concorrentes', 'página de comparação', '[Produto] vs [Produto]', '[Produto] alternativa', ou 'landing pages competitivas'. Cobre quatro formatos: alternativa singular, alternativas plurais, você vs concorrente, e concorrente vs concorrente. Enfatiza pesquisa profunda, arquitetura de conteúdo modular e tipos de seção variados além de tabelas de recursos.

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

Especialista em design de prompts eficazes para aplicações com LLM. Domina estrutura de prompts, gerenciamento de contexto, formatação de output e avaliação de prompts. Use quando: engenharia de prompts, system prompt, few-shot, chain of thought, design de prompts.

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

Quantiza LLMs para 8-bit ou 4-bit com redução de memória de 50-75% e perda mínima de acurácia. Use quando a memória GPU é limitada, precisa ajustar modelos maiores ou quer inferência mais rápida. Suporta formatos INT8, NF4, FP4, treinamento QLoRA e otimizadores 8-bit. Funciona com HuggingFace Transformers.

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

Formato GGUF e quantização llama.cpp para inferência eficiente em CPU/GPU. Use ao implantar modelos em hardware de consumidor, Apple Silicon, ou quando precisar de quantização flexível de 2-8 bits sem requisitos de GPU.

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

Skill de pesquisa profunda alimentado por NotebookLM MCP. Conduz pesquisa estruturada em múltiplas fontes (análise de mercado, inteligência competitiva, análise de tendências, pesquisa de prospects) usando Google NotebookLM como mecanismo de pesquisa, depois entrega briefs formatados e artefatos opcionais de estúdio (slides, podcasts de áudio, vídeos, infográficos, relatórios, mapas mentais).

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

Applies Canvas brand colors, typography, and visual polish to artifacts that benefit from a consistent product look-and-feel. Use it when brand colors, style guidelines, visual formatting, or company design standards apply.

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

Use this Canvas-owned clean-room skill when a spreadsheet file is the primary input or output. Trigger for `.xlsx`, `.xls`, `.xlsm`, `.csv`, `.tsv`, workbooks, templates, trackers, models, dashboards, charts, formulas, data cleaning, formatting, validation, recalculation, and Google Sheets-targeted handoff.

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

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

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

Load this skill whenever the project contains static or interactive maps, embedded map widgets (Google Maps, Leaflet, Mapbox, OpenStreetMap), or any geographic visualizations. Under no circumstances embed a map without a text-based alternative conveying the same information. Absolutely always ensure map controls are keyboard-accessible and that all meaningful map content is available without the visual map.

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

Load this skill whenever the project contains charts, graphs, data visualizations, infographics, or any visual representation of data (bar charts, line charts, pie charts, scatter plots, dashboards). Under no circumstances render a chart without a text alternative, data table, or summary. Prioritize conveying the same information through non-visual means.

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

[Quality] Use when you need to research and configure code quality tooling for any tech stack — linters, formatters, static analysis, pre-commit hooks, and CI gates.

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