3,216 件 ・ 関連度順
概要と使いどころ
Use when the user asks to "pick which social channels to run", "should we be on X platform or 小红书", or "plan our organic social channel portfolio"; produces an audience/objective-first portfolio with capability/access matrix, cadence-budget reality check, declared ECHO operating profile, boundary routing, and proposed-state registry events. Not for recording canonical channel facts — use channel-registry. 社媒渠道选择/渠道组合规划/平台能力矩阵/自然社媒
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says 'co-marketing,' 'partner marketing,' 'joint campaign,' 'who should we partner with,' 'integration marketing,' 'cross-promotion,' 'collaborate with another company,' 'partnership ideas,' or 'co-brand.' For customer referral programs, see referrals. For launch-specific partnerships, see launch.
日本語の概要は準備中です。原文の説明を表示しています。
Product marketing and go-to-market strategy for B2B SaaS launches and positioning. Use this skill when planning a product launch, developing positioning and messaging, analyzing competitive landscape, building customer advocacy programs, designing a win/loss interview program, working out why we lose deals, designing GTM strategy, creating category positioning, planning analyst briefings, or deciding which country to expand into and how far to localize. Also use it for brand marketing and demand creation — how much to spend on brand versus performance, what to measure when a brand campaign produces no conversion event, and how to answer "we cannot attribute it". Also triggers on: positioning, product launch, competitive intelligence, messaging, customer advocacy, win/loss analysis, win/loss interviews, why we lose deals, closed-lost analysis, loss reason, close-reason field, competitive displacement, displace an incumbent, rip and replace, competitive takeout, switch from a competitor, win deals from a competitor, incumbent contract, renewal window, auto-renewal notice period, switching costs, EU Data Act, cloud switching rights, why do we lose to no decision, GTM, category design, analyst briefing, G2 review, international expansion, market entry, expand into Europe, which country should we launch in next, localization, translate our site, in-country go-to-market, regional GTM, is cold email legal in Germany, brand marketing, brand awareness, brand vs performance, brand versus demand gen, demand creation, demand capture, 95-5 rule, out of market buyers, category entry points, distinctive brand assets, mental availability, brand tracking, brand health, brand lift, share of search, how do we measure brand, justify brand spend, brand budget.
日本語の概要は準備中です。原文の説明を表示しています。
Checks Tailwind utility class hygiene at the syntax level: arbitrary-value overuse that bypasses the theme scale, conflicting/duplicate utilities on one element, and hardcoded arbitrary colors that should use design tokens.
日本語の概要は準備中です。原文の説明を表示しています。
Apply when tempted to ask 'should I do X?' on reversible work. Proceed, present the result, let the human course-correct after the fact; reserve confirmation for irreversible actions.
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating, editing, reviewing, packaging, or organizing AI-agent skills and deciding whether a skill should be text-only, script-backed, or backed by an ML/specialist pipeline.
日本語の概要は準備中です。原文の説明を表示しています。
Control risky structural change by proving a refactor is necessary and that behaviour, contracts, data, security boundaries, and operational properties can be preserved through a staged migration. Use whenever the user wants to refactor, restructure, clean up, modernise, extract, migrate, rewrite, or re-architect existing code, or asks whether they should. Prefer this over starting the refactor. DO NOT REFACTOR is a first-class outcome. Part of the audit suite; inherits the shared constitution while its own job is proving necessity and behavioural preservation.
日本語の概要は準備中です。原文の説明を表示しています。
Calculate and schedule quarterly estimated tax payments (Form 1040-ES) for self-employed individuals. Covers self-employment tax calculation (15.3%), income tax estimation, safe harbor rules (100%/110% of prior year), payment deadlines, and underpayment penalties. Trigger on "estimated taxes", "quarterly taxes", "1040-ES", "how much should I pay quarterly", "self-employment tax", "avoid tax penalty".
日本語の概要は準備中です。原文の説明を表示しています。
Creating interactive data visualisations using d3.js. This skill should be used when creating custom charts, graphs, network diagrams, geographic visualisations, or any complex SVG-based data visua...
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to \\\"analyze competitors", "assess competitive landscape", "identify differentiation", "evaluate market positioning", "apply Porter's Five Forces",...
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "perform cloud penetration testing", "assess Azure or AWS or GCP security", "enumerate cloud resources", "exploit cloud misconfiguratio...
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "intercept HTTP traffic", "modify web requests", "use Burp Suite for testing", "perform web vulnerability scanning", "test with Burp ...
日本語の概要は準備中です。原文の説明を表示しています。
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create ...
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "test for broken authentication vulnerabilities", "assess session management security", "perform credential stuffing tests", "evaluate ...
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "pentest AWS", "test AWS security", "enumerate IAM", "exploit cloud infrastructure", "AWS privilege escalation", "S3 bucket testing...
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "attack Active Directory", "exploit AD", "Kerberoasting", "DCSync", "pass-the-hash", "BloodHound enumeration", "Golden Ticket", ...
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "test API security", "fuzz APIs", "find IDOR vulnerabilities", "test REST API", "test GraphQL", "API penetration testing", "bug b...
日本語の概要は準備中です。原文の説明を表示しています。
Control FriendlyBet operating cost, free-tier viability, provider/API cost, GitHub Actions/Supabase/Vercel usage, documentation hygiene, company memory updates, playbook maintenance, and skill validation. Use when evaluating cost, operational burden, tooling, internal docs, company memory, or whether agent profiles should become full skills.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
日本語の概要は準備中です。原文の説明を表示しています。
Design direction interview methodology — SUPERSEDED. The `impeccable` skill's `/impeccable teach` command now handles design direction discovery with a more comprehensive, multi-round interview that writes PRODUCT.md and DESIGN.md. This file is kept for pipeline backward compatibility — all new design work should use `/impeccable teach` instead.
日本語の概要は準備中です。原文の説明を表示しています。
Bootstrap a new Gradle module in any Kotlin Android project. Walks the user through choosing one of three module types — library module (`com.android.library`), feature module (regular Android library that hosts a feature/UI, install-time only), or dynamic feature module (`com.android.dynamic-feature`, on-demand/conditional/instant delivery). Use whenever the user wants to add a module, modularize code, extract a util/data/ui layer, create a new feature, set up Play Feature Delivery, or asks "should this be a library or feature module?". Discovers the project's existing conventions (plugin aliases, namespaces, sibling modules, version catalog) instead of hardcoding any. Pushes back on bad combos (e.g. utility code in a dynamic feature). Stops at scaffolding; app-level wiring is out of scope.
日本語の概要は準備中です。原文の説明を表示しています。
End-to-end Android indie idea workflow — feature-build phase only (no monetization). Phased — discover (if no idea) → generate 2 candidates → refine scope (offline/online, sharing, MVP vs full, core-value features) → risk/reward/tradeoff analysis when scoping down → emit idea brief. Use for greenfield app concepts, new feature ideation, idea discovery, or pre-design discovery before writing a design document. Triggers — new app idea, feature concept, indie dev brainstorm, validate idea, refine idea, what should I build, find an app idea, idea pipeline, I have no idea, help me find an app idea, scope down, MVP scoping, core value features.
日本語の概要は準備中です。原文の説明を表示しています。
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
日本語の概要は準備中です。原文の説明を表示しています。