「onboarding」の検索結果

Main entry point for the Show Me The Money business automation suite. Dual mode: pre-task routing (which skill fits your problem) + post-task navigation (a skill just finished — what's next). Use when the user wants to start a business, automate operations, generate revenue, find product ideas, set up marketing, or run any business function autonomously. Also use when the user says 'show me the money', '来财' (the suite's Chinese name), 'make money', 'start a business', 'automate my business', 'build a company', 'what's next', or '下一步怎么走'. Includes a beginner tutorial mode triggered by '/money onboarding', '/money tutorial', '/money 新手', '/money 教程', 'how do I use this', or '这个怎么用' — a zero-input guided walkthrough that produces a demo business brief.

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

Set up bundle IDs, capabilities, signing certificates, provisioning profiles, and encrypted signing sync with the asc cli. Use when onboarding a new app, rotating signing assets, or sharing them across a team.

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

Understand this repository quickly before making changes. Use for architecture discovery, ownership mapping, command selection, and initial implementation planning.

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

Inspect and install CCAM monitoring hooks for Claude Code and Codex. Use when onboarding a provider, repairing missing hooks, checking which provider is active, or validating that installation preserved unrelated user hooks.

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

Onboard quickly to this repository. Use when asked to understand architecture, locate ownership, choose the right module, or identify the correct commands and verification strategy before coding.

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

Generate project documentation from codebase analysis — ARCHITECTURE.md, API_ENDPOINTS.md, DATABASE_SCHEMA.md. Reads source code, schema files, routes, and config to produce accurate, structured docs. Use when starting a project, onboarding contributors, or when docs are missing or stale. Triggers: 'generate docs', 'document architecture', 'create api docs', 'document schema', 'project documentation', 'write architecture doc'.

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

Write copy following Sentry brand guidelines. Use when writing UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing copy, or any user-facing content. Covers both Plain Speech (default) and Sentry Voice tones.

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

Friendly, jargon-free onboarding for people new to coding agents and Power BI agentic development. Invoke for setup, prerequisites, tool installation, terminal guidance, safety questions, or explanations of models, context, prompts, tools, and environments. Use setup mode for concise installation help, explain mode for guided learning, and improve-my-agent-setup for an existing setup audit.

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

Design and build complete web experiences from scratch — award-level product and marketing pages, cinematic scroll-directed sites where the page is directed like a film, and multi-screen products (app, dashboard, admin, settings, onboarding, docs site) built as one design system with every component, state and route in one style. Use whenever the user wants to create or redesign a landing page, website, hero section, portfolio, promo or product page; wants scroll animations, storytelling pages, or a site that feels like a movie; or says "make it beautiful", "make it wow", "cinematic", or "design system" — even if they name no technique. Generates its own assets via local CLIs (images, video frames, depth maps, 3D), and gates every ship with an executable anti-slop linter and a screenshot verification loop. Not for polishing a UI someone else built, and not for backend-only work.

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

Designing forms with multiple steps, progress indicators, conditional logic, and save-and-resume mechanics. The discipline of breaking complex data collection into stages that respect cognitive load while maintaining completion intent. Honest about kitchen-sink-single-page (overwhelms before the user starts), progress-theater (steps without genuine staging), and genuinely-staged (each step earns its own page) patterns. Triggers on multi-step form, multi-page form, form wizard, signup wizard, lead form, application form, intake form, configurator, onboarding form. Also triggers when a long form is converting poorly, when an audience is dropping off mid-form, or when a multi-step form is being scoped for the first time.

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

Design and run a documentation system for a team or product. Use this skill when planning what to document, choosing a documentation tool, organizing existing docs, fixing stale documentation, designing a maintenance cadence, or scoping technical writing work. Triggers on documentation, docs, tech writing, knowledge base, wiki, runbook, README, internal docs, doc audit, doc maintenance, stale docs, where do we document. Also triggers when the team is repeatedly answering the same questions or when onboarding takes too long.

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

Guided project onboarding flow

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

New team member onboarding

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

Design and write email automation sequences (welcome/onboarding, nurture, re-engagement, trial expiration, sales) for SaaS and B2B, with subject lines, copy, CTAs, and timing. Use when building drip campaigns or designing lifecycle email.

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

Design cross-channel journeys as state machines, simulation-tested before build. "map the onboarding journey"

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

When the user wants to optimize, improve, or increase conversions on any marketing page or form — including homepage, landing pages, pricing pages, feature pages, lead capture forms, or contact forms. Also use when the user says 'CRO,' 'conversion rate optimization,' 'this page isn't converting,' 'improve conversions,' 'why isn't this page working,' 'my landing page sucks,' 'form abandonment,' 'nobody's converting,' 'low conversion rate,' or 'this page needs work.' Use this even if the user just shares a URL and asks for feedback. For signup/registration flows, see signup. For post-signup activation, see onboarding. For popups/modals, see popups.

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

When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product. Also use when the user mentions "marketing plan," "growth plan," "GTM plan," "go-to-market plan," "AARRR plan," "90-day marketing plan," "12-month marketing roadmap," "fractional CMO plan," or "fCMO plan." Generates an exhaustive 13-section plan structured by AARRR (Acquisition, Activation, Retention, Referral, Revenue), customized to the client's current budget, team, and stage, mapped to future funding milestones, cross-referenced with the 139-idea marketing-ideas library and an embedded 17-section current-state audit rubric, with a full marketing operations stack showing which skills and MCP/API integrations execute each part. Outputs a Notion-paste-ready markdown document. For positioning and ICP context before planning, see product-marketing. For stage-specific deep work, see onboarding, signup, emails, referrals, pricing.

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

Risk-based vendor assessment framework for IT service providers, technology vendors, and third-party partners under DORA, NIS2, GDPR. Provides three-phase process (Initial Screening / Detailed Assessment / Final Evaluation), six-dimension risk scoring (Financial/Operational/Compliance/Security/Reputational/Strategic) with weighted matrices, full DORA Art. 28-30 contractual checklist, NIS2 Art. 21(2) security measures enumeration, GDPR Art. 28 documentation checks, red flags per dimension, trigger-based review criteria, and document templates. Use when: (1) Evaluating new vendors or technology providers, (2) Conducting critical ICT third-party due diligence under DORA, (3) Performing supply chain security assessment under NIS2, (4) Creating vendor onboarding documentation, (5) Establishing ongoing vendor monitoring, (6) Assessing concentration risk, or (7) Generating executive vendor risk reports.

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

Screen a client, counterparty, payer or corporate against the sanctions lists published by the designating authorities themselves — the UK Sanctions List (FCDO), OFSI, the UN Security Council, the EU consolidated list and OFAC's SDN and non-SDN lists. Use when onboarding, before taking a payment, before completing a transaction, or whenever a name must be checked against sanctions. Produces candidates and provenance, never a clearance: the record names every list searched with its publication date and count, states what was NOT searched, and ends at a blank decision block. Fails closed — a cache that is missing, damaged, truncated or stale is reported NOT SEARCHED and the process exits non-zero, so nothing can read an incomplete run as clean. Matches across transliteration, diacritics, homoglyphs and initials, because nobody spells a name the way the publisher does. Standard library only; screening opens no network connection.

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

End-to-end external local counsel lifecycle management for multi-jurisdiction legal matters. LC selection criteria and capability assessment, engagement setup and instruction design, performance monitoring and check-in cadence, scope enforcement, and relationship escalation. Use when selecting local counsel for a jurisdiction, designing LC instructions, managing the LC check-in rhythm, enforcing scope boundaries when LC signals overreach, or escalating a performance or relationship issue beyond the matter team. Trigger on: 'which LC should we use', 'LC instruction', 'brief the local counsel', 'LC hasn't responded', 'LC is going off scope', 'LC scope dispute', 'confirm scope with LC', 'LC check-in', 'LC is slow', 'monitor the LC network', 'LC engagement letter', 'LC selection', 'what should we tell the local counsel', 'LC onboarding', 'LC performance issue', 'LC relationship problem'.

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

AI co-counsel for divorce and family-law attorneys — a jurisdiction-portable scaffold spanning the full matter lifecycle. Eight operating modes mirror how a matter actually moves: intake and onboarding, financial disclosure, children and support, property division and QDRO, discovery and document review, drafting, negotiation and mediation prep, and court prep — plus post-judgment modification and enforcement. The methodology is jurisdiction-agnostic: it forces real, verifiable research for every local form, formula, or rule rather than inventing one, handling common-law, community-property, civil-law, and MENA personal-status regimes as variables. Built around one non-negotiable: privilege. It drafts, analyzes, organizes, and pressure-tests. It is not the lawyer.

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

An animated step indicator fills as you advance — clear progress for a multi-step flow (checkout, onboarding). One per flow. Under prefers-reduced-motion fills without easing.

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

When the user wants to optimize, improve, or increase conversions on any marketing page — including homepage, landing pages, pricing pages, feature pages, or blog posts. Also use when the user says "CRO," "conversion rate optimization," "this page isn't converting," "improve conversions," or "why isn't this page working." For signup/registration flows, see signup-flow-cro. For post-signup activation, see onboarding-cro. For forms outside of signup, see form-cro. For popups/modals, see popup-cro.

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

Generates guided first-action flows that help users achieve a meaningful result within 60 seconds to boost retention. Use when user wants quick win onboarding, time-to-value optimization, or first success moments.

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