2,199 件 ・ 関連度順
概要と使いどころ
Field marketing, events, and webinars for B2B SaaS. Use this skill for conference and sponsorship selection, booth strategy, owned events and roadshows, executive dinners, the webinar program, and event-sourced pipeline measurement. Also triggers on: field marketing, events, conference, trade show, booth, sponsorship, roadshow, executive dinner, webinar, event ROI, event pipeline, user conference, meetups.
日本語の概要は準備中です。原文の説明を表示しています。
Operate professional paid advertising across Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, Apple, Amazon, Reddit, Pinterest, Snapchat, and X. Use for account intake, source-grounded audits, strategy, budget and measurement planning, creative production, experiments, reporting, monitoring, and explicitly approved campaign changes. Also trigger on PPC, paid social, retail media, attribution, tracking, landing pages, cross-platform conversion totals, negative keywords or search terms, beta-feature scoring, stale platform claims, API-token or credential setup, campaign deletion, and safe Claude Ads installation or uninstall.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and review paid-media budgets, bidding, pacing, marginal return, forecasts, CPA, ROAS, MER, LTV:CAC, constraints, and allocation across supported platforms. Use for ad budget allocation, media budget, bidding strategy, scaling, spend pacing, budget forecast, ROAS target, or investment tradeoffs.
日本語の概要は準備中です。原文の説明を表示しています。
Ensure event-driven designs specify delivery guarantees, ordering, idempotency, schema evolution, and replay/backfill strategy.
日本語の概要は準備中です。原文の説明を表示しています。
Ensure design/ADR changes include a concrete migration plan, rollout strategy, rollback conditions, and compatibility considerations.
日本語の概要は準備中です。原文の説明を表示しています。
Ensure API/contract changes specify versioning strategy, backward compatibility, deprecation plan, and migration guidance.
日本語の概要は準備中です。原文の説明を表示しています。
Detect undefined or inconsistent cache strategies (layers, consistency, invalidation, TTL, failure handling) in design documents.
日本語の概要は準備中です。原文の説明を表示しています。
Ensure architecture docs capture availability targets, failover strategy, capacity headroom, and resilience trade-offs for critical services.
日本語の概要は準備中です。原文の説明を表示しています。
Implements type-safe reactive SQL persistence in Flutter using Drift v2.32 (formerly Moor) built on SQLite with automatic code generation. Activates when defining table schemas with Drift DSL, writing type-safe join or subquery operations, handling schema migrations with MigrationStrategy, using reactive watch() streams for live UI updates, implementing ACID transactions, defining foreign key constraints or cascade deletes, enabling WAL mode for write performance, troubleshooting generated .g.dart type mismatches, migrating from sqflite or sqlite3 v2 to v3, using DAOs for query separation, or building offline-first apps requiring strong relational data integrity and compile-time SQL verification.
日本語の概要は準備中です。原文の説明を表示しています。
Expert-level guidance for Flutter production applications: architecture decisions (Clean/Layered/Hexagonal/Feature-First), advanced state management (BLoC/Riverpod/GetX), performance optimization (eliminating jank, memory profiling, reducing rebuild overhead), code review with design pattern enforcement, scalability assessments, native platform integration (MethodChannel/EventChannel/FFI), complex UI challenges (custom render objects, slivers), testing strategies (unit/widget/integration/golden), CI/CD pipeline architecture, build optimization, and accessibility compliance. Triggers: 'architecture decision', 'design pattern', 'performance issue', 'code review', 'production problem', 'scaling concerns', 'best practices', 'technical debt', 'refactoring strategy'. Essential for complex enterprise apps, critical production debugging, architectural refactors, or when choosing between competing technical approaches.
日本語の概要は準備中です。原文の説明を表示しています。
Identify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.
日本語の概要は準備中です。原文の説明を表示しています。
Discover and track emerging trends across Google Trends, Instagram, Facebook, YouTube, and TikTok to inform content strategy.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Shape FriendlyBet product decisions, MVP scope, user stories, tournament flows, multi-sport expansion, pool mechanics, social competition loops, and feature prioritization. Use when planning what FriendlyBet should build, cut, sequence, or validate, especially for new sports, prediction formats, pool flows, leaderboards, sharing, or product strategy.
日本語の概要は準備中です。原文の説明を表示しています。
Document templates for all pipeline output documents — specs, indexes, reports, and strategy docs. Use when any workflow needs to produce a structured document.
日本語の概要は準備中です。原文の説明を表示しています。
Configure CI/CD stages, secrets model, and service-aware pipeline strategy with execution verification gate
日本語の概要は準備中です。原文の説明を表示しています。
Define system architecture, error architecture, and data strategy with map guards and ideation context reload
日本語の概要は準備中です。原文の説明を表示しています。
Manage API versioning and evolution with URL/header/query strategies, deprecation workflows, breaking change classification, sunset headers, and consumer-driven contract testing. Use when designing versioning strategy, deprecating endpoints, or evolving API contracts.
日本語の概要は準備中です。原文の説明を表示しています。
Apply Gang of Four design patterns to solve architectural problems in TypeScript. Use when refactoring code architecture, implementing extensible systems, decoupling components, or following SOLID principles. Covers all 22 GoF patterns: Creational (Factory Method, Abstract Factory, Builder, Prototype, Singleton), Structural (Adapter, Bridge, Composite, Decorator, Facade, Flyweight, Proxy), and Behavioral (Chain of Responsibility, Command, Iterator, Mediator, Memento, Observer, State, Strategy, Template Method, Visitor).
日本語の概要は準備中です。原文の説明を表示しています。
Know when NOT to speak in group chats. Use this skill before replying in any group conversation to decide if a response adds unique value or is just noise. Prevents unsolicited jumping-in, echo responses, and unnecessary acknowledgments.
日本語の概要は準備中です。原文の説明を表示しています。
Build and run the owner's self-branding system in a structured way across LinkedIn, Substack, dev.to, X, profile rewrites, recurring series, and comment strategy. Use when the owner asks for positioning, a branding plan, profile updates, content drafts, a publishing sequence, comment ideas, or help maintaining a consistent public voice. Optimize for operator credibility: specific experience, defensible numbers, concrete artifacts, and category ownership.
日本語の概要は準備中です。原文の説明を表示しています。
Datasets : ProntoQA, FOLIO, ProofWriter, ConditionalQA, StrategyQA Model : GPT-5 (Azure deployment) Config : max_attempts=3 , verify_timeout=10000ms B
日本語の概要は準備中です。原文の説明を表示しています。
Review Jupyter notebooks for side effects, dependencies, and safe execution strategy before running or editing them.
日本語の概要は準備中です。原文の説明を表示しています。
Help with MongoDB query optimization and indexing. Use only when the user asks for optimization or performance: "How do I optimize this query?", "How do I index this?", "Why is this query slow?", "Can you fix my slow queries?", "What are the slow queries on my cluster?", etc. Do not invoke for general MongoDB query writing unless user asks for performance or index help. Prefer indexing as optimization strategy. Use MongoDB MCP when available.
日本語の概要は準備中です。原文の説明を表示しています。