「onboard」の検索結果

Drafts a DRAFT job description from a role brief, team context and the organisation's own template, in inclusive plain language, with every requirement traced to its source, unconfirmed fields marked TBC and a numbered list of items the hiring manager must confirm before posting. Use when the user asks to "write a job description", "draft the job ad", "refresh this role profile", "tidy up this vacancy notice" or "turn these notes into a job posting" from a brief, notes or an old job description. Do not use for interview questions or a scorecard from the finished job description, use interview-scorecard-builder instead; for the new hire's first 90 days, use onboarding-plan-builder. Drafts for human review; never approves, authorises or signs off.

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

Builds a DRAFT structured interview scorecard from a job description: five to eight competencies traced to it, past-behaviour and situational evidence questions with probes, four-level rating anchors written as observable behaviours, a blank scoring sheet, a panel plan and the items the hiring manager must confirm. Use when the user asks to "build an interview scorecard for this job description", "write competency questions for this role", "draft the interview guide for the panel", "set up a rating scale for the interviewers", "put together a structured interview kit" or "create a hiring rubric from the JD". Do not use for writing or fixing the job description itself, use job-description-drafter instead; for the new hire's first 90 days, use onboarding-plan-builder. Drafts for human review; never approves, authorises or signs off.

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

複雑なコードベースを体系的に分析し、アーキテクチャを可視化・ドキュメント化して新規開発者のオンボーディングを支援する汎用スキル。成果物は必ず `docs/` 配下に分割出力する。以下のリクエストで使用する：(1)「このコードベースを分析して」「全体像を教えて」など概要把握、(2)「アーキテクチャドキュメントを作って」「C4図を生成して」など設計ドキュメント生成、(3)「オンボーディング資料を作って」など新規開発者向け資料作成、(4)「技術的負債を洗い出して」など負債評価、(5)「機能一覧を出して」など機能インベントリ生成、(6)「この機能を操作したら何が起きるか追跡して」などユーザー操作フロー追跡、(7)「新機能の実装手順を出して」などフロント／バック横断の実装ガイド生成。特定の言語・フレームワーク・ディレクトリ構成に依存せず、どのリポジトリでも利用できる。

Provision a client-brand AI assistant in the NV oOS Pro Toolkit — brand intake, system-prompt authoring, tool selection, an idempotent provisioning script, credentials, and end-to-end verification. Use when creating a brand manager or social media assistant for a client brand (e.g. Aerlinn), onboarding a new brand into the Design Stack, replicating an existing brand assistant, or updating a brand assistant's prompt, tools, or campaign copy.

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

Set up a paid-media client, brand, account, data-source, privacy, and mutation-guardrail profile for Claude Ads. Use for onboarding, initial configuration, brand DNA, API tokens or credential profiles, environment-variable or keychain setup, connecting exports or read adapters, safe native or verified-local installation, curl-pipe-bash install requests, declaring KPIs, or preparing a new advertising project.

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

Product-led growth and customer-base growth for B2B SaaS. Use this skill for self-serve funnel work (activation, time-to-value, free trial vs freemium, PQL definition, in-product upgrade moments, sales-assist triggers) and for growing revenue from existing customers (adoption, expansion, churn-save, renewal marketing, net revenue retention). Also triggers on: PLG, product-led growth, activation, aha moment, time to value, free trial, freemium, PQL, product qualified lead, onboarding, self-serve, customer marketing, expansion revenue, upsell, cross-sell, churn, retention, NRR, renewal.

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

SharedPreferences (v2.5.5) for Flutter providing simple persistent key-value storage for non-sensitive user settings and app preferences. Use this skill when storing user preferences (theme mode, language selection, font size), app settings and configuration, feature flags or A/B test assignments, simple cache data, onboarding completion status, last selected values (filters, sort options), user consent flags, or any non-sensitive data that survives app restarts. Supports String, int, double, bool, and StringList types. NOT suitable for storing tokens, passwords, API keys, or any sensitive/encrypted data (use flutter_secure_storage instead). Ideal for quick persistent storage without database overhead.

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

Integrate Firecrawl into product code: SDK setup and FIRECRAWL_API_KEY onboarding, /scrape, /search and /interact endpoints. Use when an application (not the agent itself) calls Firecrawl.

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

Convert a regular/single-user app into a multi-tenant SaaS — add authentication, organizations/teams, role-based permissions (RBAC), plans & billing (Stripe / HYP-היפ / license keys / usage metering), invites and onboarding. Use when the user wants to "turn this into a SaaS", "add login/orgs/teams", "add plans and payments", "add user roles/permissions", "make this multi-tenant", "הפוך לסאאס", "להוסיף התחברות / ארגונים / הרשאות / מסלולים ותשלום".

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

Plan FriendlyBet ethical growth, SEO, README positioning, open-source contribution paths, self-hosting story, public trust, and discovery without ads, trackers, spam, or dark patterns. Use for repo-facing docs, growth strategy, launch positioning, SEO pages, contributor onboarding, or public messaging.

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

Review or design FriendlyBet user experience, visual direction, mobile-first flows, premium sports interface, Hebrew/English copy fit, RTL behavior, accessibility, interaction patterns, and product UI polish. Use when a task touches screens, flows, layout, visual hierarchy, onboarding, prediction UX, share UX, or design quality.

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

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.

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

Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.

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

Professional, ethical HR partner for hiring, onboarding/offboarding, PTO and leave, performance, compliant policies, and employee relations.

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

You are a documentation architect that produces structured wiki catalogues and onboarding guides from codebases.

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

Task sequences, progressive disclosure, and the pacing of an experience over time. Use when designing multi-step flows, evaluating onboarding, or diagnosing why users get lost.

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

Behavioral UX specialist applying choice architecture, friction audits, and commitment design to guide users toward intended actions without coercion. Use when optimizing conversion flows, onboarding, or checkout UX.

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

Bring a new machine to a verified AOS installation: read-only doctor baseline, install after GO, MCP servers wired per harness with the configs backed up first, memB and OpenWiki checks, and a second doctor run for the delta. Use for "set up this machine", "onboard a new computer", "install AOS on this laptop".

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

When the user wants to reduce churn, improve user engagement, or increase lifetime value. Also use when the user mentions "retention", "churn", "users leaving", "engagement", "DAU/MAU", "user activation", or "why are users uninstalling". For onboarding-specific issues, see app-launch. For monetization, see monetization-strategy.

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

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.

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

Control smart-home accessories and commission Matter devices using HomeKit and MatterSupport. Use when managing homes/rooms/accessories, creating action sets or triggers, reading accessory characteristics, onboarding Matter devices, or building a third-party smart-home ecosystem app.

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

Transfer app data between platforms using AppMigrationKit. Use when implementing one-time data migration from Android or other platforms to iOS, managing cross-platform transfer sessions with AppMigrationExtension, packaging and archiving user data for export, importing resources on the destination device, tracking transfer progress, handling migration errors, or building onboarding flows that import existing user data.

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

Use when someone asks to write, rewrite, review, or improve text that appears inside a product or interface. Examples: "review the UX copy", "is there a better way to phrase this", "rewrite this error message", "write copy for this screen/flow/page", reviewing button labels, improving CLI output messages, writing onboarding copy, settings descriptions, or confirmation dialogs. Trigger whenever the request involves wording shown to end users inside software — apps, web, CLI, email notifications, modals, tooltips, empty states, or alerts. Also trigger for vague requests like "review the UX" where interface copy review is implied. Do NOT trigger for content marketing, blog posts, app store listings, API docs, brand guides, cover letters, or interview questions — this is a technical writing skill for interface language.

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

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.

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