「bar」の検索結果

Build production realtime voice agents with Hume's Empathic Voice Interface (EVI): speech-to-speech sessions, empathic/prosodic response design, EVI 3 versus EVI 4-mini selection, WebSocket and SDK integration, tools/function calling, interruption/barge-in, turn-taking, transcripts/audio artifacts, pricing/limits, privacy, safety, consent, and QA.

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

Translate text content between languages with high quality and natural phrasing. Covers document translation, content localization, and multi-language research support for teams working across language barriers.

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

End-to-end eDNA metabarcoding from raw amplicons to community ecology. Covers QC, primer removal, denoising with OBITools3 or DADA2, contamination filtering, taxonomy assignment, Hill number diversity, and constrained ordination. Use when processing environmental DNA samples for biodiversity assessment or ecological surveys.

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

Visualize enrichment results using enrichplot package functions. Use when creating publication-quality figures from clusterProfiler results. Covers dotplot, barplot, cnetplot, emapplot, gseaplot2, ridgeplot, and treeplot.

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

Plot per-group distributions of continuous data using boxplots, violins, beeswarms, quasirandom jitter, and raincloud plots with sample-size honesty (Weissgerber 2015), KDE-bandwidth awareness, and N-aware encoding choices. Use when comparing distributions across a small number of groups — expression per cluster, biomarker per arm, scores per condition — and the bar-of-mean default is misleading.

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

Symfony UX TwigComponent for reusable UI building blocks -- server-rendered components with PHP classes and Twig templates. Use when creating buttons, cards, alerts, badges, navbars, or any reusable UI element with props, blocks/slots, computed properties, or anonymous (template-only) components. Code triggers: AsTwigComponent, #[AsTwigComponent], ExposeInTemplate, PreMount, PostMount, <twig:Alert />, <twig:Button>, component(), computed properties, anonymous component, HTML syntax. Also trigger when the user asks "how to create a reusable component", "how to make a component library", "how to pass props to a component", "how to use slots/blocks in a component", "how to build a design system in Symfony", "what is the HTML syntax for components", "how to create a component without a PHP class". Do NOT trigger for components that re-render dynamically on user input (use live-component), for JS behavior (use stimulus), or for page navigation (use turbo).

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

UX-тексты на русском языке: кнопки, формы, ошибки, пустые состояния, онбординг, подтверждения, уведомления, пуши и микрокопия. Use this skill whenever the user asks to write, rewrite, review, choose, or improve interface copy, product messages, UI strings, transactional emails, push notifications, toasts, snackbars, forms, empty states, onboarding, errors, confirmations, labels, tooltips, or button text. Триггеры: «текст для кнопки», «сообщение об ошибке», «текст в форму», «пустое состояние», «подпись к полю», «текст тоста», «снекбар», «онбординг», «пуш-уведомление», «микрокопия», «UX-текст», «что написать на экране…», «лейбл поля», «тултип», «подтверждение удаления», «письмо-уведомление». Для статей и постов см. skills statya и redaktura; для проектного словаря — redpolitika.

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

Analyze application error logs and monitoring platform exports (Sentry, Datadog, Rollbar) to identify error patterns, duplicates, and severity. Use when someone asks to "audit errors", "analyze exceptions", "find noisy alerts", "deduplicate error groups", or "triage production errors". Parses JSON/CSV error exports and produces categorized reports with root cause analysis.

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

Warren Buffett said he looks for "economic castles protected by unbreachable moats." A moat is a sustainable competitive advantage that protects your business from competitors. Without a moat, success attracts competition that erodes your margins to zero. This skill covers identifying, building, and deepening moats. Network effects, switching costs, brand, scale economies, and the rarer moats like regulatory capture and counter-positioning. Use when "moat, defensibility, competitive advantage, network effects, switching costs, barrier to entry, unfair advantage, protect from competition, sustainable advantage, winner take all, flywheel, lock-in, moat, defensibility, strategy, network-effects, switching-costs, competitive-advantage, seven-powers" mentioned.

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

Expert in negotiation strategy - systematic approaches to reaching agreements that create value. Covers preparation, tactics, objection handling, and closing. Knows when to push, when to concede, and how to expand the pie rather than just divide it. Use when "negotiation, negotiate, deal terms, BATNA, making a deal, closing a deal, contract terms, bargaining, " mentioned.

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

The foundational theory of interactive experience design - loops, motivation, feel, and the art of meaningful playUse when "game design, core loop, game feel, player motivation, game mechanics, meaningful choice, progression system, game economy, game balance, playtesting, GDD, game document, fun factor, engagement, flow state, risk reward, player agency, juice, game polish, 8 kinds of fun, bartle types, MDA framework, game-design, player-experience, core-loop, motivation, game-feel, MDA, playtesting, GDD, systems-thinking, player-psychology, engagement, flow-state" mentioned.

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

Expert in gamification mechanics - points, badges, streaks, progress bars, and the psychology that makes them work. Covers variable reward systems, progress mechanics, social competition, and ethical considerations. Knows how to create engagement without manipulation. Use when "gamification, points, badges, streaks, leaderboard, achievements, engagement, retention loop, " mentioned.

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

AgentCall (agentcall.dev) — Join a video meeting (Google Meet, Teams, Zoom) as an AI bot with voice and visual presence. Supports audio-only mode with voice intelligence (barge-in, interruptions), text-to-speech mode, and webpage modes for custom UI. Use when asked to join a call, attend a meeting, or participate in a video conference.

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

Audit whether a paper's baseline comparisons are COMPLETE, FAIR, and SIGNIFICANT: a required recent SOTA baseline is missing while 'best/SOTA' is claimed (HP-MISSING-BASELINE); a baseline is undertuned / given less compute-tuning-data, run at a mismatched config, or the equal-budget ablation-as-baseline is absent (HP-WEAK-BASELINE); 'outperforms' is asserted over overlapping error bars or with no variance/seeds (HP-SIG-OVERLAP); and a cross-row 'improves over baseline by X%' is arithmetically wrong (HP-DELTA-ERROR, cross-row form only). A versioned per-domain baseline profile + a live leaderboard/recency search are assembled by the EXECUTOR as structured facts; a fresh cross-model reviewer (gpt-5.6-sol xhigh, read-only, fresh thread per dimension) PROPOSES findings, each span-anchored to a ledger claim_id; tools/adjudicate_findings.py DECIDES the verdict. Works at L0 (stated comparisons) and deepens at L2 (configs/result files). A completeness question it cannot settle internally becomes needs_external_check, never a guessed missing baseline. Emits baseline-comparison-audit.findings.json; computes NO verdict. Detect-only. Triggers: "baseline audit", "missing baselines", "is the comparison fair", "weak baseline", "baseline 误报", "SOTA earned?".

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

Accessibility Audit and Testing workflow skill. Use this skill when the user needs You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct audits, identify barriers, and provide remediation guidance and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

Accessibility Audit and Testing workflow skill. Use this skill when the user needs You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct audits, identify barriers, and provide remediation guidance and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

半导体芯片制造工艺 (Semiconductor Process Engineering / 半导体芯片制造工艺 — 以「物理化学极限 + 良率经济双重约束」为特征的集成电路前道/后道制造工艺认知操作系统：从「器件架构与微缩路线（planar→FinFET→GAA nanosheet→CFET、等效微缩 DTCO/STCO、背面供电 BSPDN）→ 工艺整合（FEOL/MOL/BEOL 模块协同、PDK、流片 tape-out）→ 单元工艺（光刻 litho（DUV 浸没式 193i / EUV 13.5nm / 多重曝光 SADP-SAQP / OPC / mask）、刻蚀 etch（RIE/ICP/原子层刻蚀 ALE）、薄膜沉积 depo（CVD/PECVD/LPCVD/ALD/PVD/外延 epi/电镀 Cu）、掺杂 doping（离子注入 ion implant / 退火 RTA-laser anneal）、CMP 化学机械抛光、清洗 cleaning）→ 量测检测 metrology（CD-SEM / OCD / overlay / 椭偏 ellipsometry / 缺陷检测 defect inspection / e-beam）→ 良率工程 yield（缺陷密度 / SPC 统计过程控制 / FDC / APC / DOE 实验设计 / 良率爬坡 yield ramp）→ 先进封装 advanced packaging（2.5D/3D、CoWoS、HBM、混合键合 hybrid bonding、chiplet、TSV）」的完整器件-工艺-良率-量产决策链。覆盖 (a) 第一性张力 — **物理/化学/材料的硬约束（量子隧穿、短沟道效应、RC 延迟、热预算、缺陷物理、ppb 级污染控制）⇄ 良率/成本/产能的经济约束（每片晶圆成本、良率是主经济指标、D0 缺陷密度、wafer-per-hour、折旧）**；**持续微缩/摩尔定律（dimensional + equivalent scaling、节点路线图 N5/N3/N2/A16/A14、high-NA EUV）⇄ 物理极限/微缩放缓（原子尺度、漏电、功耗墙、成本墙、'摩尔定律已死'之争）**；**协同优化/整合（DTCO 设计-工艺协同、STCO 系统-工艺协同、模块间 trade-off）⇄ 单模块极致优化（单一 unit process 工艺窗口）**；**工艺配方的 tacit 手艺（process recipe 调试、工艺窗口、缺陷根因分析、量产 ramp 的经验）⇄ 可建模/可仿真/数据驱动（TCAD 仿真、ML 良率分析、APC/FDC、数字孪生）**；**性能-功耗-面积-成本 PPAC 四角权衡 ⇄ 良率/可制造性 DFM 优先**；**自主可控/国产替代（卡脖子、EUV 出口管制、设备/材料/EDA 国产化、SMIC/长江存储/长鑫/中微/北方华创/上海微电子）⇄ 全球高度分工（ASML 光刻垄断、AMAT/Lam/TEL/KLA 设备、TSMC/Samsung/Intel 代工、全球供应链）**。(b) 核心工作流 / pipeline（最标准、最易蒸高质量 + CLI 化）— 新节点/新工艺导入：器件目标与 PPAC 定义 → 工艺整合方案与 PDK → 单元工艺开发与配方调试（DOE 找工艺窗口）→ 量测建立与 SPC → 良率爬坡（缺陷分类 + 根因分析 + 工艺改善）→ 量产移交与持续改善。具体单元工艺 SOP：光刻（曝光条件 / OPC / overlay 控制 / 多重曝光分解）、刻蚀（选择比 / profile / loading effect / ALE）、沉积（台阶覆盖 / 应力 / 均匀性）、CMP（去除速率 / 碟形 dishing / 侵蚀 erosion）、量测与缺陷分析、良率分析与 FA 失效分析。(c) 工具栈 — 设备（光刻 ASML/上海微电子 SMEE；刻蚀+沉积 AMAT/Lam/TEL/中微 AMEC/北方华创 Naura；离子注入 AMAT/Axcelis；CMP AMAT/荏原 Ebara；量测检测 KLA/AMAT/中科飞测/上海精测）、EDA/TCAD/仿真（Synopsys Sentaurus/Silvaco/Coventor SEMulator3D、OPC Calibre/Synopsys）、良率与制造软件（SPC、MES、FDC/APC、缺陷分析 yield management、PWS）、材料（光刻胶 photoresist、CMP 浆料 slurry、特气、靶材、掩膜 mask blank）。(d) 知识正典 — 半导体工艺 canon 横跨器件物理与制造工程：核心教材（Plummer/Deal/Griffin《Silicon VLSI Technology》、Sze《Physics of Semiconductor Devices》《VLSI Technology》、Wolf & Tauber《Silicon Processing for the VLSI Era》、Campbell《Fabrication Engineering at the Micro and Nanoscale》、May & Spanos《Fundamentals of Semiconductor Manufacturing and Process Control》、Quirk & Serda《Semiconductor Manufacturing Technology》、肖国勇/施敏中文教材）、路线图（ITRS/IRDS、IEEE 国际器件与系统路线图）、顶会论文（IEDM、Symposium on VLSI Technology、IRPS 可靠性、SPIE Advanced Lithography、ISSCC、DAC）、行业分析（SemiAnalysis、TechInsights、IC Knowledge）。(e) figures/流派 — 学术与器件奠基（Gordon Moore 摩尔、Robert Dennard 登纳德微缩、胡正明 Chenming Hu FinFET/UTB-SOI 发明人 UC Berkeley、刘明 Tsu-Jae King Liu Berkeley、Krishna Saraswat Stanford、Mark Bohr Intel 工艺架构）、产业领袖与工艺大师（张忠谋 Morris Chang TSMC、林本坚 Burn-Jeng Lin 浸没式光刻、Martin van den Brink ASML、米玉杰/梁孟松 SMIC/三星工艺、Mark Liu/魏哲家 TSMC）、行业分析师（Dylan Patel SemiAnalysis、Scotten Jones IC Knowledge、TechInsights 拆解、Handel Jones）、科普与拆解（Asianometry、The Chip Letter、半导体行业观察）。流派分歧：等效微缩派 vs 摩尔定律已死派、前道微缩 vs 先进封装 chiplet 异构集成、dimensional scaling vs DTCO 协同优化、IDM vs 纯代工 foundry 模式、自主可控/国产替代路线 vs 全球分工。(f) 行业话术/黑话 — 制程节点 node / 流片 tape-out / 工艺窗口 process window / 良率 yield / 缺陷密度 D0 / 关键尺寸 CD / 套刻 overlay / 掩膜 reticle-mask / 光刻胶 PR / 浸没式 immersion / EUV/DUV / 多重曝光 multi-patterning SADP-SAQP / OPC / 刻蚀选择比 selectivity / profile / loading effect / 原子层刻蚀 ALE / 台阶覆盖 step coverage / 外延 epi / 离子注入 implant / 退火 anneal / RTA / CMP / dishing-erosion / FEOL-MOL-BEOL / FinFET / GAA / 纳米片 nanosheet / CFET / 背面供电 BSPDN / high-NA / PPAC / DTCO-STCO / DFM / SPC / FDC-APC / DOE / WAT-PCM / 良率爬坡 yield ramp / FA 失效分析 / particle 颗粒 / 洁净室 cleanroom-级别 / 12寸-8寸 wafer / chiplet / CoWoS / HBM / 混合键合 hybrid bonding / TSV / PDK / 等效微缩. (g) 争议/批判 — 「摩尔定律是否已死 vs 等效微缩继续」、「节点命名营销化（N3/N2 ≠ 物理 3nm/2nm，gate pitch/metal pitch 才是真尺度）」、「前道微缩 vs 先进封装异构集成谁是未来」、「自主可控/国产替代的现实（EUV 卡脖子、设备/材料/EDA 国产化进度、出口管制 entity list、良率与成熟度差距）」、「良率/成本/性能三角权衡」、「人才稀缺与工艺 know-how 的 tacit 性」、「中国大基金/产能扩张是否过剩」、「制裁与技术封锁」。(h) 大量隐性工艺手艺（process recipe 调试与工艺窗口寻找、缺陷根因分析与 FA、量产良率爬坡的经验判

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

独立开发者与微型 SaaS — 单人或极小团队 (≤3 人) 构建可持续订阅收入的软件产品商业, 有别于自由职业/咨询、企业级 SaaS 和开源维护: (a) 产品发现与验证 (自己的痒 vs 市场优先 Nugent/Walling; 着陆页冒烟测试; 先接 Stripe 再写代码; JTBD 访谈适配独立开发者场景; Reddit/HN/X/社区痛点挖掘; Mom Test 验证框架; 公开构建作为验证机制); (b) 独立开发者技术架构 (无聊技术论 McKinley; 单体优先; serverless vs VPS 在 ≤$100/月预算下的取舍; Rails/Django/Laravel/Next.js 等框架的出货速度选型; 托管服务优先于自建; Supabase/PlanetScale/Neon 数据库即服务; Clerk/Auth0 认证即服务; Stripe/Paddle/LemonSqueezy 支付; Vercel/Fly.io/Railway 部署; AI 辅助编码 Cursor/Copilot 作为力量倍增器); (c) 无营销团队的分发与增长 (SEO 作为微型 SaaS 护城河; Product Hunt 发布; AppSumo 终身授权利弊; 冷邮件; Twitter/X 公开构建; IndieHackers 社区分发; 集成市场 Shopify/WordPress/Zapier/Slack 应用目录; 联盟计划; 一人内容营销); (d) 定价与变现 (SaaS 定价心理学; freemium vs 免费试用 vs 纯付费; 按席位 vs 按用量 vs 固定费率; 年付折扣; 老用户保价; 微型 SaaS 流失率控制; MRR/ARR/LTV/CAC 在微型规模的含义; $10K MRR 里程碑心理学); (e) 独立创始人心智模型与生活设计 (default alive vs default dead Graham; 拉面盈利 Levels; 生活方式生意 vs 增长生意的光谱; 独立开发者倦怠预防; 时间管理与上下文切换成本; 地理套利与远程优先; 一次构建反复销售的资产思维; 社区作为支持网络 IndieHackers/WIP/MicroConf); (f) 法务与运营基础 (公司注册地选择 LLC/Ltd/GmbH 税效; Stripe Atlas vs Firstbase vs 本地律师; 服务条款与隐私政策; GDPR/CCPA 低成本合规; 知识产权基础; 首次雇人的承包商 vs 员工选择; 独立开发者会计 SaaS — Xero/QuickBooks; 多辖区税务义务)。中国独立开发者生态: 出海作为主导策略 (从中国构建面向全球市场的产品以避开国内竞争/监管); 即刻/V2EX/少数派作为社区枢纽; 微信小程序作为替代分发; 小报童/爱发电作为中文市场变现; 人民币定价心理学; 支付宝/微信支付集成; ICP 备案要求; 中国区 App Store 审核差异; 独立开发者周刊。诚实处理: 生存偏差 (每一个 Pieter Levels 背后是数千个从未达到 $1K MRR 的人), AI 对微型 SaaS 生态位的颠覆 (wrapper 产品脆弱), 独自构建的孤独与心理健康成本, 公开构建的表演性质 vs 真正透明, AppSumo 终身授权上瘾毁坏单位经济, 样板代码销售的伦理边界。不含: 企业级 SaaS (不同 GTM/销售/融资模型), 不含: 自由职业/咨询 (用时间换钱非建资产), 不含: 开源维护 (不同可持续性模型), 不含: 风投支持的创业 (不同增长期望), 不含: 无代码/低代码平台构建 (相邻但不同受众), 不含: 内容创作作为主业。 (Independent Developer and Micro-SaaS — the craft of single-person or tiny-team (≤3 people) software product businesses that generate sustainable recurring revenue without venture capital, distinct from freelancing/consulting, enterprise SaaS, and open-source maintainership: (a) product discovery and validation (scratching your own itch vs market-first Nugent/Walling; landing page smoke tests; Stripe checkout before code; Jobs-to-Be-Done interview adapted to solo context; Reddit/HN/X/community pain-point mining; idea validation frameworks Fitzpatrick Mom Test; build-in-public as validation mechanism); (b) technical architecture for solo operators (boring technology thesis Mckinley; monolith-first; serverless vs VPS tradeoffs for ≤$100/mo infra; framework selection for shipping speed — Rails/Django/Laravel/Next.js/Remix/SvelteKit; managed services over self-hosted whenever possible; database-as-a-service Supabase/PlanetScale/Neon/Turso; auth-as-a-service Clerk/Auth0/Supabase Auth; payment integration Stripe/Paddle/LemonSqueezy; deployment Vercel/Fly.io/Railway/Render; monorepo vs polyrepo for solo; AI-assisted coding Cursor/Copilot as force multiplier); (c) distribution and growth without a marketing team (SEO as moat for micro-SaaS Ahrefs-style content marketing on 1-person budget; Product Hunt launches; AppSumo lifetime deals tradeoffs; cold email outreach; Twitter/X building in public; IndieHackers community distribution; integration marketplaces Shopify/WordPress/Zapier/Slack app directories as channels; affiliate programs; content marketing at scale-of-one); (d) pricing and monetization (SaaS pricing psychology Patel/Campbell; freemium vs free trial vs paid-only; per-seat vs usage-based vs flat-rate; annual discount strategies; grandfathering existing customers; churn reduction for micro-SaaS — Baremetrics/ProfitWell/ChartMogul analytics; MRR/ARR/LTV/CAC at micro scale; the $10K MRR milestone psychology); (e) solo founder mental model and lifestyle design (default alive vs default dead Graham; ramen profitability Levels; lifestyle business vs growth business spectrum; burnout prevention for solo operators — no team to delegate to; time management and context-switching costs; geographic arbitrage and remote-first; the 'build once sell twice' asset mindset; community as support network IndieHackers/WIP/MicroConf); (f) legal and operational basics (incorporation LLC/Ltd/Gm

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

Create interactive data visualizations using Vega-Lite declarative JSON grammar. Supports 20+ chart types (bar, line, scatter, histogram, boxplot, grouped/stacked variations, etc.) via templates and programmatic builders. Use when users upload data for charting, request specific chart types, or mention visualizations. Produces portable JSON specs with inline data islands that work in Claude artifacts and can be adapted for production.

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

Odoo 19 development knowledge base with 18 specialized guides covering Actions (ir.actions.*, cron jobs, server actions), Controllers (HTTP routing, endpoints, auth types), Data files (XML/CSV records, shortcuts, noupdate), API Decorators (@api.depends, @api.constrains, @api.ondelete, @api.onchange, @api.model, @api.private), SQL Constraints (models.Constraint replacing _sql_constraints), Database Indexes (models.Index), Module development (manifest, wizards, reports), Field types (Char, Text, Monetary, relational fields), Manifest configuration (__manifest__.py, dependencies, asset bundles), Mixins (mail.thread, mail.activity.mixin, mail.alias.mixin, utm.mixin), ORM Model methods (search, CRUD, domain filters, recordsets, CamelCase model naming), Migration scripts (pre/post/end hooks, data migration), OWL frontend components (hooks, services, lifecycle), Performance optimization (N+1 prevention, batch ops, _read_group), QWeb Reports (PDF/HTML, paper formats, barcodes, t-out), Security/ACL (record rules, field permissions, privilege-based groups, @api.private), Testing (TransactionCase, HttpCase, mocking, query count assertions), Transactions (savepoints, UniqueViolation, serialization failures), Translations (i18n, PO files, translatable fields), XML Views (list/form/search, kanban card templates, xpath inheritance, QWeb templates). Use when writing, reviewing, or debugging any Odoo 19 Python or XML code, creating or modifying modules, fixing performance issues, or looking up Odoo 19 API patterns and best practices. Includes CSS/SCSS asset authoring and review for Odoo addons.

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

Complete reference for DTG Base module utilities and helpers. DTGBase is an abstract model providing common utility methods for date/time handling, barcode generation, timezone conversion, file operations, and more.

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

Orchestrate a MULTI-PHASE, dependent, or resumable run over many provider subagents from a JS script, off the main context (`cc-fleet workflow`). Use for fan-out→barrier→synthesis, per-item pipelines, loop-until-dry, or a run that must survive a kill and `--resume` from its journal. NOT a flat fan-out of independent tasks (that is /cc-fleet:subagent — cheaper, no script); NOT interactive collaboration (that is /cc-fleet:team); NOT trivial single-shot work for the main session.

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

Orchestrate a MULTI-PHASE, dependent, or resumable run over many cc-fleet PROVIDER subagents from a JS script, off the main context (`cc-fleet workflow`). Use for fan-out→barrier→synthesis, per-item pipelines, loop-until-dry, or a run that must survive a kill and `--resume` from its journal. Trigger ONLY to run a cc-fleet provider workflow. NOT a flat fan-out of independent tasks (that is /cc-fleet:subagent — cheaper, no script); NOT trivial single-shot work; NOT for editing or researching cc-fleet's own workflow code.

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

Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does this site use', 'how is this built'. Also for single elements: 'copy this navbar', 'recreate this illustration', 'give me a prompt to regenerate this graphic' — element mode outputs a focused element.md, with token-grounded image-model prompts when the element is visual art. If the user brings any visual source and wants to understand it at a design level — this skill should activate.

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