2,777 件 ・ 関連度順
概要と使いどころ
Use this skill to write or revise a README.md for a Shipfox workspace package (libs/*, tools/*). It applies the shared package README standard and repository prose policy. Trigger on write a README, draft README, rewrite README, document this package, or improve the README.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a Changeset file for the current branch using Shipfox agent automation. Trigger when the user asks to add a Changeset, document a change for release, bump versions, or prepare a PR that touches published packages.
日本語の概要は準備中です。原文の説明を表示しています。
ALWAYS use this skill when creating pull requests. Applies Shipfox agent sequencing for GitHub CLI review preparation and pull-request creation. Trigger on create PR, open PR, submit PR, make PR, push and create PR, or prepare changes for review.
日本語の概要は準備中です。原文の説明を表示しています。
Use when setting up a Shipfox workflow from a template.
日本語の概要は準備中です。原文の説明を表示しています。
Use when running a validated local Shipfox workflow change against a real trigger and inspecting its effects.
日本語の概要は準備中です。原文の説明を表示しています。
Use when checking a local Shipfox workflow change without starting a run.
日本語の概要は準備中です。原文の説明を表示しています。
ALWAYS use this skill when committing changes. Applies Shipfox agent sequencing for branch checks, scoped validation, and commit creation. Trigger on commit, commit changes, save changes, make a commit, or create commit.
日本語の概要は準備中です。原文の説明を表示しています。
Use when diagnosing a failed or stalled Shipfox workflow run, or an event that did not start one.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing a Shipfox workflow from an idea or adapting an existing workflow without a template.
日本語の概要は準備中です。原文の説明を表示しています。
Writes, reviews, and debugs idiomatic Rust code with memory safety and zero-cost abstractions. Implements ownership patterns, manages lifetimes, designs trait hierarchies, builds async applications with tokio, and structures error handling with Result/Option. Use when building Rust applications, solving ownership or borrowing issues, designing trait-based APIs, implementing async/await concurrency, creating FFI bindings, or optimizing for performance and memory safety. Invoke for Rust, Cargo, ownership, borrowing, lifetimes, async Rust, tokio, zero-cost abstractions, memory safety, systems programming.
日本語の概要は準備中です。原文の説明を表示しています。
Navigate a new leadership role using Michael Watkins' First 90 Days 30/60/90 framework. Use when someone says "I just started a new role", "I'm starting as a new manager", "I joined a new company as a leader", "I was just promoted", "how do I onboard as a leader", "what should I do in my first 30 days", "I inherited a team", "I need a 90 day plan", or "I'm new to this team". Also trigger when someone describes feeling overwhelmed in a new leadership role, unsure where to start, or tempted to make changes too quickly before they've listened. Applies to first-time managers, leaders joining new companies, and leaders moving into new functions or teams within the same company.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing nonprofit fundraising lifecycle stages, donor pipeline workflows, cultivation-to-stewardship cycles, or Salesforce Opportunity sales process configuration for NPSP or Nonprofit Cloud. Trigger keywords: fundraising lifecycle, donor pipeline, cultivation stage, solicitation workflow, major gift process, moves management, NPSP Opportunity stages, stewardship cycle, NPC fundraising stages. NOT for lapsed donor re-engagement or portfolio segmentation — use admin/donor-lifecycle-requirements. NOT for Engagement Plan setup — use admin/npsp-engagement-plans.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when configuring Salesforce B2B or D2C Commerce checkout: payment methods, shipping/tax integration, guest checkout, order summary setup, and CartCheckoutSession state orchestration. Trigger keywords: checkout flow, payment adapter, shipping tax integration, guest checkout, order summary, CartCheckoutSession, Managed Checkout, Commerce checkout flow. NOT for deciding the checkout design before build (LWR vs Aura) — use admin/commerce-checkout-flow-design. NOT for writing the CommercePayments adapter class — use apex/commerce-payment-integration.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when designing the checkout experience for a Salesforce B2B or D2C Commerce storefront — covering runtime model selection (LWR Managed Checkout vs Aura Flow Builder), cart and line-item requirements, payment option scoping, shipping rule definition, and guest vs. registered buyer experience design. Trigger keywords: checkout flow design, checkout UX requirements, LWR vs Aura checkout, guest checkout design, payment options design, shipping rules, checkout experience planning. NOT for configuring the checkout in Setup once designed — use admin/commerce-checkout-configuration. NOT for choosing B2B vs D2C Commerce — use admin/b2b-vs-b2c-requirements.
日本語の概要は準備中です。原文の説明を表示しています。
Ship workflow: prepare stages/commits locally; release pushes + opens a PR; publish handles issues + versioning. Use for 'ship', 'push', 'create a PR'. Official (→main) and beta (→dev) modes.
日本語の概要は準備中です。原文の説明を表示しています。
Manage JIRA issue relationships via jira-as: link, unlink, blockers, dependencies, clone, bulk-link. NOT sprint/epic relationships (mk:jira-agile).
日本語の概要は準備中です。原文の説明を表示しています。
发布上线：PR only（建 PR 即停）或 Full ship（合并 PR + 同步本地基础分支）；测试失败不发布、不 force push，状态汇报严格区分提交/推送/合并/部署。 触发方式：用户说"ship"、"发布"、"合并上线"、"发 PR"。
日本語の概要は準備中です。原文の説明を表示しています。
GStack ship method for final landing, PR, changelog, release, and deploy readiness checklists when the user explicitly wants to ship.
日本語の概要は準備中です。原文の説明を表示しています。
Use when advising, planning, reviewing, reporting, operating, or improving CTO and technology leadership work across strategy, cybersecurity management, SME/COE, functional and technical requirements, framework selection, people, organization, delivery, risk, KPI, roadmap, budgeting, governance, audit, R&D, stakeholder communication, culture, politics, and sector-specific leadership.
日本語の概要は準備中です。原文の説明を表示しています。
Reads one export transaction, order or shipment description and returns a DRAFT export review pack: parties to screen with a screening checklist, an item classification worksheet, a red-flag review, licence-determination questions and open items. Use when the user asks to "prepare the export review for this order", "pre-check this shipment for export control", "who do we need to screen on this deal", "build the classification worksheet for this item" or "assemble the trade-compliance file for this technology transfer". Do not use for vendor security or due-diligence screening of a supplier's questionnaire answers; use vendor-risk-screening-brief instead. Never classifies, screens, clears, decides licence need or releases a shipment; trade compliance does. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says 'co-marketing,' 'partner marketing,' 'joint campaign,' 'who should we partner with,' 'integration marketing,' 'cross-promotion,' 'collaborate with another company,' 'partnership ideas,' or 'co-brand.' For customer referral programs, see referrals. For launch-specific partnerships, see launch.
日本語の概要は準備中です。原文の説明を表示しています。
Ensure designs define data flow, state ownership, consistency boundaries, and cross-boundary writes to prevent drift and incidents.
日本語の概要は準備中です。原文の説明を表示しています。
Pre-ship framing and the technical release gate, with approvals under the go-gate rules. Generated from plugin-commands.json; invoke as $bdb-aos:shipping.
日本語の概要は準備中です。原文の説明を表示しています。
BDB Shipping Godmode, the final gatekeeper for production releases. Use when running pre-launch checks, feature-flag rollouts, or rollback planning under Spec-Driven Development before a release ships.
日本語の概要は準備中です。原文の説明を表示しています。