「story」の検索結果

Creative director v2 — brand vision, campaigns, team leadership, client presentations, storytelling

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

Product Inventor e Design Alchemist de nivel maximo — combina Product Thinking, Design Systems, UI Engineering, Psicologia Cognitiva, Storytelling e execucao impecavel nivel Jobs/Apple.

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

Builds personal brand assets using Seth Godin's frameworks: signature symbol, slogan, surprise (Purple Cow), salient idea, and signature story. Use when named (branding), or when the user asks for a brand symbol, slogan, tagline, Purple Cow, counterintuitive angle, core idea, brand story, or personal brand positioning.

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

penpotを含む場合は必ず読み込む。セルフホスト環境管理、MCP経由デザインシステム構築・ UI/UXデザイン作成・プロトタイプ参照、デザインからのアプリケーション生成、 外部パイプライン（トークン同期・Style Dictionary・Storybook）、デザインレビュー・コメント操作。

Music-video production skill for turning an existing MP3 into a pure-visual (no-voiceover) music video through a bundled Busabase App-in-Skill UI. Use when the user wants to build an MV from a song they upload: write a one-line concept, keep a cast of characters with reference cards, and break the song into storyboard shots where each shot has a scene description and an image + video that can be either AI-generated (image-to-image from the character cards, draft video via local LTX) or uploaded by the user. Same character/storyboard management model as kelly-drama. Song generation (creating the song itself, incl. voice-cloned singing) is a documented future capability.

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

Brand-narrative single source of truth (Busabase App-in-Skill) built on the TALE discipline — Trace / Architect / Land / Evaluate. The agent drafts positioning, the message house of value pillars, the story bank, evidence-backed proof points, and vocabulary/tone guardrails; the human curates which drafts become the CANONICAL narrative; a drift monitor flags off-brand usage across channels. Use when the user invokes $kelly-brand or /kelly-brand, mentions brand narrative, brand messaging, positioning, message house, value pillars, story bank, proof points, tone/vocabulary guardrails, narrative quality (NQS), brand drift, or wants a single source of truth for what the brand says.

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

Generate release notes from merged PR history and commits. Categorizes changes by type and creates GitHub releases with semantic versioning. Use when the user asks to create a release or generate release notes (e.g., "リリースノート", "release note", "リリース作成"). Do NOT use for changelogs, commit summaries, or PR descriptions.

Parse Windows Prefetch files using the windowsprefetch Python library to reconstruct application execution history, detect renamed or masquerading binaries, and identify suspicious program execution patterns.

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

Analyze Chromium-based browser artifacts using Hindsight to extract browsing history, downloads, cookies, cached content, autofill data, saved passwords, and browser extensions from Chrome, Edge, Brave, and Opera for forensic investigation.

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

Visual storytelling skill chain for DSH; use for narrative motion, scroll-driven UX, and stack-aware implementation rails.

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

Inspects PostHog Visual Review (VR) runs that gate PR merges with screenshot regression checks. Use when the user mentions "visual review", "VR", "snapshot diff", "screenshot test", "storybook regression", "playwright snapshot", asks why a PR is blocked or what changed visually, wants to triage the VR backlog, decide whether a snapshot diff is real vs flaky, or check whether a story has been changing across runs. Also invoke when a PR has a failing `visual-review` status check, when a PR comment mentions "Visual review", or when the user is on a branch with an open VR run.

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

Work safely with endpoint versions — preview a draft in the playground, roll back to an older version, update settings on one version without bumping query history, deactivate a specific version. Use when the user asks "how do I roll back my endpoint", "preview my changes before publishing", "I want to fix v5 without bumping the version", or anything involving the version history. Calls out today's limitations honestly: there is no pointer flip; "rollback" means forking the old query into a new top version.

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

Querying Stellar chain data via Stellar RPC (preferred) and Horizon (legacy). Covers RPC JSON-RPC methods, Horizon REST endpoints, streaming, pagination, historical queries, Hubble/Galexie for deep history, and the RPC/Horizon migration story. Use when reading balances, transactions, operations, ledgers, contract events, or building any indexer/analytics workflow.

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

Windows アプリ開発 (WinUI 3 / XAML) の UI 基盤リファレンス。 レイアウトパネル Grid, StackPanel, Canvas, RelativePanel, SplitView, ScrollViewer、 XAML マークアップ x:Bind, x:Name, x:Class, StaticResource, ThemeResource、 添付プロパティ, 依存関係プロパティ、 スタイル・テーマ Style, ControlTemplate, DataTemplate, VisualStateManager, ResourceDictionary, Acrylic, Mica, SystemBackdrop、 データバインディング Binding, INotifyPropertyChanged, ObservableCollection, IValueConverter, DataContext, MVVM、 アニメーション Storyboard, DoubleAnimation, EasingFunction, ThemeTransition, ConnectedAnimation, ImplicitAnimation。

Figma REST API / Plugin API / Widget API / Code Connect / MCP Server リファレンス。 OAuth / Personal Access Token / Plan Access Token 認証、files, variables, webhooks, Dev Mode, Dev Resources, SCIM, activity-logs, library-analytics エンドポイント。 figma グローバルオブジェクト、node types (FrameNode, TextNode, ComponentNode 等)、 data types、figma.variables、figma.codegen、figma.ui。 useSyncedState, useSyncedMap, usePropertyMenu, AutoLayout, register。 Code Connect CLI / UI / React / SwiftUI / Compose / HTML / Storybook / custom parsers。 Figma MCP Server ツール・プロンプト・Code to Canvas・Write to Canvas。

nuqs (Type-safe URL search params state manager for React / Next.js) リファレンス。 useQueryState, useQueryStates, parsers (parseAsString / parseAsInteger / parseAsBoolean / parseAsArrayOf 等)、 Next.js App Router / Pages Router、SSR、シャロールーティング、history 制御。 createSerializer, createStandardSchemaV1, inferParserType ユーティリティ、URL 長さ制限 (limits)。

Assemble a Japanese shokumu-keirekisho (career history document) from an experience inventory, choosing between reverse-chronological, chronological, and skills-based layouts, mapping the target posting's requirements to the experiences that can support them, and drafting the summary, work history, skills, and self-PR so that each sentence stays within what its evidence supports and confidential details are abstracted. Use when a user wants to write or rebuild a whole shokumu-keirekisho for a specific posting or as a general version, or wants to decide which experiences to include and in what order; do not use to invent experience, numbers, titles, or qualifications, to predict whether it will pass screening, to fill in a rirekisho form, or to submit it anywhere.

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

Inventory a person's work history as facts before any document is written, listing each period of employment and what they actually did, splitting every experience into situation, their own actions, outcome, and stated role, and recording what each claim rests on (public record, their own records, someone who was there, or memory alone). Use when a user is starting a job search, needs material for a rirekisho, shokumu-keirekisho, or entry sheet, or wants to find which periods of their history they have never written down; do not use to judge their strengths, aptitude, or market value, to name a job they are suited for, or to write finished application copy.

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

Triage a GitHub issue that already has the cc-issue-created label and is assumed ready to start. Inspect the comment history first to decide whether human confirmation is needed (cc-need-human-check, highest priority — reserved for issue-level deadlock, or for confirmation items answer-issue-questions already investigated and explicitly marked unanswerable); otherwise close the issue as not needed, delegate unanswered confirmation items in the last comment or the description to answer-issue-questions (cc-answer-issue-questions), refresh a description stale relative to settled comment-history content (cc-update-issue), or move to execution (cc-exec-issue). Any UI-changing issue is routed to the design-first flow (cc-create-ui-design) before execution; the exceptions are an issue whose description already names the .pen design to implement against, and a minor UI change that introduces no new visual decision (no new screen/section, no layout change, no new reusable component, no visual expression outside existing design tokens/components). Design files are never edited in the implementation PR. Dependency checks are out of scope.

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

openreel-storyboardのMiniMax H3 queueをCLIで検証・生成・監視・復旧する。既存runのstatus、resume、cancelにも使う。

Produz vídeo curto — roteiro, storyboard, prompts por cena e geração via Runway quando há chave. Use quando o usuário disser "vídeo", "reels", "roteiro de vídeo", "Runway", "Higgsfield", "animação", "storyboard", "vídeo de IA". Runway gera de fato a partir de imagem; Higgsfield não tem API pública estável e segue manual. Vídeo é o item mais caro da stack.

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

Inventory, archive, and summarize PWDEV Flow project history safely. Use when the user asks to find stale artifacts, archive completed work, clean the Flow workspace without deletion, or generate a changelog from verified history.

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

Estrutura narrativa para copy — PAS, BAB, AIDA, PASTOR, Jornada do Herói e Golden Circle. Use quando o usuário disser "storytelling", "contar a história", "narrativa da marca", "o texto está sem fio condutor", "case de sucesso", ou quando a página precisar de narrativa em vez de argumento listado.

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

Generate comprehensive changelogs from Git history, commit messages, pull requests, and issue tracking for release documentation. Use when preparing releases, documenting changes, creating release notes, categorizing commits, generating version summaries, maintaining project history, or automating changelog updates.

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