「story」の検索結果

Reference Hildegard von Bingen's Physica natural history knowledge. Covers classification of plants, stones, animals, fish, birds, elements, and trees with their medicinal, symbolic, and practical properties. Enables cross- referencing between categories and application guidance. Use when exploring a specific plant, stone, or animal from Hildegard's perspective, researching medieval natural history and cosmology, cross-referencing properties across categories, or integrating Physica knowledge into health, spiritual, or creative practice.

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

"Apply narrative research methods to understand human experience through stories, analyzing narrative structure, temporality, and meaning-making in life stories and oral histories. Use this skill when the user needs to analyze how people construct meaning through storytelling, examine narrative structure and plot, conduct life story or oral history research, or when they ask 'how do stories shape identity', 'how do I analyze a life narrative', or 'what does this story reveal about experience'.".

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

Use this skill when building or maintaining a Requirements Traceability Matrix (RTM) on a Salesforce project: one row per requirement, columns for source, user-story id(s), test-case id(s), defect id(s), sprint, release, and status. Covers forward traceability (req → story → code → test) and backward traceability (test → req). Trigger keywords: RTM, requirements traceability matrix, audit trail for salesforce delivery, traceability for steerco, deferred requirement tracking, regulatory traceability. NOT for eliciting the requirements in the first place — use admin/requirements-gathering-for-sf. NOT for user-story authoring — use admin/user-story-writing-for-salesforce. NOT for UAT test design — use admin/uat-test-case-design. NOT for Apex test design — use apex/test-class-standards. NOT for backlog prioritization — use admin/moscow-prioritization-for-sf-backlog. More triggers: traceability.md, build-layer traceability, REQ-XXX and FG-XXX id mapping, artefact-to-requirement orphan report, coverage-gap report, check_rtm.py --manifest-dir, owning run-time agent column, design decision ref column, metadata API name in a traceability row.

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

Pre-ticket Fibonacci sizing for a paste-mode batch of user stories. Default mode is advisory-only (writes a Story Sizing Report). Opt-in `--auto-create` delegates ticket creation to mk:jira-issue + mk:jira-collaborate with mandatory dry-run + single batch confirmation gate. NOT for single-ticket estimation (mk:jira-estimator); NOT for sprint capacity (mk:planning-engine).

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

Use when verifying a story or ticket implementation against its spec and acceptance criteria - per-AC verdicts with file:line evidence and proving tests, code reuse and design conformance, dead code, stale docs, comment discipline. Finds the spec from an explicit path, the ticket key in the branch name, or plan files - and asks rather than guessing. For defect-hunting code review use dotnet-techne-code-review instead. Keywords: story QA, acceptance criteria, spec conformance, AC coverage, definition of done, dead code check, reuse check, comment check, verify story, QA this branch.

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

Write acceptance criteria for a Jira story using Given/When/Then scenarios. Use this skill when the user asks to write AC, acceptance criteria, write scenarios, improve a story, add AC to a ticket, or mentions a Jira ticket and wants better requirements. Also triggers on "write better AC", "this story needs AC", "add scenarios to this ticket", or when reviewing a Jira story for completeness.

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

Split user stories into smaller, independently deliverable slices using the SPIDR method (Spike, Path, Interface, Data, Rules). Use this skill whenever the user asks to split a story, break down work, slice a story, asks "can this be split", mentions "SPIDR", says "story splitting", or wants to decompose a large ticket into smaller pieces. Also trigger when a user presents a story that seems too large for a single sprint and asks for help sizing or scoping it.

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

View publication history for catalog resources — who changed what and when. Use when investigating timeline of changes, finding who modified a connector, or correlating changes across capture/collection/materialization chains. Use when user says "what changed", "who changed", "publication history", "catalog history", "when was it published", "timeline of changes", or "what happened to my connector".

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

Monta peças verticais 9:16 — story, reels, shorts, TikTok — respeitando as áreas seguras da interface. Use quando o usuário disser "story", "reels", "shorts", "vertical", "9:16", "TikTok", "capa de reels", "template de story". A restrição dominante aqui é a UI do app, que cobre topo, base e lateral.

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

WhatsAppの相手やグループへのメッセージ・ファイル送信と、履歴の同期・検索をエージェントに頼めます。宛先や期間を指定して過去のやり取りも探せます。

• WhatsAppの相手に伝言したいとき
• グループにファイルを共有したいとき
• キーワードと期間で履歴を探したいとき

OpenClawのGit履歴からリリース用の変更履歴を作り直します。利用者に関わる変更をまとめ、Issue・PRへの参照や貢献者の記載漏れを検証します。

• stable版公開前の変更履歴作成
• 前回のbeta版からの差分整理
• 貢献者とPR参照の記載確認

Finds or publishes a pkg.pr.new canary release for a Storybook branch. Use when the user wants the canary package specifier for a branch or needs to trigger the canary workflow manually.

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

Creates a pull request following Storybook conventions. Use when creating PRs, opening pull requests, or submitting changes for review.

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

Review, improve, rewrite, author, or plan Storybook documentation in /docs. Use this when asked to review docs, improve a page, rewrite documentation, draft new docs, or advise on docs strategy.

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

Recomputes Storybook browser support floors from Plausible /docs usage, writes pinned versions, and opens a PR. Use only when a human explicitly applies this skill.

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

Write the changelog entry for a new minor or major Storybook release. Use when preparing a CHANGELOG.md entry for a X.Y.0 version.

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

Use this skill when Storybook is already installed and the user wants a working `preview` file and stories for real components.

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

Use this skill when Storybook exists but needs an upgrade.

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

Drive and test terminal apps (especially the Cline CLI TUI in apps/cli) through tuistory — named background PTY sessions that agents can read, wait on, snapshot, screenshot, and type into. Like Playwright/tmux for terminals, with reactive waiting instead of blind `sleep`. Use this skill when you need to: - Manually test or reproduce bugs in the interactive Cline TUI (`bun run cli -i`) from a headless environment - Run a dev server or any long-lived/interactive process in the background without hanging your tool call - Write or extend Playwright-style e2e tests for the TUI (`bun run test:e2e:tuistory` in apps/cli) - Capture text snapshots or styled PNG screenshots of a TUI screen as evidence

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

Parse Windows Prefetch files (versions 17, 23, 26, 30) with tools like PECmd, WinPrefetchView, or python-prefetch to determine program execution history, including run counts, execution timestamps, and referenced files/DLLs. Use when building a timeline of program execution on a Windows system, confirming whether a suspicious binary ran, or correlating execution evidence with other forensic artifacts during an investigation.

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

Correlate Windows registry keys (USBSTOR, MountedDevices), Event Logs, and setupapi.dev.log to reconstruct USB device connection history, first/last-plugged timestamps, and drive letter mappings. Use when investigating removable media usage, tracking device provenance, or building a timeline for suspected data exfiltration.

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

Expert in building immersive scroll-driven experiences - parallax storytelling, scroll animations, interactive narratives, and cinematic web experiences. Like NY Times interactives, Apple product pages, and award-winning web experiences. Makes websites feel like experiences, not just pages. Use when: scroll animation, parallax, scroll storytelling, interactive story, cinematic website.

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

Summarizes WeChat group chat highlights into a structured digest using the local wx-cli binary (https://github.com/jackwener/wx-cli). Generates a normal digest by default; a roast (毒舌) version is opt-in. Maintains per-group history (history.json + history-digests.jsonl), per-user profiles, and per-group fact memory (memory.md) across runs, with privacy guardrails baked in. Use when the user asks to "总结群聊", "群聊精华", "群聊摘要", "summarize group chat", "group chat digest", mentions a WeChat group name with a time range, says "帮我看看 XX 群最近聊了什么", "XX 群有什么值得看的", or asks to "回溯画像" / "初始化画像" / "backfill profiles". Adds the roast version when the user says "毒舌版", "roast 版", "再来个毒舌的", or similar.

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

Turn an article, case study, brand narrative, product journey, or long-form story into a cinematic scroll-driven landing page using one of three renderers: scrubbed video, a real-time Three.js world, or semantic HTML/SVG data and typography. Use when the user asks for a scroll world, fly-through landing page, article-to-website transformation, animated planet, data scrollytelling, video-scrubbed page, connected visual journey, or story-led alternative to ordinary stacked sections.

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