api-contract
This skill should be used when the user asks about "API contract", "api-contract.md", "shared interface", "TypeScript interfaces", "request response schemas", "endpoint design", or needs guidance on designing contracts that coordinate backend and frontend agents.
sprint-workflow
This skill should be used when the user asks about "how sprints work", "sprint phases", "iteration workflow", "convergent development", "sprint lifecycle", "when to use sprints", or wants to understand the sprint execution model and its convergent diffusion approach.
thymer-capture
Capture notes, logs, and journal entries to Thymer. Use when user says "note this", "log this", "capture this", "add to journal", "inbox this", "save this conversation", or wants to save content to their Thymer workspace.
codex-review
Codex CLI を使って、noninteractive に code review を依頼することができます。
vercel-react-best-practices
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.
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
tip-javascript-typescript
This skill should be used when writing or refactoring TypeScript/JavaScript code. It provides coding patterns and best practices aligned with the user's preferred development style, typescript language usage patterns, and library-specific tips.
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
prepare-issue-pr
Prepare comprehensive Issue or Pull Request descriptions using repository templates. Automatically detects type, finds appropriate templates, and guides users through filling them out completely. Use when users want to create Issues or PRs.
github-pr-review-operation
GitHub Pull Requestのレビュー操作を行うスキル。PR情報取得、差分確認、コメント取得・投稿、インラインコメント、コメント返信をghコマンドで実行する。PRレビュー、コードレビュー、PR操作が必要な時に使用。
GroundEffect
Use this skill when the user asks about email, calendar, or Gmail/Google Calendar management via GroundEffect CLI. Triggers include "search my email", "list recent emails", "check my calendar", "what's on my calendar", "show my meetings", "calendar tomorrow", "calendar next week", "create a calendar event", "manage groundeffect accounts", "sync status", "start the daemon", "groundeffect", "groundeffect command", "draft email", "save draft", "save as draft", "create draft", "send email".
thoughts-management
Manage thoughts directory operations including initialization, synchronization, and metadata generation. Use after creating or modifying research documents, implementation plans, or notes to keep the searchable directory synchronized. Also use when gathering git metadata for document frontmatter.
annotate
Create flexible annotation workflows for AI applications. Contains common tools to explore raw ai agent logs/transcripts, extract out relevant evaluation data, and llm-as-a-judge creation.
gke-expert
Expert guidance for Google Kubernetes Engine (GKE) operations including cluster management, workload deployment, scaling, monitoring, troubleshooting, and optimization. Use when working with GKE clusters, Kubernetes deployments on GCP, container orchestration, or when users need help with kubectl commands, GKE networking, autoscaling, workload identity, or GKE-specific features like Autopilot, Binary Authorization, or Config Sync.
contribution-loop
Find repos with design drift and generate meaningful PRs to fix them. Runs as an autonomous loop discovering GitHub repos using design systems, scanning for drift, and staging fixes for human review.
humanize
Transform AI-generated text into natural, human-like content that bypasses AI detectors like GPTZero, Turnitin, and Originality.ai. Uses credits based on word count.
readability
Analyze text readability with Flesch-Kincaid, Gunning Fog, SMOG, and other metrics. Returns objective scores with interpretation and recommendations.
word-stats
Get word count, character count, reading time, and text statistics. Quick analysis without questions.
follow-up
Write follow-up emails that re-engage without being annoying. Uses proven psychology for follow-up sequences. 42% of replies come from follow-ups.
cold-email
Write cold emails that get replies using proven frameworks (AIDA, PAS, BAB). Enforces best practices like 50-125 word limit and personalized openers.
detect-ai
Analyze text to detect if it was written by AI. Returns a score from 0-100 with detailed metrics. Use when checking content before publishing or submitting.
php-modernization
Use when working with ANY PHP modernization task: upgrading PHP 8.1+, adding strict types, configuring PHPStan/Rector/PHP-CS-Fixer, refactoring to enums/DTOs/readonly, improving type safety, or reviewing PHP code quality. Triggers on: PHP upgrade, modernize, type safety, PHPStan, Rector, PHP-CS-Fixer, enum, DTO, readonly, strict_types.
android
Use when working with Android devices via ADB - connecting devices, running shell commands, installing apps, debugging, taking screenshots, UI automation, viewing logs, analyzing crashes, or exploring system internals. Triggers on "adb", "logcat", "install apk", "debug android", "android device", "shell command", "screenshot", "dumpsys", "crash", "ANR".
lineageos
Use when working with LineageOS custom ROM development, including syncing sources, building, device trees, repopick, Gerrit contributions, or LineageOS-specific features. Triggers on "LineageOS", "lineage-sdk", "breakfast", "brunch", "repopick", "vendor/lineage", "lineage.dependencies", "mka bacon".
android-build
Use when building Android apps (Gradle CLI) or ROMs (AOSP, LineageOS). Triggers on "gradle build", "assemble", "AOSP", "LineageOS", "lunch", "mka", "breakfast", "brunch", "compile android", "device tree", "kernel build".
android-fastboot
Use for fastboot operations, flashing partitions, bootloader unlocking, recovery mode, or partition management. Triggers on "fastboot", "flash boot.img", "unlock bootloader", "recovery mode", "TWRP", "Magisk", "partition", "sideload", "A/B slots". WARNING - These operations can brick devices if done incorrectly.
growth-experimentation
When the user wants to design, prioritize, or analyze growth experiments -- including A/B tests, hypothesis frameworks, ICE/RICE scoring, or growth sprints. Also use when the user says "A/B test," "experiment design," "growth sprint," "experiment prioritization," or "statistical significance." For analytics setup, see product-analytics. For growth modeling, see growth-modeling.
viral-loops
When the user wants to design product-driven viral growth -- including invite mechanics, collaboration loops, embedding loops, or network effects. Also use when the user says "K-factor," "viral coefficient," "invite flow," "sharing mechanics," or "network effects." For structured referral programs, see referral-program. For growth loop design, see growth-loops.
user-segmentation
When the user wants to segment users for personalized experiences -- including behavioral cohorts, engagement scoring, churn risk scoring, or ICP refinement. Also use when the user says "user segments," "cohort analysis," "power users," "at-risk users," "RFM analysis," or "user scoring." For product-led sales, see product-led-sales. For retention, see retention-analysis.
usage-based-pricing
When the user wants to design or implement usage-based, consumption, or metered pricing -- including credit systems, overage handling, or billing infrastructure. Also use when the user says "pay per use," "metered billing," "credit system," "usage pricing," or "consumption pricing." For broader pricing strategy, see pricing-strategy. For expansion, see expansion-revenue.
trial-optimization
When the user wants to optimize free trial conversion -- including trial length, trial type selection, expiry flows, or trial email sequences. Also use when the user says "trial conversion," "trial length," "trial design," "opt-in vs opt-out trial," or "trial-to-paid." For activation, see activation-metrics. For feature gating, see feature-gating.
signup-flow-cro
When the user wants to optimize a signup or registration flow -- including field selection, social auth, single-step vs multi-step forms, or mobile signup. Also use when the user says "signup conversion," "registration form," "reduce signup friction," "signup A/B test," or "signup drop-off." For post-signup onboarding, see product-onboarding. For activation measurement, see activation-metrics.
self-serve-motion
When the user wants to reduce friction in the self-serve buying experience, optimize in-product checkout, remove "contact sales" gates, or design self-serve onboarding and support. Also use when the user says "frictionless," "self-service," "remove sales gates," "no-demo experience," or "friction audit." For signup flow optimization, see signup-flow-cro. For pricing page design, see pricing-strategy.
retention-analysis
When the user wants to analyze, diagnose, or improve user retention -- including cohort analysis, churn prediction, engagement scoring, or resurrection campaigns. Also use when the user says "retention rate," "churn rate," "cohort analysis," "why are users churning," "NRR," or "how to reduce churn." For engagement loops, see engagement-loops. For activation, see activation-metrics.
referral-program
When the user wants to design a referral or affiliate program -- including reward structures, referral mechanics, two-sided incentives, or partner programs. Also use when the user says "refer a friend," "referral reward," "affiliate program," "ambassador program," or "referral ROI." For viral loop design, see viral-loops. For growth loops, see growth-loops.
product-onboarding
When the user wants to design or improve new user onboarding -- including product tours, checklists, empty states, welcome flows, or progressive disclosure. Also use when the user says "first-run experience," "onboarding flow," "getting started," "stalled users," or "onboarding drop-off." For activation metrics, see activation-metrics. For signup optimization, see signup-flow-cro.
product-led-sales
When the user wants to layer sales onto a PLG motion, build PQL scoring, design sales handoffs from product usage signals, or plan a hybrid PLG + sales model. Also use when the user says "product-led sales," "PQL," "PQA," "when to add sales to PLG," or "enterprise PLG." For broader PLG strategy, see plg-strategy. For expansion revenue, see expansion-revenue.
product-analytics
When the user wants to set up product analytics -- including event taxonomy, tracking plans, funnel analysis, or tool selection (Mixpanel, Amplitude, PostHog). Also use when the user says "event tracking," "analytics setup," "tracking plan," "analytics implementation," or "user identification." For PLG metrics, see plg-metrics. For experimentation, see growth-experimentation.
pricing-strategy
When the user wants to design or optimize pricing, packaging, or monetization -- including tier structure, freemium design, value metrics, or price research. Also use when the user says "pricing page," "how to price," "freemium vs free trial," "Good-Better-Best tiers," or "value-based pricing." For feature gating, see feature-gating. For trial optimization, see trial-optimization. For usage-based models, see usage-based-pricing.
plg-strategy
When the user wants to assess PLG readiness, design a product-led growth strategy, choose between freemium and free trial, evaluate PLG maturity, or plan a hybrid PLG + sales model. Also use when the user says "should we do PLG," "PLG vs sales-led," "growth motions," "PLG audit," or "go-to-market strategy." For specific mental models, see plg-mental-models. For growth loop design, see growth-loops.
plg-metrics
When the user wants to define PLG metrics, build a growth dashboard, or set KPI targets -- including activation rate, free-to-paid conversion, NRR, or North Star metric. Also use when the user says "PLG dashboard," "growth KPIs," "metric definitions," or "PLG benchmarks." For activation-specific metrics, see activation-metrics. For analytics setup, see product-analytics.
plg-mental-models
When the user needs mental models or frameworks for PLG decisions -- including product-channel fit, time-to-value, network effects, habit loops, or pricing psychology. Also use when the user asks "what framework should I use," "how should I think about this," or references a specific model like "adjacent user theory" or "bowling alley framework." For comprehensive PLG strategy, see plg-strategy. For growth loops, see growth-loops.
plg-ideas
When the user wants PLG ideas, tactics, or inspiration -- a mega-reference of 100+ product-led growth strategies organized by category. Also use when the user says "growth ideas," "PLG playbook," "growth tactics," "what should we try," or "growth brainstorm." For PLG strategy, see plg-strategy. For experimentation, see growth-experimentation.
paywall-upgrade-cro
When the user wants to optimize in-app paywalls, upgrade screens, or upgrade prompts -- including feature locks, usage limit walls, trial expiration screens, or context-triggered upsells. Also use when the user says "paywall design," "upgrade conversion," "upgrade modal," or "upsell prompt." For feature gating strategy, see feature-gating. For in-product messaging, see in-product-messaging.
in-product-messaging
When the user wants to design in-product messages -- including tooltips, banners, modals, slideouts, or notification bells -- without annoying users. Also use when the user says "in-app messages," "product announcements," "nudges," "contextual help," or "message frequency." For upgrade prompts specifically, see paywall-upgrade-cro. For feature launches, see feature-adoption.
growth-modeling
When the user wants to build quantitative growth models -- including loop-based models, sensitivity analysis, revenue forecasting, or unit economics. Also use when the user says "growth forecast," "revenue model," "CAC LTV," "growth projections," or "financial model." For growth loops, see growth-loops. For PLG metrics, see plg-metrics.
growth-loops
When the user wants to design, map, or quantitatively model growth loops -- including viral, content, paid, or sales loops. Also use when the user says "growth flywheel," "compounding growth," "loop modeling," "S-curve sequencing," or "growth engine." For viral-specific loop design, see viral-loops. For quantitative forecasting, see growth-modeling.
free-tool-strategy
When the user wants to plan a free tool for acquisition -- including calculators, analyzers, generators, or interactive resources as an engineering-as-marketing strategy. Also use when the user says "free tool," "engineering as marketing," "lead magnet tool," "free calculator," or "SEO tool." For viral growth, see viral-loops. For PLG strategy, see plg-strategy.
feature-gating
When the user wants to decide what features to gate vs keep free, design usage limits, implement reverse trials, or plan a free tier. Also use when the user says "what should be free," "feature gate," "paywall placement," "usage limits," or "reverse trial." For pricing strategy, see pricing-strategy. For upgrade screens, see paywall-upgrade-cro.
feature-adoption
When the user wants to drive adoption of a specific feature -- including launch planning, discovery mechanisms, adoption funnels, or feature deprecation. Also use when the user says "feature launch," "feature rollout," "underused features," "feature stickiness," or "how to get users to use a feature." For in-product messaging, see in-product-messaging. For onboarding, see product-onboarding.
Page 876 of 1486 · 74265 results
