「card」の検索結果

Use when the user has one or more video clips and wants to add post-production on top — AI-generated cover as first frame, HTML/CSS captions synced to SRT, kinetic illustration overlays at hook moments, chapter chips, end-card CTA, or any other timed motion graphics. Most often used as the downstream of `/wjs-segmenting-video` — pick up where that skill stopped (raw cropped clip + per-clip SRT) and produce the upload-ready MP4. Backed by HyperFrames so everything compiles to ONE final encode — no cascade of re-encodes. Triggers — "加封面", "加字幕", "加动画", "加 CTA", "做后期", "post-production", "title card", "kinetic captions", "end card".

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

Nexscope Ozon Russia SKU full detail query for one product ID per call, returning price, discount, Ozon Card price, rating, review count, stock, sales, revenue, revenue potential/lost revenue, listing date, images, and the complete product card. Trigger for Ozon product or SKU detail, price/rating/sales/stock checks, competitor Ozon cards, Nexscope Ozon detail, or Russian marketplace product detail by a known SKU.

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

A live visual Kanban board and continuity layer for long-running agentic tasks. Nobody wants to read a markdown plan or stare at raw HTML while an agent grinds for an hour, so Plandeck turns the plan into a board that organizes itself. Use it when a task is multi-step, long-running, or needs visual planning. Break the work into cards, declare which card depends on which, and Plandeck computes the critical path, auto-promotes cards to Ready as their dependencies clear, rolls up story-point estimates into an honest percent complete, and names the one next action. Plans, observed transitions, and last-known-good snapshots stay as plain files on disk, so they survive /clear and context resets. After a reset, run plandeck next to recover the single next move and its recent history. If the plan stops parsing, run plandeck doctor before using git. Renders a live board in the browser over SSE. Triggers on plan a project, break down a task, kanban board, task board, visual plan, long-running agent, agentic task, track dependencies, critical path, story-point estimates, what is next, mission journal, recover plan, plandeck.

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

Use when analyzing competitors, creating sales battlecards, building competitive positioning, preparing for competitive deals, or updating competitive intelligence. Triggers: 'battlecard for [competitor]', 'competitive analysis of [competitor]', 'how do we beat [competitor]', 'compare us to [competitor]', 'competitive intel', 'win against [competitor]'.

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

Build a Gumroad-ready digital product from scratch — ebook, card deck, playbook, Notion template, or flipbook. Walks from concept → content outline → design brief → per-item markdown → images → multi-format build (PDF, HTML flipbook, Notion, card deck) → Gumroad sales page + email blast + launch assets. Use when "make a digital product", "build an ebook", "create a playbook", "card deck", "notion template product", "gumroad product", "make a pdf to sell", or any request to ship a sellable information product.

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

Organize, track, and value a trading card game collection. Covers inventory methods, storage best practices, grade-based valuation, want-list management, and collection analytics for Pokemon, MTG, Flesh and Blood, and Kayou cards. Use when starting a new collection and setting up inventory tracking, cataloging an existing collection that has grown beyond casual knowledge, valuing a collection for insurance or sale, or deciding which cards to submit for professional grading based on value potential.

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

品牌無關的 IG/Threads/X/FB 圖卡引擎——把任何主題（idea / 文章 / 教學）變成輪播圖卡 + 4 平台文案。HTML+CSS 模板 → Chrome headless 渲染 PNG。風格由 brand pack 決定（brands/），接哪個 pack 出哪個風格，引擎不綁死品牌。觸發詞：做圖卡、生 carousel、social card、IG 圖卡、Threads 卡片、貼文文案、教學圖卡、infographic、輪播圖、carousel post。

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

Turn a local talking-head / 口播 video into metadata, transcript, and an AI-composed card-based video where the agent composes cards by cloning styled templates and filling them (designing bespoke only when content needs it), then renders to MP4. Ships with the Interflow AI club sign-off ("Interflow AI 出品"). Use when the user asks for interflow-video-cut, 口播成片, talking-head repurposing, video takeaways, transcript cleanup, or turning a spoken video into a captioned card video.

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

Write model cards documenting AI capabilities. TRIGGERS - Use when user needs help with ai-model-card-writer related tasks.

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

Use when the user asks about carding, BIN attacks, payment-card breach markets, fullz/CVV2 trade, autoshops (BidenCash, Brian's Club, Russianmarket, B1ack's Stash), or financial-fraud TTPs. Self-updating knowledge cell.

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

Import and roleplay with SillyTavern-compatible character cards (TavernAI V2/V3 PNG format)

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

Research your competitors and build an interactive battlecard. Outputs an HTML artifact with clickable competitor cards and a comparison matrix. Trigger with "competitive intel", "research competitors", "how do we compare to [competitor]", "battlecard for [competitor]", or "what's new with [competitor]".

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

Elite website image-to-code skill for Codex. For visually important web tasks, it must first generate the design image(s) itself, deeply analyze them, then implement the website to match them as closely as possible. In Codex, it must prefer large, readable, section-specific images instead of tiny compressed boards, generate fresh standalone images for sections or detail views instead of cropping old ones, avoid lazy under-generation, avoid cards-inside-cards-inside-cards UI, and keep the hero clean, spacious, readable, and visible on a small laptop.

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

Use when a task needs the judgment of a Cardiovascular Technologist — measuring and grading a cardiac or vascular ultrasound finding, tracking contrast/anticoagulation/radiation limits during a live cath lab procedure, choosing between imaging modalities for a clinical question, or writing up a diagnostic study for physician sign-off.

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

Elite website image-to-code skill for Codex. For visually important web tasks, it must first generate the design image(s) itself, deeply analyze them, then implement the website to match them as closely as possible. In Codex, it must prefer large, readable, section-specific images instead of tiny compressed boards, generate fresh standalone images for sections or detail views instead of cropping old ones, avoid lazy under-generation, avoid cards-inside-cards-inside-cards UI, and keep the hero clean, spacious, readable, and visible on a small laptop.

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

塔罗牌占星：把「抽三张塔罗牌」与「西方占星本命盘」合为一次解读。 用户带着一个具体问题来 → 抽三张牌（可复现的 seed）→ 若愿意提供生日，则用脚本 确定性地排出星座与星盘 → 用黄金黎明的塔罗↔占星对应把两者接起来（牌落在黄道哪一旬， 你的哪颗行星正站在那里）→ 给出一张交叉对照表、对所问之事的审慎取向与可执行建议。 塔罗层：牌阵位置语义、牌与牌的组合叙事、元素尊贵、正逆位、直觉对话、治疗性解读。 占星层：本命盘、相位与宫位、必然尊贵、行运盘推运、比较盘/组合盘（合盘）、太阳弧推运。 当用户说：塔罗、塔罗牌、抽牌、抽三张牌、占卜、算一卦（西洋）、牌阵、正逆位、 星盘、本命盘、星座、上升星座、月亮星座、占星、行运、流年、合盘、比较盘、 太阳弧、推运、我该不该……、这段关系会怎样、我适不适合换工作 时使用。 English triggers: "tarot", "tarot reading", "draw three cards", "what do the cards say", "spread", "reversed card", "natal chart", "birth chart", "astrology", "rising sign", "transits", "synastry", "composite chart", "solar arc", "progressions", "should I take this job", "what does my chart say". 内置离线脚本：抽牌洗牌（可复现 seed）、本命盘（行星/四轴/宫位/相位/元素统计）、 必然尊贵、牌↔盘共鸣、元素数字统计、行运盘、比较盘+组合盘、太阳弧+次限推运。 边界：要**周公解梦**请用 `zhougong-dream-interpretation`；要**四柱八字**请用 `bazi`； 要**中式黄历择日/测吉凶**请用 `zhanshi-jixiong`。本技能只做西洋塔罗与西洋占星。 即使用户只是随口说「帮我抽张牌看看」「我最近水逆吗」，也应主动使用本技能。

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

Evaluates cardiovascular risk factors in persons receiving hormone therapy by obtaining fasting lipid profiles and diabetes screening. Triggered when a patient is on gender-affirming hormone therapy and due for routine cardiovascular risk assessment.

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

Generates infographic image card series with 12 visual styles, 8 layouts, and 3 color palettes. Breaks content into 1-10 cartoon-style image cards optimized for social media engagement. Use when user mentions "小红书图片", "小红书种草", "小绿书", "微信图文", "微信贴图", "image cards", "图片卡片", baoyu-xhs-images, or wants social media infographic series.

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

Elite website image-to-code skill for Codex. For visually important web tasks, it must first generate the design image(s) itself, deeply analyze them, then implement the website to match them as closely as possible. In Codex, it must prefer large, readable, section-specific images instead of tiny compressed boards, generate fresh standalone images for sections or detail views instead of cropping old ones, avoid lazy under-generation, avoid cards-inside-cards-inside-cards UI, and keep the hero clean, spacious, readable, and visible on a small laptop.

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

Use when creating, testing, or updating active-recall flashcards grounded in session concepts to reinforce retention.

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

Builds a DRAFT structured interview scorecard from a job description: five to eight competencies traced to it, past-behaviour and situational evidence questions with probes, four-level rating anchors written as observable behaviours, a blank scoring sheet, a panel plan and the items the hiring manager must confirm. Use when the user asks to "build an interview scorecard for this job description", "write competency questions for this role", "draft the interview guide for the panel", "set up a rating scale for the interviewers", "put together a structured interview kit" or "create a hiring rubric from the JD". Do not use for writing or fixing the job description itself, use job-description-drafter instead; for the new hire's first 90 days, use onboarding-plan-builder. Drafts for human review; never approves, authorises or signs off.

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

Use when the user asks to "build battle cards", "prep the sales team for launch", or "write the internal launch FAQ"; produces the internal enablement kit for a sales-led launch — battle cards vs each named alternative (where we win / where they win / trap questions, every fact traceable), a sales talk track derived from the PR-FAQ spine, an objection-handling table (objection → response → evidence), internal FAQ + CS macros, and an internal launch announcement with embargo discipline. Not for the external message house — use message-house-builder; not for competitor tracking itself — use competitor-tracker or competitor-analysis; not for outbound sequences — use cold-outbound-sequencer. 销售赋能/battle card/销售叙事/异议处理/内部FAQ

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

When the user wants to create, plan, or optimize App Store In-App Events — the event cards that appear on the Today tab, search results, and your product page. Use when the user mentions "in-app event", "App Store event", "event card", "Today tab", "live event", "challenge", "game event", "seasonal event card", or wants visibility beyond organic search. For general ASO, see aso-audit. For seasonal keyword strategy, see seasonal-aso.

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

Access security tokens and smart cards using CryptoTokenKit. Use when building token driver extensions with TKTokenDriver and TKToken, communicating with smart cards via TKSmartCard, implementing certificate-based authentication, managing token sessions, or integrating hardware security tokens with the system keychain.

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