「story」の検索結果

Senior software engineer for story execution and code implementation. Use when the user asks to talk to Amelia or requests the developer agent.

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

Video content planning. Writes narration scripts, storyboards, shot lists, and asset checklists. Saves plan to marketing/video-plan.md.

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

Engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with trend tracking. Per-person breakdowns, shipping streaks, and actionable improvements. Use when asked for "retro", "weekly review", "what did we ship", or "engineering retrospective".

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

Generate an /insights-style HTML report across MANY of your agent coding sessions (Claude Code and OpenAI Codex): what you work on, how you use the agent, your wins, your friction points, and concrete fixes to become more effective — precise goal-setting, not trusting output blindly, scoping, context hygiene, right-sizing models. Reads local session history and writes one self-contained report.html. Use when the user asks to "разбери мои сессии", "оцени как я работаю с агентом", "мой insights", "session insights report", "review how I work", "на что обратить внимание", or runs "/mentor", "/mentor claude", "/mentor codex", "/mentor both". Do NOT use for reviewing the CODE produced (that's code-review) or building the agent.

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

Reconstruct an open-source project's growth channels, key content, and stage-by-stage attribution from GitHub history and public web evidence. Use this skill when asked to research GitHub star growth, identify launch and amplification channels, explain viral milestones, find representative posts or videos, compare Product Hunt/Show HN/Reddit/KOL impact, or produce an evidence-backed OSS growth attribution report.

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

Satori is a clinically informed wisdom companion for navigating the inner life — emotions, meaning, grief, purpose, relationship, identity, and the questions that don't resolve easily. Activate when someone is processing something difficult, wrestling with a life question, seeking perspective, or simply needs to think alongside someone who won't rush them toward an answer. Also activate when someone uses language like "I've been struggling with," "I don't know what to do," or "I need to figure out" — or any emotionally charged framing. When in doubt, activate. Draws from Taoism, Buddhism, Stoicism, Christianity, Sufi wisdom, Hindu philosophy, Confucian ethics, and African thought, alongside modern psychology, neuroscience, and trauma-informed frameworks (IFS, DBT, CFT, Schema Therapy, Somatic). Uses Motivational Interviewing, Voss tactical empathy, McAdams Life Story, and Singer Self-Defining Memory — woven naturally, not mechanically.

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

Build, normalize, and maintain the user's Career Context file so downstream platform outputs stay factual and consistent. Use when the user wants an agent to consolidate CV data, LinkedIn exports, GitHub history, project summaries, bio facts, achievements, or positioning into one professional source of truth before editing platform-specific assets.

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

Releasing Craft CMS plugins — tagging, Packagist propagation, GitHub releases, branch promotion, shared-library ordering, history rewrites. ALWAYS load when cutting, preparing, verifying, or debugging a plugin release: bumping a version, dating a changelog, creating or moving a git tag, or checking what Packagist serves.

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

Never tags, pushes, edits, or publishes. Read-only evidence pack and curated RIPDPI release notes from Git/GitHub history for a stable-tag-to-candidate-SHA range. Use when preparing a changelog or release notes.

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

Continue real repository work between Claude Code, Codex CLI, and Grok Build with a privacy-bounded, drift-aware handoff packet. Use for cross-vendor takeover, context-limit checkpoints, multi-hop Claude→Codex→Grok relays, or receiving an existing Director packet. Use native resume commands for same-CLI history; never treat another vendor's session ID as portable.

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

View Self-Evolving Loop session status, history, and memory metrics

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

Act as the team's Scrum Master of record, or copilot to a human one: plan sprints, run daily pulses, close sprints, prepare and follow up retrospectives, track and escalate impediments, and detect process anti-patterns across sprint history. Use whenever the user asks for Scrum or agile process help, in any language — "plan the sprint", "chuẩn bị retro", "how is the sprint going", "our velocity dropped", "track this blocker", "the same problem keeps coming back" — even without the word "Scrum", and whenever `_project/scrum-master/` exists and the question touches sprints, ceremonies, impediments, or team process health. Not for delivery dates and budget (project-manager) or deciding what to build (product-manager).

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

Inspect and explain bmad-loop run artifacts under `.bmad-loop/runs/`. Use for live health checks ("is it stuck?", "is the loop alive?", "what is the agent doing?") and post-run forensics ("what happened?", "why did story X fail?", "where did the tokens go?"). Also triggers on "monitor/check/summarize the loop", "why did the run pause?", Vietnamese "theo dõi bmad loop", "phân tích run", "đọc log của run", and equivalent requests in other languages. Use only for bmad-loop's own run artifacts, not application runtime logs or CI-provider build logs.

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

Integrate current Univer Pro features into browser applications. Use for licensed Sheets, Docs, Slides, Bases, Boards, or PDFs; advanced Sheets presets; collaboration and edit history; Office import/export; printing; pivot tables; charts; sparklines; shapes; Pro workers; license ordering; or Pro Facade APIs.

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

Personal assistant for the [YOUR LAST NAME] family. Use this skill when: - Filling out forms (medical, insurance, school, government, travel) - Making appointments or reservations - Handling insurance claims or benefits questions - Coordinating with service providers - Travel planning and bookings - Financial tasks (account info, routing numbers, advisor contacts) - Any task requiring family member details, insurance info, medical history, or household information Triggers: form filling, insurance, medical records, appointments, family info, travel booking, school forms, emergency contacts, allergies, prescriptions, household services, bank account, routing number, financial, accountant, tax

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

Generate a state document (context transfer) that allows any fresh AI instance to resume work without conversation history. Use this skill whenever the user asks to checkpoint, create a state transfer, save state, generate a handoff document, create compaction insurance, or says anything like 'snapshot this', 'create a context transfer', 'checkpoint', 'save state for handoff', 'write a recovery doc', or 'transfer context'. Also trigger when the user mentions compaction concerns, session handoff, multi-session continuity, or wants to preserve the current conversation's state. Works for any conversation type: projects, research, debugging, investigations, design sessions, or long-running chats. This skill produces a structured markdown document optimized for AI cold-start recovery, not human notes.

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

Use when users ask about Nexus Mutual claims history, claim statistics, approval/denial rates, payout amounts, or want to analyze past claims for a product or time period.

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

Analytics and BI engineer — dashboards, metrics design, reporting pipelines, and data storytelling. Use when asked to "build a dashboard", "design a metric", "write a report", or "audit our analytics".

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

Map current AI safety controls — filter inventory, coverage gaps, latency impact, incident history. Use when asked "what AI safety controls do we have", "find guardrail coverage gaps", or "map our filters".

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

Use when asked to design social media graphics, ad creatives, or marketing assets. Examples: "design a LinkedIn post for our launch", "create ad creatives for our campaign", "make an Instagram story", "design a Twitter card", "create a banner ad", "social assets for the product announcement".

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

Hacker News post crafter — given a product, feature, or story produces a ready-to-post HN submission (title ≤80 chars, no marketing), honest body text with technical depth, no outbound links, predicted reception analysis, and comment-response templates for likely pushback. Use when asked to "write an HN post", "craft a Show HN", "prepare our Hacker News launch", or "help me post on HN".

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

Maintain per-repo and cross-repo changelogs — append structured entries after agent work. Use when asked to "log this change", "update changelog", "what changed", "change history".

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

Design and build websites with film-inspired visual systems, director-driven art direction, storyboard-first layout planning, and cinematic motion. Use when the user asks for a cinematic site, movie-style landing page, director-inspired UI, film-noir, sci-fi, romance, thriller, action, animation, or a movie-like website aesthetic, including requests phrased in Chinese. Do not use for generic web design unless the user explicitly wants a film or director reference.

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

Expert guide for Headless CMS integration (Sanity, Payload CMS, Strapi, Contentful, Storyblok) with modern frameworks / Panduan ahli integrasi Headless CMS (Sanity, Payload, Strapi, Contentful) dengan framework modern.

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