1,872 件 ・ 関連度順
概要と使いどころ
Generate or update CHANGELOG.md from git history. Parses conventional commits, groups by version tags, categorizes into Added/Fixed/Changed/Breaking sections using keep-a-changelog format, and creates comparison links. Use when you need to create a changelog, update release notes, document version history, or prepare release documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Write user stories with acceptance criteria. Use when the user says "write user stories", "convert this to stories", "create acceptance criteria", "break this into tickets", "story map", "walking skeleton", "story for this feature", or wants to translate a feature idea into sprint-ready items - even if they don't explicitly say "user stories".
日本語の概要は準備中です。原文の説明を表示しています。
Write personalized pitch emails to journalists, podcasters, newsletter writers, and analysts using AIDA adapted for media pitching and Ryan Holiday's journalist psychology from "Trust Me I'm Lying." Different from press releases (use /press-release-writer for those). Use when the user asks to pitch a journalist, pitch a reporter, "get coverage in X", media outreach, podcast pitch, analyst briefing request, or wants to land a story. Reads brand voice and positioning from knowledge/. For the press release itself, see press-release-writer. For the underlying customer story, see case-study-writer.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user says "write my pitch", "help me tell my startup story", "craft my investor narrative", "why now slide", "what's our secret", "how do I explain what we do", "make my pitch compelling", "pitch deck story", "elevator pitch", "why will we win", "contrarian insight", or wants to build a persuasive, coherent narrative around their startup for investors, press, or recruiting.
日本語の概要は準備中です。原文の説明を表示しています。
Communicate data insights to non-technical stakeholders in a structured, persuasive format. Use when the user says "present these findings", "explain this analysis to leadership", "make a data presentation", "tell the story behind the data", "translate this into a business narrative", "make this insight actionable", "stakeholder readout", "executive summary of results", or needs to turn analysis output into a decision-ready document or slide deck.
日本語の概要は準備中です。原文の説明を表示しています。
Use when practitioners need to understand system-managed fields (CreatedDate, LastModifiedDate, SystemModstamp, CreatedById, LastModifiedById, IsDeleted) — their update behavior, indexing, and queryability. Triggers: 'difference between SystemModstamp and LastModifiedDate', 'how to query deleted records', 'set CreatedDate during data migration', 'why does LastModifiedDate not match SystemModstamp', 'Create Audit Fields permission'. NOT for a field's value-change history — use data/field-history-tracking. NOT for Shield Field Audit Trail — use security/field-audit-trail.
日本語の概要は準備中です。原文の説明を表示しています。
Eliciting, documenting and structuring requirements for a Salesforce implementation: stakeholder discovery interviews, As-Is and To-Be process mapping, and gap analysis against standard Salesforce capability. Trigger keywords: requirements gathering, user story, As-Is To-Be, gap analysis, stakeholder interview, process mapping, business requirements, fit gap. NOT for authoring the user stories themselves - use admin/user-story-writing-for-salesforce. NOT for scoring requirements against a specific org - use admin/fit-gap-analysis-against-org. NOT for technical design decisions - use architect/solution-design-patterns. Also covers the requirements catalogue itself (one row per requirement, MoSCoW priority, source stakeholder, downstream target) and Salesforce non-functional requirements: record volume, sharing layer, integration pattern, reporting joins, mobile/offline, and licence implication.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when prioritizing a Salesforce backlog with the MoSCoW method (Must / Should / Could / Won't) plus an effort + value lens, deciding what fits in the next sprint or release, and using WSJF as a tie-break when MoSCoW alone produces ties. Trigger keywords: MoSCoW prioritization, must should could won't, WSJF salesforce, prioritize salesforce stories, sprint commit, backlog grooming. NOT for story writing or splitting (use admin/user-story-writing-for-salesforce). NOT for release train planning (use agents/release-train-planner). NOT for sizing/estimation method debates — this skill assumes a sizing convention is already in place.
日本語の概要は準備中です。原文の説明を表示しています。
Use when setting up or auditing a dedicated Salesforce integration user — Salesforce Integration user license, API-only profile, permission set layering, MFA waiver, and login monitoring. NOT for creating human users, roles, or login hours — use admin/user-management. NOT for login IP ranges, session lifetime, or OAuth client-credential hardening — use security/api-only-user-hardening. Trigger keywords: service account, API-only user, run-as user, client credentials execution user, LoginHistory, REQUEST_LIMIT_EXCEEDED, integration login failure.
日本語の概要は準備中です。原文の説明を表示しています。
Expert in narrative structure, character development, plot pacing, and compelling storytelling
日本語の概要は準備中です。原文の説明を表示しています。
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas.
日本語の概要は準備中です。原文の説明を表示しています。
Record final outcomes to history.md, not intermediate requests or reversed decisions
日本語の概要は準備中です。原文の説明を表示しています。
Performs manual testing of Story AC via executable bash scripts saved to tests/manual/. Creates reusable test suites per Story.
日本語の概要は準備中です。原文の説明を表示しています。
rescue 브랜치 history-only 보존 후 삭제 검증
日本語の概要は準備中です。原文の説明を表示しています。
Sparkle Design の UI コンポーネントを shadcn registry 経由でプロジェクトに追加するスキル。 パッケージマネージャの自動検出、設定バリデーション、コンポーネントインストール、 Storybook 統合、CSS セットアップ、トラブルシューティングをカバーする。 「Sparkle コンポーネントを追加」「sparkle-design のコンポーネントをインストール」 「@sparkle-design のセットアップ」「コンポーネントをどう追加する」 「registry の設定」「components.json の設定」への言及で発動する。 English: "add a sparkle button", "install sparkle-design card", "add @sparkle-design/input", "set up components from sparkle registry", "how do I install components", "registry setup"
Expert in turning data visualizations into compelling video and animation content for social media and marketing. Activate on: data commercial, animated chart, data storytelling video, chart animation, Remotion data video, Motion Canvas, Flourish animation, D3 animation, data viz social media, dashboard recording, data narrative video. NOT for: static data visualization (use data-viz-2025), general video editing (use video-processing-editing), full video production pipeline (use ai-video-production-master).
日本語の概要は準備中です。原文の説明を表示しています。
Learns from DAG execution history to improve future performance. Identifies successful patterns, detects anti-patterns, and provides recommendations. Activate on 'learn patterns', 'execution patterns', 'what worked', 'optimize based on history', 'pattern analysis'. NOT for failure analysis (use dag-failure-analyzer) or performance profiling (use dag-performance-profiler).
日本語の概要は準備中です。原文の説明を表示しています。
Agile product ownership toolkit for Senior Product Owner including INVEST-compliant user story generation, sprint planning, backlog management, and velocity tracking. Use for story writing, sprint planning, stakeholder communication, and agile ceremonies.
日本語の概要は準備中です。原文の説明を表示しています。
This skill guides evaluation for malignancy using imaging in patients with a history of adrenal adenoma (post‑adrenalectomy Cushing’s syndrome) when the adenoma demonstrates a CT density of ≥10 Hounsfield units or when pathology is consistent with possible carcinoma. Trigger phrases include “CT density ≥10 HU”, “possible carcinoma on pathology”, and “post‑adrenalectomy CS patient with adrenal adenoma history”.
日本語の概要は準備中です。原文の説明を表示しています。
Agile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking. Use when writing user stories, creating acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing the backlog.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a component library needs a workshop — one story per concept, JSDoc summaries the manifest can carry, stories run as tests, and an opt-in MCP channel that replaces guessing with querying.
日本語の概要は準備中です。原文の説明を表示しています。
Use when choosing HOW to record change history / audit trails — walks the tier matrix (columns → audit log → temporal → event sourcing). Triggers on 'wer hat was wann', 'audit log'.
日本語の概要は準備中です。原文の説明を表示しています。
Define a brand identity constraint set from a confirmed strategy — colour story, type story, logo direction, imagery direction. Defines the tokens that token emission and asset generation consume.
日本語の概要は準備中です。原文の説明を表示しています。
Especialista em construir experiências imersivas baseadas em scroll - storytelling por paralaxe, animações de scroll, narrativas interativas e experiências web cinematográficas. Como as interativas do NY Times, páginas de produtos da Apple e experiências web premiadas. Torna websites em experiências, não apenas páginas. Use quando: animação de scroll, paralaxe, storytelling de scroll, história interativa, website cinematográfico.
日本語の概要は準備中です。原文の説明を表示しています。