「bus」の検索結果

Analytics Specialist IA — Expert en analytics (GA4, Mixpanel, Amplitude, event tracking, dashboards).

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

A/B Testing Specialist IA — Expert en tests A/B (hypothèses, significativité, multivarié, culture d'expérimentation).

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

Agency builder — Positionnement, offres, pricing, recrutement freelances, processus de livraison

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

Build resilient applications with robust error handling strategies that gracefully handle failures and provide excellent debugging experiences.

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

Generate comprehensive market opportunity analysis with TAM/SAM/SOM calculations

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

Comprehensive guide to tracking, calculating, and optimizing key performance metrics for different startup business models from seed through Series A.

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

Create detailed 3-5 year financial model with revenue, costs, cash flow, and scenarios

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

Expert startup business analyst specializing in market sizing, financial modeling, competitive analysis, and strategic planning for early-stage companies.

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

Expert data scientist for advanced analytics, machine learning, and statistical modeling. Handles complex data analysis, predictive modeling, and business intelligence.

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

Use taste as a competitive moat and business advantage. In the AI and vibe-coding era, execution is commoditized. Taste is the defensible edge. Use when advising founders on product differentiation, building product culture, evaluating why some products win despite fewer features, or understanding taste as a strategic asset.

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

Alternative Slowbar coffee intelligence — scientific analysis from seed to cup using First Principle + System Thinking. Covers: varieties, terroir, cultivation, disease diagnosis, processing, roasting physics/chemistry, extraction science, brewing, business strategy, storytelling. ALWAYS trigger for coffee-related questions requiring scientific depth. DO NOT trigger for simple recipes or general food questions. Style: science-driven, farmer-first, quality-obsessed.

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

Build a tdmcp TouchDesigner-bridge vertical slice the house way — promote an op from /api/exec to a first-class REST endpoint (e.g. POST /api/connect, GET /api/logs, node_detail flags), add its typed method in src/td-client/touchDesignerClient.ts, its Zod envelope in src/td-client/validators.ts, rewire the tool(s) to prefer the endpoint with an exec fallback, and write py_compile + td/tests unittest + offline msw client tests. Use when adding/changing a bridge REST endpoint, editing td/, extending node_detail/get_bridge_logs, promoting connect/disconnect/param-modes/DAT-text off exec, or doing any exec→REST work — especially the td-depth bridge-robustness backlog. Honors probe-live discipline when TouchDesigner is offline.

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

Expert capability for robust, stealthy, and efficient browser automation using Playwright Go.

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

Generate Japanese PDFs using reportlab or fpdf2 with CJK font embedding, vertical text, business document templates, and inkan image placement. Triggers on requests to create 日本語PDF, 請求書PDF, 領収書PDF, PDF帳票, 縦書きPDF.

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

When the user wants to optimize their subscription business end-to-end — from trial start through renewal, cancellation, and win-back. Use when the user mentions "subscription lifecycle", "trial conversion", "churn", "cancellation", "win-back", "lapsed subscribers", "dunning", "billing retry", "grace period", "renewal rate", "subscriber LTV", or "resubscribe". For paywall design and pricing strategy, see monetization-strategy. For subscription analytics dashboards, see app-analytics.

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

Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready. Use when the user asks to harden, make production-ready, handle edge cases, add error states, or fix overflow and i18n issues.

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

Use when: investigating a legacy, inherited, third-party-built, or otherwise newly-unfamiliar codebase before scoping a migration or major refactor. Formalizes a repeatable five-step investigation pass — entry-point census, business-rule classification, side-effect/idempotency cataloging, implicit-contract discovery, semantic-duplication detection — plus a canonical per-project Open Questions document. Requires checkable signals: ticket keywords or prior documentation gaps. Not a mandatory gate;

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

Use when: analysing a project's test health — coverage, robustness, and CI integration.

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

Use when: investigating a legacy, inherited, third-party-built, or otherwise newly-unfamiliar codebase before scoping a migration or major refactor. Formalizes a repeatable five-step investigation pass — entry-point census, business-rule classification, side-effect/idempotency cataloging, implicit-contract discovery, semantic-duplication detection — plus a canonical per-project Open Questions document. Requires checkable signals: ticket keywords or prior documentation gaps. Not a mandatory gate; reserved for entry-point-heavy work in code areas with no prior investigation record.

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

Use when: UI standards discovery, UI pattern research, UI audit, pre-handoff UI state coverage review, or when a business-specific child skill needs a stack-agnostic UI methodology to load first.

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

Use immediately after RBR confirms a root cause and a fix is scoped, before considering the finding complete. Checks whether the confirmed defect is one instance of a structurally identical pattern elsewhere in the same file family, workflow, or business-domain area, and folds in or explicitly defers every other instance found. Mandatory for Architect and CAO — not an optional lens the agent judges when to apply.

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

No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points. This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power

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

Build communication features with Twilio: SMS messaging, voice calls, WhatsApp Business API, and user verification (2FA). Covers the full spectrum from simple notifications to complex IVR systems and multi-channel authentication. Critical focus on compliance, rate limits, and error handling. Use when: twilio, send SMS, text message, voice call, phone verification.

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

This skill should be used when the user asks to "escalate privileges", "get root access", "become administrator", "privesc techniques", "abuse sudo", "exploit SUID binaries", "Kerberoasting", "pass-the-ticket", "token impersonation", or needs guidance on post-exploitation privilege escalation for Linux or Windows systems.

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