「uis」の検索結果

Expert architectural standards for scalable Godot Apps, Tools, EditorPlugins, and Control-heavy UIs using Composition (Has-A Orchestrator + components). Use when building dashboards, tool windows, forms, settings panels, or EditorPlugin UIs. Do NOT use for gameplay entities (Player/Enemy/Weapon/Hitbox) — route those to godot-composition. Trigger keywords: Control, EditorPlugin, tool UI, Orchestrator, VLS, rock test, AuthComponent, ThemeManager, Saveable component, dependency injection.

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

Expert patterns for RPG/action ability systems including cooldown strategies, combo systems, ability chaining, skill trees with prerequisites, upgrade paths, and resource management. Use when implementing unlockable abilities, character progression, or complex skill systems. Trigger keywords: PlayerAbility, AbilityManager, cooldown, SkillTree, SkillNode, prerequisites, can_use, execute, ComboSystem, ability_chain, global_cooldown, charge_system, upgrade_path.

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

Apple Search Ads campaign strategy for indie developers — paid acquisition, keyword bidding, budget planning, and ROAS optimization. Use when user asks about running ads, paid user acquisition, or Apple Search Ads campaigns.

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

Pull GA4 reports, traffic data, and insights from the Google Analytics Data API. Use when asked about website traffic, user behavior, acquisition channels, conversions, or audience segments. Trigger phrases: "google analytics", "GA4", "traffic report", "analytics data", "user acquisition", "engagement metrics", "conversion tracking", "audience segments", "page views", "sessions".

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

ACTIVATION PREREQUISITE: the request or discovered target must explicitly identify C#, .NET, `.cs`, or `.csproj`; otherwise stay dormant without invoking this skill. USE FOR: locating System.DateTime.Now/UtcNow, System.IO.File/Directory, System.Environment, HttpClient, Console, or Process usage in C#; auditing C# code for hard-to-test framework dependencies; or verifying those C# calls are already abstracted. DO NOT USE FOR: any target lacking the activation prerequisite; generating wrappers (use generate-testability-wrappers); migrating code (use migrate-static-to-wrapper); or general code review.

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

Multi-channel demand generation, paid media optimization, SEO strategy, and partnership programs for Series A+ startups. Includes CAC calculator, channel playbooks, HubSpot integration, and international expansion tactics. Use when planning demand generation campaigns, optimizing paid media, building SEO strategies, establishing partnerships, or when user mentions demand gen, paid ads, LinkedIn ads, Google ads, CAC, acquisition, lead generation, or pipeline generation.

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

ACTIVATE when evaluating acquisition targets, conducting M&A due diligence, planning integration strategy, analyzing synergies, preparing sale materials, assessing culture fit, valuing targets, creating merger checklists, or managing M&A transactions. Critical for executives involved in buy-side or sell-side M&A, from initial target evaluation through post-acquisition integration.

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

Quantifies CRISPR editing outcomes with CRISPResso2 (Clement 2019 Nat Biotechnol) across Cas9-nuclease (indels, HDR), CBE and ABE base editors (target conversion + bystander), and prime editor (pegRNA-templated) modes. Covers single-amplicon (CRISPResso), multi-sample batch (CRISPRessoBatch), pooled-amplicon (CRISPRessoPooled), WGS off-target (CRISPRessoWGS), and sample-comparison (CRISPRessoCompare) workflows; quantification-window math that controls what is called edited; substitution-vs-indel diagnostic to distinguish BE from Cas9 contamination; MMEJ deletion pattern interpretation; allele-frequency tables; and failure modes from amplicon misalignment or contamination. Use when quantifying editing from amplicon sequencing, choosing CRISPResso mode by design, distinguishing intended edits from bystanders and indel byproducts, debugging low-alignment runs, or generating publication-grade editing reports.

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

Build interactive web applications using HTML/JavaScript interfaces with MATLAB computational backends via the uihtml component. Use when creating HTML-based MATLAB apps, JavaScript MATLAB interfaces, web UIs with MATLAB, interactive MATLAB GUIs, or when user mentions uihtml, HTML, JavaScript, web apps, or web interfaces.

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

Expert in growing and engaging communities sustainably. Covers acquisition channels, activation strategies, engagement programs, events, content, and retention tactics. Knows that healthy growth is about depth, not just numbers. Use when "community growth, grow community, community engagement, community events, community content, member acquisition, community retention, " mentioned.

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

Android Jetpack Compose Expert workflow skill. Use this skill when the user needs Expert guidance for building modern Android UIs with Jetpack Compose, covering state management, navigation, performance, and Material Design 3 and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

Comprehensive B2B demand generation and lead acquisition skill. Use when building lead generation systems, creating demand acquisition campaigns, optimizing CAC, designing lead magnets, conducting lead research, or planning multi-channel demand strategies. Covers ICP definition, funnel strategy, channel optimization, lead scoring, attribution, and pipeline generation for B2B SaaS.

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

🇺🇸 Your dev team ships features nobody asked for while user-reported bugs pile up for months. Operations blames engineering for ignoring users; engineering blames operations for not understanding technical constraints. This gives you the complete Product × Engineering × Operations alignment SOP — from unified backlog to 10-day sprint cadence to veto power rules. What's inside: • Dual-layer Kanban system (master backlog + sprint board with unified tagging) • 10-day sprint standard process (Day 1 dev → Day 6 testable build → Day 10 ship) • Issue template with reproducibility requirements (3x reported = auto-severe) • Tri-party alignment meetings (daily standup / sprint planning / sprint review) • Operations veto power on releases (P0 bug = block shipping) • User feedback → product iteration closed loop (beta testing + interview SOP) • Core metrics framework (acquisition → activation → retention → monetization → referral) • Technical debt management (20-30% sprint capacity reserved) • Ready-to-use templates: Bug Report, Sprint Planning, Responsibility Matrix Built from: Real product strategy meetings + beta testing frameworks. References Supabase sprint model, Manus/DeepSeek commercialization alignment. By @WeiYipei. 🇨🇳 你的研发团队在做没人要的新功能，用户反馈的 Bug 堆了三个月没人动。运营觉得研发不听用户，研发觉得运营不懂技术。这份 SOP 给你从统一看板到 10 天迭代节奏到一票否决权的完整产研运协同框架。 🇯🇵 開発チームは誰も求めていない機能を作り、ユーザーから報告されたバグは何ヶ月も放置。このSOPは、統一バックログから10日スプリント、リリース拒否権まで、プロダクト×エンジニアリング×オペレーションの完全な連携フレームワークを提供します。 🇰🇷 개발팀은 아무도 요청하지 않은 기능을 만들고, 사용자가 보고한 버그는 몇 달째 방치됩니다. 이 SOP는 통합 백로그부터 10일 스프린트, 릴리스 거부권까지 제품×개발×운영 완전 협업 프레임워크를 제공합니다. Triggers: "product ops" | "engineering operations" | "product development SOP" | "sprint planning" | "iteration management" | "cross-functional alignment" | "product engineering ops" | "dev ops collaboration" | "产研运协同" | "迭代管理" | "产品研发运营" | "プロダクト開発運営" | "제품개발운영"

Your competitor just launched. You have no idea how they grew so fast. Should you reverse-engineer their website? Track their social media? Map their growth flywheel? This gives you the complete SOP — from Wayback Machine snapshots to X/Twitter propagation analysis to growth flywheel scoring. Built from 150+ AI startup competitive analyses including the Lovable case study (4.3M views, 229K impressions launch day). By @WeiYipei. What's inside: • 4-step research framework (website teardown → social media → traffic sources → ad spend) • 3-version website evolution analysis (V1 / Beta / Launch via Wayback Machine) • X/Twitter propagation chain mapping (4-phase model + single-post teardown template) • Growth flywheel 6-stage scoring system (Activation → Referral → Acquisition → Retention → Revenue → Product) • KOL identification framework (Traffic King / Topic Starter / Mindset Shifter) • Content effectiveness ranking (validated: Visual Demo > User Story > Competitor Comparison) • ICP deep analysis template + Freemium pricing teardown • Complete self-check checklist 🇨🇳 你的竞品刚刚爆了。你完全不知道他们怎么做到的。该拆官网？盯社媒？画增长飞轮？这份 SOP 给你从 Wayback Machine 快照到 X/Twitter 传播链路还原到飞轮六阶段评分的完整方法论。基于 150+ AI 创业公司竞品分析实战，含 Lovable 完整案例。 🇯🇵 競合が突然バズった。どうやって成長したか全く分からない。このSOPは、Waybackスナップショットからツイッター伝播チェーン分析、フライホイール6段階スコアリングまでの完全な競合調査フレームワークを提供します。150以上のAIスタートアップ分析から構築。 🇰🇷 경쟁사가 갑자기 폭발적으로 성장했습니다. 어떻게 그렇게 빨리 성장했는지 모릅니다. 이 SOP는 Wayback 스냅샷부터 X/Twitter 전파 체인 분석, 플라이휠 6단계 스코어링까지 완전한 경쟁사 조사 프레임워크를 제공합니다. 150개 이상의 AI 스타트업 분석에서 구축. Triggers: "competitor research" | "competitive analysis" | "competitor analysis" | "growth flywheel" | "market research" | "竞品调研" | "竞品分析" | "增长飞轮" | "传播链路" | "競合分析" | "경쟁사 분석" | "social media teardown" | "Twitter propagation" | "content strategy analysis"

Drafts and revises U.S. environmental indemnity agreements for real estate lending and acquisition transactions, allocating contamination and environmental-law liability to protect lenders, secured parties, or buyers. Covers indemnity scope, reps/warranties, covenants, remediation rights, escrows, insurance, survival, and assignment aligned to loan or acquisition documents. Use when drafting an environmental indemnity agreement, environmental liability allocation, lender environmental rider, or Phase I/II ESA-driven risk terms.

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

Reverse engineer CGX Cognionics Quick-20 EEG acquisition protocol using MCP RE tooling (Binary Ninja, Ghidra, radare2)

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

Knowledge reference for Autonomous Refinement Loop research — pattern research into prerequisites for autonomous execution without synchronous human blocking gates. Defines failure categories, prerequisites, and conditions for replacing human judgment with machine-verifiable checks. Use when designing or evaluating autonomous agent loops, gate conditions, or HOOTL execution patterns.

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

Works backward from the stated goal through its prerequisite chain — what must exist to reach the goal, then what each of those requires, back to the current state — classifying each prerequisite as AVAILABLE, DERIVABLE, or MISSING, and blocking planning until nothing is MISSING. Use before creating plans, delegating to agents, or defining acceptance criteria. Activates on specs, PRDs, tickets, RFCs, architecture designs, and multi-step engineering tasks. Always pass `#N` or an inline goal — invoking with no argument and no inline context returns BLOCKED. Integrates with CoVe-style planning pipelines.

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

Use when Stage 1 Discovery is complete and design must begin — transforms the ARTIFACT:DISCOVERY into an actionable ARTIFACT:PLAN via RT-ICA prerequisite verification. Produces approach, components, success criteria, acceptance tests, and risks. Blocks on missing prerequisites before design proceeds.

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

Clone un site web à l'identique à partir d'une URL : capture Playwright complète (screens full-page + fold par fold sur desktop/tablet/mobile, crops par section, états hover), extraction de tout ce que le navigateur expose (fonts, variables CSS, palette, typo, layout, breakpoints, animations, assets, console/network), reconstruction section par section, puis boucle de vérification par diff pixel et console propre. Utilise ce skill DÈS QUE l'utilisateur veut copier, cloner, répliquer, reproduire, « refaire pareil », s'inspirer fortement d'un site, d'une landing page, d'un template ou d'une page précise (« fais-moi la même chose que X », « copie ce site », « reproduis cette landing », « clone neverboring.ai », « je veux exactement ce design »), même s'il ne dit pas « clone ». Aussi pour auditer visuellement un site existant (screens complets, design tokens, fonts utilisées).

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

Evaluates MAC clause scope, carve-outs, and enforceability standards in acquisition agreements. Use when reviewing MAC provisions, assessing deal certainty, or analyzing interim covenant protections.

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

Research the etymology of a word by tracing proto-language roots, identifying cognates across language families, documenting semantic drift with dated attestations, and flagging folk etymologies. Use when investigating word origins, comparing cognate sets across related languages, charting historical meaning changes, or debunking popular but unsupported origin stories.

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

AI systematic knowledge acquisition from unfamiliar territory — deliberate model-building with feedback loops. Maps spaced repetition principles to AI reasoning: survey the territory, hypothesize structure, explore with probes, integrate findings, verify understanding, and consolidate for future retrieval. Use when encountering an unfamiliar codebase or domain, when a user asks about a topic requiring genuine investigation rather than recall, when multiple conflicting sources require building a coherent model, or when preparing to teach a topic and deep understanding is required first.

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

Build and maintain a library collection through acquisitions, weeding (deaccessioning), collection assessment, reader advisory, and interlibrary loan coordination. Covers selection criteria, collection development policies, the CREW/MUSTIE method for weeding, usage analysis, and responsive collection management. Use when building a new collection with a defined scope and budget, assessing an existing collection for gaps or outdated materials, when shelves are overcrowded and systematic weeding is needed, or when establishing a formal collection development policy.

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