「time」の検索結果

World-class content strategy expertise combining the frameworks of Andy Crestodina's data-driven approach, Ann Handley's "everybody writes" philosophy, and the content engines that power companies like HubSpot, Ahrefs, and Intercom. Content strategy isn't about creating content - it's about creating the right content for the right audience at the right time in the right format. The best content strategists think in systems, not pieces. They build content engines that compound over time and turn strangers into customers and customers into advocates. Use when "content strategy, content plan, editorial calendar, blog strategy, content marketing, topic clusters, pillar content, content audit, content calendar, SEO content, content distribution, content funnel, thought leadership, content engine, content topics, what to write, content, strategy, editorial, SEO, blog, planning, distribution, measurement" mentioned.

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

Specialist in creating size-optimized real-time audio-visual demos and procedural artUse when "demoscene, size coding, 64k intro, 4k intro, 1k intro, tiny code, shader golf, shader minification, procedural demo, bytebeat, pouet, demo party, real-time procedural, demoscene, size-coding, 64k-intro, 4k-intro, shader-optimization, procedural, webgl, graphics" mentioned.

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

Plan a zero-downtime migration for data or infrastructure. Use when a senior developer needs a safe migration strategy.

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

量化交易 (量化交易 (Quantitative Trading) — 面向股票、期货与期权二级市场的系统化交易者（私募/自营/公募量化研究员、CTA 交易员、有工程能力的个人系统化交易者）的『把一个交易想法，变成一个在真钱上还站得住的策略』的判断体系；不是加密与链上交易（那是 crypto-onchain-trading 的范围），不是个人长期资产配置与理财（personal-investing），不是卖方投行的并购与承销（investment-banking-mna），也不是主观基本面选股与券商 IT 系统开发。覆盖：(a) 第一性张力 —— 这行的核心世界观分歧：**经济学解释先行 ⇄ 数据里挖出来就行**（一派要求任何超额收益背后先有风险补偿或行为偏差的故事，否则视为噪音；另一派认为解释是事后编的，只信严格的样本外与实盘，机器学习派把这条推到极致，两派对同一个因子会给出完全相反的判断）；**横截面选股 ⇄ 时序趋势跟踪**（选股要在同一时点比较一篮子标的的相对好坏、假设均值回复与相对定价，CTA 趋势在单一品种的时间序列上假设动量延续，两者的研究方法、回测口径、风险来源和亏损形态几乎不重叠，却常被外行混为一谈）；**样本内的漂亮曲线 ⇄ 多重检验之后还剩什么**（因子动物园与可复制性危机是本行最重要的一次集体自省：显著性门槛该抬多高、发表后收益衰减多少、大量已发表因子在严格复制下失效，以及回测过拟合的概率如何度量）；**回测至上 ⇄ 只信实盘**（回测是唯一能低成本证伪的工具，也是最容易骗自己的工具：前视偏差、幸存者偏差、时点数据缺失、参数寻优、重复使用同一份历史数据；于是有人把纸上交易与小仓位实盘当成唯一可信的检验）；**alpha ⇄ 容量与成本**（一个策略的规模是它自己的敌人：冲击成本随规模上升、换手越高越吃成本、拥挤度让同类策略在回撤时同时踩踏；毛收益漂亮而净收益为负是新手最常见的死法）；**风险预算 ⇄ 收益最大化**（波动率目标、凯利与部分凯利、风险平价、回撤止损、杠杆与尾部，这一层的分歧决定了同一个信号在不同人手里是稳健产品还是爆仓故事）；**高频做市 ⇄ 中低频统计套利与基本面量化**（延迟、撮合机制、报单结构与硬件是一套技能树，因子构建、组合优化与风险模型是另一套，混谈两者是外行破绽之一）；**学术公开 ⇄ 业界闭源**（真正在赚钱的策略通常不发表，公开材料存在系统性的幸存者偏差与选择性披露，这是本行诚实边界的核心）；**中国市场的制度约束 ⇄ 教科书假设**（T+1、涨跌停、融券与做空成本、股指期货基差与贴水、行业与市值中性化的实际口径、指数增强与市场中性产品的收益来源，以及监管对程序化交易与高频交易的报告与差异化收费要求，让直接照搬美股论文的做法在 A 股经常失效）；**模型信心 ⇄ 制度与市场结构变化**（策略衰减、结构性断点、极端行情下相关性同时上升、去杠杆踩踏，这些不是尾部意外而是本行的常态风险）。(b) 工具栈 —— 数据（行情与基本面的时点数据 point-in-time、复权口径、停牌与退市处理、财报修订、指数成分历史、期货主力连续合约的拼接方式、期权链与波动率曲面数据；供应商与开源社区两条路线）、研究框架（向量化回测与事件驱动回测的取舍、因子检验与分层回测、组合优化与风险模型、机器学习工具链与交叉验证的时间序列改造）、执行与交易接口（券商与期货柜台接口、模拟盘、订单类型与算法委托、成交回报与对账）、基础设施（时序数据库与列式存储、行情落地、任务编排、实验记录与版本管理）、以及最被低估的东西：一份写清楚假设与失效条件的策略说明书、一套不会自欺的回测规范、一张归因表 —— 选型的真正分岔从来不是功能清单，而是『你的策略是靠信号质量赢，还是靠执行与成本赢』。(c) 心智模型层 —— 收益必须先有来源（风险补偿、行为偏差、结构性约束或提供流动性）；样本外只有一次，用完就没了；毛收益是观点，净收益才是事实；规模是策略的敌人；相关性在你最需要分散的时候上升；回测里每多试一次，显著性就贬值一次；活下来比赢一次重要，所以先定风险预算再谈收益。(d) 工作流 —— 想法与假设成文、数据准备与清洗、单因子与信号检验、组合构建与风险约束、交易成本与容量估计、样本外与滚动前推验证、纸上交易与小仓位实盘、上线监控与风控阈值、业绩归因与衰减检测、策略退役与复盘、极端行情与事故处置、多策略配置与资金分配。(e) 表达 DNA、质量基准（什么算一次可信的回测与一次合格的策略上线）、反模式（外行与新手最容易犯的错：只看年化与最大回撤、参数寻优后的曲线拟合、忽略成本与容量、用未来数据、拿主力连续合约当真实可交易序列、把杠杆当收益来源、爆仓后归因于黑天鹅）、智识谱系（学术因子与资产定价派、系统化 CTA 与趋势跟踪派、金融机器学习派、市场微观结构与执行派、期权与波动率交易派、风险管理与尾部批评派、中国私募的指数增强与市场中性实践派）。) Master OS — automated mastery of 量化交易 (Quantitative Trading) — 面向股票、期货与期权二级市场的系统化交易者（私募/自营/公募量化研究员、CTA 交易员、有工程能力的个人系统化交易者）的『把一个交易想法，变成一个在真钱上还站得住的策略』的判断体系；不是加密与链上交易（那是 crypto-onchain-trading 的范围），不是个人长期资产配置与理财（personal-investing），不是卖方投行的并购与承销（investment-banking-mna），也不是主观基本面选股与券商 IT 系统开发。覆盖：(a) 第一性张力 —— 这行的核心世界观分歧：**经济学解释先行 ⇄ 数据里挖出来就行**（一派要求任何超额收益背后先有风险补偿或行为偏差的故事，否则视为噪音；另一派认为解释是事后编的，只信严格的样本外与实盘，机器学习派把这条推到极致，两派对同一个因子会给出完全相反的判断）；**横截面选股 ⇄ 时序趋势跟踪**（选股要在同一时点比较一篮子标的的相对好坏、假设均值回复与相对定价，CTA 趋势在单一品种的时间序列上假设动量延续，两者的研究方法、回测口径、风险来源和亏损形态几乎不重叠，却常被外行混为一谈）；**样本内的漂亮曲线 ⇄ 多重检验之后还剩什么**（因子动物园与可复制性危机是本行最重要的一次集体自省：显著性门槛该抬多高、发表后收益衰减多少、大量已发表因子在严格复制下失效，以及回测过拟合的概率如何度量）；**回测至上 ⇄ 只信实盘**（回测是唯一能低成本证伪的工具，也是最容易骗自己的工具：前视偏差、幸存者偏差、时点数据缺失、参数寻优、重复使用同一份历史数据；于是有人把纸上交易与小仓位实盘当成唯一可信的检验）；**alpha ⇄ 容量与成本**（一个策略的规模是它自己的敌人：冲击成本随规模上升、换手越高越吃成本、拥挤度让同类策略在回撤时同时踩踏；毛收益漂亮而净收益为负是新手最常见的死法）；**风险预算 ⇄ 收益最大化**（波动率目标、凯利与部分凯利、风险平价、回撤止损、杠杆与尾部，这一层的分歧决定了同一个信号在不同人手里是稳健产品还是爆仓故事）；**高频做市 ⇄ 中低频统计套利与基本面量化**（延迟、撮合机制、报单结构与硬件是一套技能树，因子构建、组合优化与风险模型是另一套，混谈两者是外行破绽之一）；**学术公开 ⇄ 业界闭源**（真正在赚钱的策略通常不发表，公开材料存在系统性的幸存者偏差与选择性披露，这是本行诚实边界的核心）；**中国市场的制度约束 ⇄ 教科书假设**（T+1、涨跌停、融券与做空成本、股指期货基差与贴水、行业与市值中性化的实际口径、指数增强与市场中性产品的收益来源，以及监管对程序化交易与高频交易的报告与差异化收费要求，让直接照搬美股论文的做法在 A 股经常失效）；**模型信心 ⇄ 制度与市场结构变化**（策略衰减、结构性断点、极端行情下相关性同时上升、去杠杆踩踏，这些不是尾部意外而是本行的常态风险）。(b) 工具栈 —— 数据（行情与基本面的时点数据 point-in-time、复权口径、停牌与退市处理、财报修订、指数成分历史、期货主力连续合约的拼接方式、期权链与波动率曲面数据；供应商与开源社区两条路线）、研究框架（向量化回测与事件驱动回测的取舍、因子检验与分层回测、组合优化与风险模型、机器学习工具链与交叉验证的时间序列改造）、执行与交易接口（券商与期货柜台接口、模拟盘、订单类型与算法委托、成交回报与对账）、基础设施（时序数据库与列式存储、行情落地、任务编排、实验记录与版本管理）、以及最被低估的东西：一份写清楚假设与失效条件的策略说明书、一套不会自欺的回测规范、一张归因表 —— 选型的真正分岔从来不是功能清单，而是『你的策略是靠信号质量赢，还是靠执行与成本赢』。(c) 心智模型层 —— 收益必须先有来源（风险补偿、行为偏差、结构性约束或提供流动性）；样本外只有一次，用完就没了；毛收益是观点，净收益才是事实；规模是策略的敌人；相关性在你最需要分散的时候上升；回测里每多试一次，显著性就贬值一次；活下来比赢一次重要，所以先定风险预算再谈收益。(d) 工作流 —— 想法与假设成文、数据准备与清洗、单因子与信号检验、组合构建与风险约束、交易成本与容量估计、样本外与滚动前推验证、纸上交易与小仓位实盘、上线监控与风控阈值、业绩归因与衰减检测、策略退役与复盘、极端行情与事故处置、多策略配置与资金分配。(e) 表达 DNA、质量基准（什么算一次可信的回测与一次合格的策略上线）、反模式（外行与新手最容易犯的错：只看年化与最大回撤、参数寻优

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

独立开发者与微型 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

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

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.

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

When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but don't use the product," "time to value," or "first session experience." Use this whenever users are signing up but not sticking around. For ongoing email sequences, see emails.

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

Email triage system that handles both one-time setup and recurring triage in a single skill. Auto-detects state: if no knowledge base exists at ${WORKSPACE}/Email/, runs an 8-section onboarding interview (grill-me discipline, one question at a time) to build a 7-file personalized KB, then offers to run triage immediately. If the KB already exists, skips setup and goes straight to triage — searches recent emails, classifies them via the user's taxonomy, researches new senders, generates TAKE IT/WORTH/PASS/FLAG recommendations, drafts replies (NEVER sends), delivers a report, and updates the KB. Use with 'update' argument to refresh preferences. Setup triggers: 'set up my inbox', 'configure inbox triage', 'set up my email system', 'configure email triage', 'build my email knowledge base', 'initialize email management'. Triage triggers: 'triage my inbox', 'inbox triage', 'check my email', 'run email triage', 'process my inbox', 'what's new in my email', 'handle my email', 'email triage'.

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

Use when the user has audio or video and wants a timestamped transcript (SRT) in the source language. Routes by source language — Chinese defaults to Volcano (豆包) ASR; other languages (Spanish, English, Portuguese, French, Italian, Japanese, Korean, etc.) use OpenAI Whisper API with word-level timestamps and self-assembled cues. Outputs SRT with punctuation-bounded cues capped for on-screen reading. Triggers — "转写", "转成字幕", "做 SRT", "transcribe", "make subtitles", "speech to text", "出字幕".

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

Use when the user has 2+ video / audio recordings of the same event captured by different devices (cameras, phones, separate audio recorders) and wants them aligned to a single common timeline. Outputs only a lightweight `.sync.json` sidecar per input — original files are never re-encoded. Triggers — "多机位同步", "对齐这几个机位", "match camera timelines", "sync these angles", "audio drift between cameras", "separate audio recorder", "Riverside / Zoom recording that needs to line up".

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

Suede AI CI and branch-protection wiring for any repo and any stack: path-aware jobs, a single aggregator required check that cannot deadlock, lockfile hygiene, runtime pinning from the repo, and the exact branch-protection settings. Use when asked to set up CI, protect main, make CI block a bad merge, fix a required check that hangs pending forever, or repair duplicate or misfiring pipelines. Detects the repo's real apps, package managers, and runtime versions first; emits workflow files and settings, never pushes or flips protection itself. NOT FOR: reviewing or grading the change the gate is failing on (use suede-code); designing the AI eval cases to wire in (use suede-ai-eval); branch and worktree hygiene (a private Suede Labs companion, not in this pack).

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

This skill should be used when the user asks to "cut to the beat", "fix the pacing", "edit this sequence", "sync cuts to music/BPM", "add a match cut / J-cut / L-cut", "build a speed ramp", or "plan a shot sequence / edit timeline". Covers editing rhythm, transitions, retiming, and translating an edit plan to an NLE or a code timeline (Remotion/AE frames).

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

Fix bugs and broken behavior when there is enough evidence to act on a repair path. Use for errors, crashes, incorrect results, API failures (500, 404, 403), CORS problems, database exceptions, broken rendering, duplicated or wrong data, off-by-one mistakes, timezone/date bugs, broken forms, config-caused runtime failures, and regressions. Trigger when the user wants the bug repaired and the conversation already contains a clear failing area, a reproducible failing test, a concrete error path, or a prior diagnosis to implement. Do NOT use for new features, pure explanation, architecture discussion, broad research, or bug reports where the main need is figuring out why the behavior happens — use diagnose for that.

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

Use this skill when calculating control system performance metrics such as rise time, overshoot percentage, steady-state error, or settling time for evaluating simulation results.

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

Diagnoses and fixes slow Neo4j Cypher queries by reading execution plans, identifying bad operators (AllNodesScan, CartesianProduct, Eager, NodeByLabelScan), and prescribing fixes (indexes, hints, query rewrites, runtime selection). Use when a query is slow, when EXPLAIN or PROFILE output needs interpretation, when dbHits or pageCacheHitRatio are poor, when cardinality estimation diverges from actuals, or when deciding between slotted/pipelined/parallel runtimes. Covers USING INDEX / USING SCAN / USING JOIN hints, db.stats.retrieve, SHOW QUERIES, SHOW TRANSACTIONS, TERMINATE TRANSACTION. Does NOT write new Cypher from scratch — use neo4j-cypher-skill. Does NOT cover GDS algorithm tuning — use neo4j-gds-skill. Does NOT cover index/constraint creation syntax details — use neo4j-cypher-skill references/indexes.md.

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

Use when writing anything that moves, animates, counts down or simulates - per-frame vs fixed-step callbacks per engine, the accumulator loop with interpolation, delta-scaled smoothing, pause and time scale, and determinism.

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

Design GPU-accelerated animations with Web Animations API (WAAPI), Scroll-Driven Animations (ScrollTimeline/ViewTimeline), FLIP technique, easing systems, and accessibility (prefers-reduced-motion). Use when user asks to create animations, transitions, scroll effects, page transitions, or interactive motion for web UIs. Do NOT use for canvas-based animations (Three.js, PixiJS), video editing, or non-web (native mobile) motion design.

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

Use when a task names Krea or Krea 2, when choosing between Krea's hosted API and its open weights, when wiring the Krea 2 Image or Krea 2 Style Reference API nodes, when building with FLUX.1 Krea Dev, when someone asks about Krea Realtime or realtime or streaming video generation, or when a Krea 2 job needs ControlNet, instruction editing, identity preservation or per-layer conditioning control that core ComfyUI does not provide.

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

Prepare a complete client review meeting prep document for a financial advisor, for whatever timeframe the review covers (quarterly, annual, ad hoc). Given a household name or email and a timeframe, pulls CRM context (Salesforce/Redtail/Wealthbox), portfolio data (Orion/Addepar/Envestnet-Tamarac), estate & tax status (Wealth.com), meeting notes (Zocks or CRM), recent correspondence (Gmail/Outlook), and the household's plan snapshot (MoneyGuide), then assembles a meeting-ready prep doc with agenda, talking points, and action items. Triggers on "pre meeting", "/pre-meeting", "prep for [client]", "quarterly review prep", "get me ready for my meeting with [client]", or "client meeting tomorrow".

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

Browser-check what a change could have broken in timepicker-ui (library demo and docs-app, before/after). Use at the end of a task that changed library behavior or styles (app/src) or docs-app pages, or when the user asks to check that nothing broke. Not for demo examples in app/docs, copy/typo/comment edits or one-line fixes (HARD RULES §5 in CLAUDE.md). Main agent only, never delegated to a subagent.

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

Audit and improve the accessibility of the timepicker-ui LIBRARY (app/src) - ARIA, keyboard operability, focus trap/management, screen-reader announcements, labels - against WCAG 2.2 AA and the WAI-ARIA Authoring Practices. Use when the user wants an a11y audit/fix of the picker itself (clock, wheel, plugins, modal, inputs). Drives the accessibility subagent in an audit → approve → apply flow. Does NOT cover docs-app (use /docs-a11y for that).

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

Audit and improve the accessibility of the timepicker-ui documentation site (docs-app/) - landmarks, heading order, skip links, keyboard nav, focus management in the command menu / sidebar / dialogs, color contrast, alt text, ARIA on custom components, Radix usage, reduced motion - against WCAG 2.2 AA. Use when the user wants an a11y audit/fix of the docs site. Drives the docs-accessibility subagent in an audit → approve → apply flow. Does NOT cover the library (use /a11y for that).

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

Audit and improve the discoverability of the timepicker-ui documentation site (docs-app/) across the full modern discoverability stack — SEO (ranking), AEO (answer engines / featured snippets), GEO (citations inside ChatGPT/Gemini/Perplexity/Claude), and AIO (Google AI Overviews). Use when the user wants to optimize docs SEO, improve Google ranking/positioning, win featured snippets or AI-answer boxes, get the docs cited by AI engines, add or fix sitemap/robots/manifest, fill in page metadata, add Open Graph/Twitter cards, answer-first copy, or JSON-LD (FAQPage/SoftwareApplication/TechArticle/BreadcrumbList). Drives the seo-optimizer subagent with an audit → approve → apply flow.

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

Cut a new timepicker-ui release. Use when the user wants to bump the version, prepare a release, write/update the changelog, or sync version + changelog across README, CHANGELOG.md and the docs-app (changelog/what's-new/version strings). Drives the build-release subagent in an audit → approve → apply flow, then runs a sanity build. Does NOT git-commit/tag or npm-publish — proposes those for the user to run.

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