Loading...
Loading...
Found 1,358 Skills
Use when the user asks to "pick a launch date", "plan the launch window", or "set the embargo and lift time"; produces a candidate-window comparison table (conflict / tailwind / risk per window) built from industry-event cycles and the competitor launch calendar, a launch-week vs rolling-release format call, store-review buffer padding (labeled Estimated), and an embargo window definition (lift moment + timezone) submitted to the launch registry as a candidate. Not for judging the cultural moment itself — use trend-spotter; not for launch-day execution — use launch-day-conductor. 发布择时/发布窗口/竞品日历/禁运期窗口/审核缓冲
When the user needs to create SOPs, playbooks, runbooks, or other operational documentation that defines how a recurring process should be executed.
When the user needs to build a LinkedIn authority system, create social content strategy, define content pillars, write posts, or establish thought leadership positioning. Activate on "LinkedIn strategy," "content pillars," "what should I post," or "build my personal brand."
Advanced and operational chat.agent capabilities for Trigger.dev, loaded on demand. Load this when working on the raw Sessions primitive (sessions / SessionHandle), a custom chat transport or the realtime wire protocol, durable sub-agents (AgentChat, chat.stream.writer), human-in-the-loop, steering, actions, background injection (chat.defer / chat.inject), fast starts (preload, Head Start via @trigger.dev/sdk/chat-server), context resilience (compaction, recovery boot, OOM, large payloads), chat.local run-scoped state, offline testing with mockChatAgent, or prerelease/version upgrades. For the everyday chat.agent({...}) definition and the useTriggerChatTransport happy path, use the trigger-authoring-chat-agent skill instead.
Build and deploy full-stack web and mobile apps with AWS Amplify Gen2 (TypeScript code-first). Covers auth (Cognito), data (AppSync/DynamoDB including schema modeling, enum types, relationships, authorization rules), storage (S3), functions, APIs, and AI (Amplify AI Kit with Bedrock). Supports React, Next.js, Vue, Angular, React Native, Flutter, Swift, and Android. Always use this skill for Amplify Gen2 topics — even for questions you think you know — it contains validated, version-specific patterns that prevent common mistakes. TRIGGER when: user mentions Amplify Gen2; project has amplify/ directory or amplify_outputs; code imports @aws-amplify packages; user asks about defineBackend, defineAuth, defineData, defineStorage, or npx ampx. SKIP: Amplify Gen1 (amplify CLI v6), standalone SAM/CDK without Amplify (use aws-serverless), direct Bedrock without Amplify AI Kit (use bedrock).
Gather and persist project design context such as audience, brand personality, UX goals, and implementation defaults for future better-web-ui work. Use when starting a project, defining UI direction, or establishing reusable design guidance before other better-web-ui skills.
Atomic Skill for Brand Gene Style Extraction. Based on product images and user-provided brand gene parameters (main color, font, platform, region, language), extract a unified brand visual language (Brand DNA) and output structured brandGeneJson for consumption by downstream atomic skills. Keywords: brand gene extraction, brand gene extract, brand DNA, brand visual definition, brand tone extraction, brand style extraction, visual identity extraction. Called by the image layout layer (linkfox-aigc-imagegen-cloth / product image layout path) in Step 3; triggered when the user says "extract brand gene", "define brand style", "brand gene", or "brand visual".
Diagnoses how rivalry, entrants, substitutes, buyers, and suppliers divide economic value within a defined industry. Use when assessing industry attractiveness, profit pressure, structural change, or structural positions with durable bargaining power.
Forces a business to pick ONE of the three self-consistent pricing strategies — More for More (the best, priced to match), More for Less (what you need at a reasonable price), or Less for Less (minimal but incredibly affordable) — then align the whole company behind it. Three gated phases: (1) collect the current reality — what you charge, what your marketing promises, which segments you serve; (2) map that onto the three strategies, surface where you're mixing them, and interrogate the trade-offs until you commit to one with its consequences accepted; (3) audit every signal (pricing page, homepage, support, roadmap) into a keep / stop / start plan ordered by how much each contradicts the story. Load when the user asks which pricing strategy fits them, whether to go premium / value / budget, why their pricing feels confused or mixed, or how to align product-price-marketing. Do NOT load to set the actual price number, write a price-increase announcement, define the ideal customer, or rewrite marketing copy.
Helps a founder build the case for raising prices and the moves that justify it; it drives toward a higher price and does not debate whether to raise. Three gated phases: (1) collect the reality (what you charge, what you promise, who buys) and diagnose which market the price has selected (the $1/$10/$100/$1,000-per-month ladder), the profit stakes (a 10% rise can be ~100% more profit), and whether the low price is strategy or fear, landing on a rough higher target; (2) brainstorm, judgment off, moves that justify a higher price — move up a market rung, price on value created not cost saved, build Love and Utility drivers, differentiate, repackage; (3) select, grilling each move down to a few that are good, strategy-consistent, buildable, and wanted. Load when the user asks how much to raise prices, what it would take to charge more, or why their price feels too low. Do NOT load to set the exact price, write the increase letter, define the ideal customer, or choose among the three pricing strategies.
Run a structured UI/UX consultation to either (a) co-design a project-specific design system and emit `design-spec.md`, (b) review an existing UI with prioritized fixes, or (c) emit compact do/don't rules for a surface. Triggers when the user wants to define / build / refine a design system or design tokens, asks for a design spec, asks for a full UI review of a screen / mockup / PR, or wants design rules for a surface type. Do NOT trigger for narrow one-off questions ("is this color OK?", "should this button be larger?") — answer those directly without invoking the consultation flow.
Use hexagonal architecture for external systems; define ports (interfaces) and per-provider adapters; select adapter at composition edge