「sel」の検索結果

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.

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

Merge, split, rotate, insert, delete, and extract PDF pages with ComPDF. Use for PDF page management, document assembly, cleanup, restructuring, and selected-page output.

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

Select and run Guardrails verification for code, dependency, test, tooling, documentation, or repository-workflow changes.

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

Start or resume a requested Guardrails implementation or PR takeover in the selected linked worktree with bounded scope and verification.

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

用户在做决策时不确定自己是否真的理解某个领域，或准备进入一个看似熟悉但缺乏验证记录的领域时。 语言信号："我觉得我懂这个行业"/"这个看起来很简单"/"别人都在投这个"/"我来研究一下这个新领域" 不适用于：纯信息查询、日常琐事选择、用户已有充分专业知识的领域。

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

用户在考虑是否卖出持仓、评估持有期限，或纠结于"何时卖出"时。 语言信号:"什么时候该卖"/"持有多久合适"/"已经涨了要不要卖"/"什么时候止盈" 不适用于:短期交易决策或投机性持仓的卖出判断。

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

Build and grow online communities across all platforms and contexts — from developer/B2B communities (Discord, Slack, Circle, Discourse) to social communities (Twitter/X, Reddit, Farcaster) to crypto/holder communities (Telegram). Covers strategy, platform selection, channel architecture, member journey mapping, onboarding, engagement rituals, ambassador/champions programs, moderation, governance, growth, retention, crisis management, and metrics. Use for: community-led growth, community strategy, developer community, user community, Discord/Slack/forum/Telegram setup, ambassador programs, community health, holder psychology, engagement systems, social community building, cross-platform coordination.

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

Comprehensive customer success and retention expertise combining onboarding, health scoring, churn prevention, retention strategies, and LTV maximization. Use when designing customer onboarding flows, reducing churn, building health scores, creating retention systems, designing upsells, or improving customer lifetime value. Covers proactive engagement, cancel flows, dunning, re-engagement, and the full customer lifecycle.

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

When the user wants help with pricing decisions, packaging, or monetization strategy. Use when the user mentions 'pricing,' 'pricing model,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'pricing strategy,' 'pricing experiments,' 'price anchoring,' 'enterprise pricing,' 'GTM pricing,' 'price setting,' 'value-based pricing,' 'revenue optimization,' or 'pricing psychology.' This skill covers pricing research, tier structure, packaging strategy, discount frameworks, upsell mechanics, and pricing experiments.

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

ESPHome device configuration, firmware, and IoT product development. Covers ESP32, ESP32-S3, ESP32-C3, ESP32-C6, ESP32-H2, ESP32-P4, ESP8266, RP2040, RP2350, nRF52, LibreTiny, Shelly, Sonoff, Tuya, BLE proxy, Matter firmware, Thread, Zigbee, GPIO, sensor YAML, LVGL displays, LED strips, voice assistant hardware, device flashing, Arduino conversion, alarm_control_panel, lock, valve, media_player, microphone, speaker, audio DAC, event entities, datetime entities, Z-Wave proxy, MIPI DSI displays, and DLMS smart meters. Also covers designing new ESPHome-based products: hardware selection, component sourcing, PCB design (KiCad), enclosures, 3D printing, CE/FCC certification, BOM optimization, and manufacturing from prototype to production scale.

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

Email/SMS lifecycle and deliverability framework for SMB Product-Builder products that send transactional or lifecycle messages (booking reminders, CRM sequences, receipts, win-back). Codifies provider selection (Resend/Postmark/Twilio/SendGrid), domain auth (SPF/DKIM/DMARC), consent and compliance (TCPA, CAN-SPAM, CASL, quiet hours, double opt-in), suppression-list discipline, and the transactional-vs-marketing split. Applied by integrations-engineer and senior-dev whenever a feature sends messages — so deliverability and consent are designed in, not bolted on after the first spam complaint.

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

Coverage-design method for qa-engineer — pyramid ratios per archetype, equivalence/boundary/property case selection, mutation score as the real coverage signal, and a flake-quarantine policy. Turns "coverage is 90%" (a number with no method) into a defensible test plan. Emits TEST-STRATEGY-{slug}.md, which the QA gate checks exists.

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

Reusable 3-round self-challenge + arbiter pattern for filtering false positives from findings/verdicts. Use when the cost of a false-positive gate block exceeds the cost of ~4 extra LLM turns.

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

The pinned default technology stack for SMB Product-Builder products. One source of truth so the architect, app-scaffolder, auth-engineer, and senior-dev never re-decide the stack per build — they build ON it. Covers framework, ORM/DB, auth, UI, payments/email/SMS, files, jobs, testing, hosting, and observability, with the chosen default + the one sanctioned alternative for each. Applied whenever a new product is scaffolded or a stack choice would otherwise be improvised. Re-deciding the stack every build is the biggest silent time sink; this kills it.

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

How to write — and how to use — a skill that IS one aesthetic rather than a catalogue of them. A catalogue lets an agent pick, and it picks the modal option; a committed aesthetic makes it execute one thing precisely, against rules you can check. Use when a design keeps coming out competent and forgettable, when starting a new brand surface with no reference, or when authoring a house style you want executed the same way twice.

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

Turn multiview fit reports into a sequential or parallel repair queue for aligning Blender products to source-of-truth templates. Use after validation shows disalignment, when the agent must iteratively fix wireframe, texture, lighting, or projection mismatches, and when skill gaps should trigger self-refinement before another rebuild.

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

Run a self-refinement loop when a Blender result is subpar, user expectations are not met, validation fails, or repeated issues reveal missing skill depth. The loop diagnoses the gap, decides whether to repair the artifact or acquire/refine a generic skill, sanitizes lessons for reusable publication, updates docs/versioning, validates, and prepares stage/commit/push when explicitly requested.

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

Read a known webpage or execute a discovered workflow or data-provider capability. Use for page content or structured results once the URL or tool is selected.

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

Evaluate Cognee itself from local telemetry: recall hit rate, latency, saves, injected context, tokens saved, a scorecard and grade, before vs after an update, and why a memory was or wasn't injected last turn.

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

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).

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

Guides mobile platform selection and delivery across native and cross-platform stacks. Use when planning auth, push, deep links, releases, or app architecture for iOS/Android.

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

Audits SaaS, cloud, payment, and AI spend. Use when analyzing bills, right-sizing plans, sizing Savings Plans or CUDs, cutting payment-processing fees, or LLM self-host breakeven.

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

Designs AI-first help centers and self-service support. Use when shaping taxonomy, article templates, or content and answer contract for support AI, not the bot build.

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

Chooses among AI/ML approaches: classical ML, LLM, RAG, fine-tuning, agents, embeddings, MoE or SSM. Use when picking or scaling an architecture, or self-host vs API.

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