「uis」の検索結果

Builds lead generation systems using Alex Hormozi's Core Four framework (warm outreach, content, cold outreach, paid ads), lead magnets, and Rule of 100. Use when designing customer acquisition, scaling advertising, choosing marketing channels for revenue stage, building referral programs, or fixing low lead flow. Covers lead magnets, LTGP:CAC math, More Better New scaling, and Lead Getters (referrals, employees, agencies, affiliates).

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

Applies the Bullseye Framework from Traction by Gabriel Weinberg and Justin Mares. Use when choosing growth channels, testing customer acquisition strategies, or deciding where to spend marketing effort. Covers all 19 traction channels with selection methodology, testing protocol, and phase-matched channel advice. Triggers include 'how do we get customers', 'which marketing channel should we use', 'we have a product but no users', 'our growth has stalled', 'should we do content marketing or paid ads', 'how do we test traction channels', 'what channels work at our stage'. NOT for product development (use Lean Startup), not for positioning/messaging (use Obviously Awesome), not for pricing (use Monetizing Innovation), not for enterprise sales methodology (use SPIN Selling).

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

Designs a deliberate sequence of offers (attraction, upsell, downsell, continuity) so a new customer generates enough cash within ~30 days to fund acquiring the next one - Alex Hormozi's client-financed acquisition. Use when customers buy once and never again, when CAC eats all the profit, when you can't afford to advertise profitably, when the business grows but cash shrinks, when you sell one product at one price, when deciding what to sell first or next, or when structuring upsells, downsells, payment plans, trials, and continuity. Covers the 30-day payback rule, attraction/upsell/downsell/continuity offer types, and cash-flow sequencing for validated markets.

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

Build and execute marketing strategy for Direct-to-Consumer (DTC) brands — customer acquisition, retention, email flows, social proof, subscription models, and repeat purchase mechanics. Use when the user says "DTC marketing", "direct to consumer", "D2C strategy", "selling directly to customers", "cut out the middleman", "DTC brand", "e-commerce brand marketing", "how do we get direct customers", "DTC growth", "consumer brand marketing", "we sell direct", or is building a brand that sells its products directly without retail or distribution middlemen.

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

Collect Amazon.com written product reviews at scale through Woot's public review AJAX route, retain every attempt and error log, reconcile partial runs, and normalize exact review text into auditable JSONL. Use for VOC, competitor review mining, low-star complaint analysis, listing research, or batch ASIN review acquisition without Amazon credentials. Amazon data layer of the bggg VOC suite (shared project folder; orchestrated by industry-orchestrator, reported by bggg-voc-report).

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

针对包含激励信号的10Hz采样电池数据，利用FFT（含去直流和加窗处理）计算特定频率的电化学阻抗并绘制奈奎斯特图。

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

Designs and reviews detections from telemetry prerequisites, correlation logic, Sigma metadata, severity, status, and benign cases. Use for detection rules, Sigma review, analytic coverage, or tuning; not generic logging advice or live deployment.

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

Validates defensive controls with paired authorized action and observation evidence, distinguishing blocked, prevented, detected, responded, and telemetry-gap outcomes. Use for purple-team validation design or offline fixture review; not unsanctioned testing or production efficacy claims.

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

Configure ViewModel state emission with StateFlow, SharedFlow, and sealed UiState classes in Android. Use for state modeling and sharing policies; defer generic lifecycle collection, navigation-event plumbing, Hilt injection, test code, and configuration-change recipes to their specific skills.

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

Enforce WCAG 2.2 AA compliance with semantic HTML, ARIA roles, keyboard navigation, and color contrast standards for web UIs. Use when building interactive components, adding form labels, fixing focus traps, or auditing a11y compliance.

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

Build Gradio web UIs and demos in Python. Use when creating or editing Gradio apps, components, event listeners, layouts, or chatbots.

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

Implements drag-and-drop and sortable interfaces with React/TypeScript including kanban boards, sortable lists, file uploads, and reorderable grids. Use when building interactive UIs requiring direct manipulation, spatial organization, or touch-friendly reordering.

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

Implements search and filter interfaces for both frontend (React/TypeScript) and backend (Python) with debouncing, query management, and database integration. Use when adding search functionality, building filter UIs, implementing faceted search, or optimizing search performance.

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

Use when an approved tutorial spec exists and the run needs a deterministic prerequisite graph before module planning.

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

Generate MSBuild binary logs (binlogs) for build diagnostics and analysis. USE FOR: adding /bl:{} to any dotnet build, test, pack, publish, or restore command to capture a full build execution trace, prerequisite for binlog-failure-analysis and build-perf-diagnostics skills, enabling post-build investigation of errors or performance. Requires MSBuild 17.8+ / .NET 8 SDK+ for {} placeholder; PowerShell must quote the complete switch as '-bl:{}'. DO NOT USE FOR: non-MSBuild build systems (npm, Maven, CMake), analyzing an existing binlog (use binlog-failure-analysis instead).

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

Build and review Blazor applications across server, WebAssembly, web app, and hybrid scenarios with correct component design, state flow, rendering, and hosting choices. USE FOR: building interactive web UIs with C# instead of JavaScript; choosing between Server, WebAssembly, or Auto render modes; designing component hierarchies and state. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

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

Orchestrates Volcengine Cloud Detect (云拨测) false-alarm reduction for failing periodic-task dial points. Use for scheduled task scans, retrying failed nodes, control-testing node health, distinguishing real target outages from broken dial points, and suggesting same-type LastMile/IDC/Private replacement nodes. Runs the byted-util-volcengine-cloud-detect volc_detect.py CLI only; requires that skill and ships no API/script implementation.

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

Use when a native app, service, or user-mode driver host allocation fails; distinguish VA exhaustion, fragmentation, and commit pressure. Not for managed .NET heap growth, proving a leak from one snapshot, or corruption.

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

将 dependency-cruiser 接入 TypeScript 仓库，使每个 package 都是一个深度模块：实现隐藏在子文件夹中，只能通过入口点文件访问。由用户调用。

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

Diagnose where your growth is actually leaking (acquisition, activation, retention, or loops) and produce a growth plan with a named loop, an activation definition, a 90-day experiment portfolio and channel guardrails. Use it when someone says growth stalled, signups don't activate, retention is flat, how do we build a growth loop, should we go PLG, onboarding redesign, churn, referral program, or which channel should we bet on. Draws on 672 insights from 143 Lenny's Podcast guests, led by Elena Verna, Casey Winters and Lauryn Isford.

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

Trigger for: writing, revising, converting, or descoping a federal Statement of Work, Performance Work Statement, SOW, PWS, or SOO; develop executable requirements; define contract scope; create measurable performance standards; or prepare requirements before an IGCE. Produce a contract-file-ready .docx plus separate chat-only staffing and Section B handoffs. Never place FTEs, SOC codes, staffing estimates, IGCE content, CLINs, or pricing schedules inside the SOW/PWS body. Do NOT use for the IGCE, market research report, acquisition plan, QASP, or clause-selection matrix.

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

Lens — Add a cognitive lens to any problem. It accepts a task description and produces an enhanced description that surfaces hidden dimensions, prerequisites, and lines of inquiry—the things you do not know you do not know. Use when the user asks to brainstorm, analyze, generate a skill, distill, or fuse, or when the input is too simple and needs to be expanded.

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

Select proportional Enterprise validation and diagnose exact CI runs, distinguishing product, harness, infrastructure, and credential failures.

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

Builds reactive UIs on Convex subscriptions: useQuery patterns, optimistic updates, pagination that stays live, presence, and avoiding subscription churn. Use when wiring the frontend to Convex, when data does not update live, or when a page rerenders too much.

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