「board」の検索結果

World-class accessibility design expertise combining the inclusive design principles of Microsoft's Inclusive Design team, the technical rigor of the W3C WCAG working group, and the lived experience perspective of disability advocates. Accessibility is not a feature - it's a fundamental quality attribute that makes products usable by everyone. Great accessibility design is invisible to those who don't need it and essential to those who do. It benefits everyone: captions help in noisy environments, keyboard navigation helps power users, high contrast helps in bright sunlight. When you design for the extremes, you improve the experience for all. Accessibility is not a checklist - it's a mindset that asks "who are we excluding?" at every design decision. Use when "accessibility, a11y, wcag, screen reader, keyboard navigation, color contrast, alt text, aria, focus management, skip link, assistive technology, inclusive design, ada compliance, section 508, accessible, voiceover, nvda, jaws, tab order, focus trap, accessibility, a11y, wcag, inclusive-design, screen-reader, keyboard-navigation, color-contrast, aria, focus-management, assistive-technology" mentioned.

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

Accessibility isn't a feature - it's a fundamental quality of good software. 1 in 4 adults has a disability. Many more have temporary impairments or situational limitations. Your users include people who can't see, can't hear, can't use a mouse, or can't process information the way you do. This skill covers WCAG guidelines, ARIA patterns, keyboard navigation, screen reader compatibility, and automated testing. Key insight: accessible code is better code. The constraints of accessibility lead to simpler, more semantic, more maintainable implementations. 2025 lesson: Accessibility lawsuits are at an all-time high. "We'll add it later" is both ethically wrong and legally risky. Start accessible, stay accessible. Use when "accessibility, a11y, wcag, aria, screen reader, keyboard navigation, focus trap, alt text, color contrast, skip link, accessible, accessibility, a11y, wcag, aria, screen-reader, keyboard, inclusive, semantic-html" mentioned.

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

Create an onboarding guide for new engineers. Use when a senior developer needs structured onboarding materials.

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

Figma 转 Photoshop (PSD) (Figma → Photoshop (PSD) 设计稿转换 (从业者视角) — 把 Figma 设计文件高保真转换为 Photoshop 分层 PSD, 核心是对齐两个工具的概念/渲染差异, 让产出的设计稿视觉一致. 覆盖: (a) 概念映射 — Figma frame / auto-layout / component / variant / constraint / vector-network / boolean / effect (drop·inner shadow / layer·background blur) / mask / blend mode / gradient / text-engine / color 与 Photoshop artboard / group / smart-object / linked / layer-style / shape-layer / path / clipping·layer mask / blend-mode 的对应关系与不可逆损耗点; (b) 转换方法栈 — 插件直出 PSD / 导出图层 (PNG·SVG) 再重组 / SVG·PDF 桥接 / 手工重建 / Figma REST API + Photoshop UXP·ExtendScript 脚本化, 各法在保真度-可编辑性-工时上的权衡与选型; (c) 保真度 QA — 字体回退与缺字处理 / 颜色空间 (sRGB·ICC profile) / 效果参数对齐 / @Nx·DPI 与栅格化 / 像素 diff 验收; (d) 两种交付目标 — 可编辑分层 PSD vs 像素保真扁平 PSD 的方法选择. 主战场 = Figma Community 插件 + Adobe 官方文档/论坛 + 设计交付 (design handoff) 实践 + 设计师社区. 不含: PSD→Figma 反向转换 / Sketch / Adobe XD / 纯前端 code handoff (HTML·CSS) / 印刷 CMYK 专业制版 (仅触及).) Master OS — automated mastery of Figma → Photoshop (PSD) 设计稿转换 (从业者视角) — 把 Figma 设计文件高保真转换为 Photoshop 分层 PSD, 核心是对齐两个工具的概念/渲染差异, 让产出的设计稿视觉一致. 覆盖: (a) 概念映射 — Figma frame / auto-layout / component / variant / constraint / vector-network / boolean / effect (drop·inner shadow / layer·background blur) / mask / blend mode / gradient / text-engine / color 与 Photoshop artboard / group / smart-object / linked / layer-style / shape-layer / path / clipping·layer mask / blend-mode 的对应关系与不可逆损耗点; (b) 转换方法栈 — 插件直出 PSD / 导出图层 (PNG·SVG) 再重组 / SVG·PDF 桥接 / 手工重建 / Figma REST API + Photoshop UXP·ExtendScript 脚本化, 各法在保真度-可编辑性-工时上的权衡与选型; (c) 保真度 QA — 字体回退与缺字处理 / 颜色空间 (sRGB·ICC profile) / 效果参数对齐 / @Nx·DPI 与栅格化 / 像素 diff 验收; (d) 两种交付目标 — 可编辑分层 PSD vs 像素保真扁平 PSD 的方法选择. 主战场 = Figma Community 插件 + Adobe 官方文档/论坛 + 设计交付 (design handoff) 实践 + 设计师社区. 不含: PSD→Figma 反向转换 / Sketch / Adobe XD / 纯前端 code handoff (HTML·CSS) / 印刷 CMYK 专业制版 (仅触及).: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on Figma → Photoshop (PSD) 设计稿转换 (从业者视角) — 把 Figma 设计文件高保真转换为 Photoshop 分层 PSD, 核心是对齐两个工具的概念/渲染差异, 让产出的设计稿视觉一致. 覆盖: (a) 概念映射 — Figma frame / auto-layout / component / variant / constraint / vector-network / boolean / effect (drop·inner shadow / layer·background blur) / mask / blend mode / gradient / text-engine / color 与 Photoshop artboard / group / smart-object / linked / layer-style / shape-layer / path / clipping·layer mask / blend-mode 的对应关系与不可逆损耗点; (b) 转换方法栈 — 插件直出 PSD / 导出图层 (PNG·SVG) 再重组 / SVG·PDF 桥接 / 手工重建 / Figma REST API + Photoshop UXP·ExtendScript 脚本化, 各法在保真度-可编辑性-工时上的权衡与选型; (c) 保真度 QA — 字体回退与缺字处理 / 颜色空间 (sRGB·ICC profile) / 效果参数对齐 / @Nx·DPI 与栅格化 / 像素 diff 验收; (d) 两种交付目标 — 可编辑分层 PSD vs 像素保真扁平 PSD 的方法选择. 主战场 = Figma Community 插件 + Adobe 官方文档/论坛 + 设计交付 (design handoff) 实践 + 设计师社区. 不含: PSD→Figma 反向转换 / Sketch / Adobe XD / 纯前端 code handoff (HTML·CSS) / 印刷 CMYK 专业制版 (仅触及). problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「figma 转 psd」「figma to psd」「figma 转 photoshop」「figma 导出 psd」「设计稿转换」

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

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.

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

Welcome and set up a new Claude for Financial Advisors user. Gets to know the advisor's RIA, learns their day-to-day pain points and tech stack, walks them through connecting their tools, explains the plugin and how skills work, runs a live pre-meeting demo, shows them how to customize skills, and closes with a personalized recommendation for which skill to try next. Use when the advisor is getting started or says any of: "onboarding," "/onboarding," "get started," "help me get started," "set up claude for financial advisors," "claude for financial advisors setup," "what can this plugin do," "I'm new to this," "show me around," or is in their first session with the plugin.

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

Use before generating, editing, or reviewing any user interface — a dashboard panel, a landing page, an email, a slide, an app screen. Sets three deliberate design dials (variance, motion, density) BEFORE generation so the output has a point of view instead of defaulting to the timid, uniform look that reads as "AI made this". Applies to Genesis's OWN dashboard UI, not only things built for others.

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

Maintain HitKeep dashboard localization. Use whenever a contributor adds or changes user-visible dashboard text, Transloco keys, locale JSON files, OptimusUI locale behavior, language switching, translated labels, localized layout, date/number/duration formatting, or supported dashboard languages.

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

Query and manage Grafana dashboards and Prometheus metrics for Happy infrastructure. Covers grafanactl CLI usage, direct Prometheus queries through Grafana proxy, and dashboard-as-code workflows. Use when user asks about metrics, dashboards, monitoring, Grafana, Prometheus, or wants to add/modify panels.

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

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.

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

Design client onboarding for insurance. TRIGGERS - Use when user needs help with insurance-onboarding-client related tasks.

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

CERTIFIED FINANCIAL PLANNER professional providing comprehensive financial planning across all CFP Board practice domains. Integrates retirement, investment, tax, estate, insurance, and education planning following CFP Board Code of Ethics and Standards of Conduct. Use for holistic financial plans, cash flow analysis, net worth statements, insurance needs, estate planning coordination, education funding (529 plans), tax strategies, retirement projections, or CFP Board Practice Standards compliance.

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

Design client onboarding processes for insurance. TRIGGERS - Use when user needs help with client-onboarding-insurance related tasks.

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

Manage GitHub Projects v2 board: add issues, update field values, and query board state. Use when managing project boards.

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

卖点分镜表：把商品卖点拆成 15–60 秒带货短视频的逐镜分镜表（时间码、画面、台词、字幕、花字、素材来源、运镜），并直接输出可渲染的 storyboard.json。Use when the user wants a storyboard, 分镜, 分镜脚本, shot list, 带货视频脚本, video script from selling points, or needs to plan a product video before generating or editing.

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

This skill should be used when the user runs /dd or /ㅇㅇ to act on the current OS clipboard (text or image) without pasting it into chat. It captures the live clipboard into a local cache and uses only the manifest plus a short preview as context, so error logs and reference images do not bloat the conversation. Korean triggers: "/dd", "/ㅇㅇ", "클립보드 보내줘", "이거 분석해줘", "방금 캡처한 거", "이 레퍼런스로", "스크린샷 드롭". English triggers: "/dd", "drop clipboard", "use what I copied", "this screenshot", "this reference".

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

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," or "lifecycle emails." For in-app onboarding, see onboarding-cro.

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

不一书个人工作台生成器。通过一场引导式访谈，帮用户（包括完全不懂代码的人）做出一个属于自己的手机端个人工作台—— 左侧常驻功能栏、右侧卡片流，打开就是今日计划、打卡、记账、体重、日程、单词、树洞等自己每天真正要用的东西， 可以部署上线并添加到手机桌面，像一个 App 一样用。 当用户说"初始化不一书个人工作台生成器"、"初始化 bys-personal-dashboard"、"我想做一个自己的个人工作台"、 "抖音上那种个人工作台我也想要一个"、"把我的日常安排做成一个手机页面"时必须触发； 即使用户只是丢来一张别人的工作台截图说"我也想要这种"，也应触发。 已有工作台后说"给我的工作台加个XX功能"、"工作台换个配色"、"工作台改一下"时，走迭代流程而不是重新初始化。 用户没说"工作台"这个词时，用三个特征判断：①在手机上用 ②每天都会打开 ③装的是用户自己的私人数据 （体重、账目、打卡、待办、日记）。三个同时成立就该触发，比如"我想把体重记账待办整理到一个地方、 手机上能点开"——这就是工作台，只是用户不知道这个叫法。三个缺任何一个都不要触发。 功能只有一个也算——"我老忘记吃药，想每天在手机上勾一下"就是种子需求，别因为"听起来只是个小功能"就不触发。 判据是数据属于谁，不是数据存在哪：用户自己的记账 Excel 想做成手机上每天看的页面，是工作台；公司销售数据做报表，不是。 不用于：用完就走、不存个人数据的小工具页（抽奖转盘、计算器、放在活动大屏或直播间给别人看的倒计时）、 后台管理系统、 给团队用的多人协作工具、个人博客/作品集/对外展示的个人官网（那些是给别人看的，不是自己每天用的）、 公司或业务数据的报表看板（用 xlsx 之类的技能）、与个人工作台无关的普通 HTML 编码问题。

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

Automate on-target verification of a program's logic by driving its RTT console with rttsh - write Lua scripts that exercise commands and assert responses, output and timing on real hardware. Use when asked to verify target-side behavior on board, build board-level checks for firmware features, or automate hardware test runs.

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

Apache Superset is a widely adopted open-source BI platform for SQL exploration, chart building, and dashboard delivery. This skill is useful when an agent needs to query warehouse data, assemble dashboards, or explain metrics using a mature analytics interface instead of ad hoc notebook code.

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

Expert customer onboarding guidance for accelerating time-to-value and ensuring successful implementations. Use when designing onboarding programs, creating kickoff frameworks, building implementation plans, or optimizing customer activation. Use for training delivery, go-live readiness, sales-to-CS handoffs, early warning detection, and tech-touch automation.

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

Analyze and decompose a product topic into a text-only proposal for the repository's .pm board. Use when the user wants to pressure-test scope, size milestones, identify dependencies, or prepare exact PM board commands without writing board files.

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

Design onboarding and activation flows that help users reach value quickly. Use when the user mentions onboarding, getting started, first-time users, activation, aha moments, or new user flows—not when the work is only the empty-state surface itself.

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

Storyboard a papercut script before any code. Writes the Camera / Cut table, one block per scene with frame-level events on each stressed word, the SFX plan and the proof beat. Use for "storyboard this script" or "plan the camera moves and cuts".

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