Loading...
Loading...
Found 3,372 Skills
Optional Stage 0 of the feature workflow — clarify vague ideas through dialogue until they are ready to enter the design phase. The role of AI is a thinking partner: dig out the real problem the user wants to solve (instead of sticking to the first solution they blurt out), actively evaluate the solution when the user brings it up, and propose better alternatives if necessary. After the discussion, output {slug}-brainstorm.md to document the results. Trigger scenarios: The user says "I have an unclear idea", "Let's brainstorm first", "The feature direction is still undecided", or the user brings a specific solution but wants to hear other ideas first. Skip this stage and proceed directly to design if the idea is already clear and the user does not want to discuss the solution further. This stage also does not handle bugs and refactoring.
Document the finalized tech stack selections, architecture decisions, long-term constraints, and coding conventions in the project into searchable permanent records. No one will remember why X was chosen six months later, but with decision documents, at least the background can be understood before making changes next time. Four categories: tech-stack (which tools/libraries/frameworks to use), architecture (how the system is organized), constraint (what is not allowed), convention (what is uniformly done). Trigger scenarios: Proactively trigger after making important choices during feature-design or issue-analyze, or when the user says "record the decision", "archive tech selection", "ADR", "record this constraint", "write down the convention". Only archive finalized decisions; do not archive proposed solutions under discussion.
Specializes in analyzing Lynx trace data to diagnose performance issues and provide actionable optimization strategies. Key Scenarios: - Loading Performance: Diagnosing slow startup metrics (FCP, FMP, TTI) and white screen issues. - Smoothness Analysis: Investigating root causes for scroll jank, frame drops, and interaction lag. - Regression Detection: Comparing traces to identify performance degradation or verify optimization gains between versions. - Pipeline Deep Dive: Pinpointing bottlenecks in specific rendering stages like Layout, Paint, JS execution, and background threads. - Native Module Analysis: Investigating performance issues related to native module calls.
BrandJet AI platform help — multi-channel outreach sequences, unified inbox, brand monitoring, AI visibility tracking, lead discovery, social listening, email warmup, Artemis AI agent, and integrations. Use when outreach sequences aren't getting replies, brand mentions going unnoticed, multi-channel sequences feel disjointed, unified inbox is overwhelming, or AI visibility scores are dropping. Do NOT use for designing cadence strategy (use /sales-cadence), cross-platform deliverability (use /sales-deliverability), social listening strategy (use /sales-social-listening), or enriching contacts (use /sales-enrich).
Influencer marketing strategy across platforms — creator discovery, audience vetting, campaign tracking, ROI measurement, outreach, gifting, and affiliate programs. Covers platform comparison (Modash, influData, Creator.co, Hypefy, LTK, Influencity, Meltwater, Skeepers, Heepsy, CreatorIQ, NeoReach, Afluencer, Collabstr, Cloutboost, House of Marketers, Famesters, inBeat, HypeAuditor, Aspire, Influencer Hero, InstaJet, Open Influence, Viral Nation, trendHERO, Upfluence, GRIN, PlutoBa), discovery workflow (search, filters, lookalikes, audience analysis), vetting framework (fake followers, engagement authenticity, audience demographics), campaign setup and tracking (EMV, ROAS, CPM, sales attribution), creator outreach (email templates, negotiation, rate cards), product gifting and seeding, influencer affiliate programs, and creator payments. Use when unsure which influencer platform to pick, can't find the right creators for your niche, worried about fake followers or inflated metrics, campaign results aren't being tracked properly, creators aren't responding to outreach, or influencer spend isn't showing ROI. Do NOT use for platform-specific config (use /sales-modash, /sales-infludata, /sales-creatorco, /sales-hypefy, /sales-ltk, /sales-influencity, /sales-meltwater, /sales-brandwatch, /sales-skeepers, /sales-heepsy, /sales-creatoriq, /sales-neoreach, /sales-afluencer, /sales-collabstr, /sales-cloutboost, /sales-houseofmarketers, /sales-famesters, /sales-inbeat, /sales-hypeauditor, /sales-aspire, /sales-influencer-hero, /sales-instajet, /sales-openinfluence, /sales-viralnation, /sales-trendhero, /sales-upfluence, /sales-grin, or /sales-plutoba), TikTok marketing strategy (use /sales-tiktok-marketing), gaming influencer marketing strategy (use /sales-gaming-marketing), ad campaign strategy (use /sales-retargeting), or email marketing to subscribers (use /sales-email-marketing).
Create pull requests using GitHub CLI with proper templates and formatting
Review a resume like a professional resume writer AND an ATS (Applicant Tracking System) — produce an ATS score (0-100), a level detection (fresher / mid / senior), a breakdown of what's working, what's failing, the 7 Deadly Sins check, priority fixes, concrete before→after bullet rewrites, and missing keywords. Use this skill whenever the user asks to review, audit, critique, score, rate, roast, or improve a resume or CV, or types /resume-review, or drops a resume PDF with a job description. Trigger EVEN IF the user just says "look at my CV", "check my resume", "is this resume good", "why am I not getting interviews", "roast my resume", or shares a resume file without explicit review instructions — any interaction involving a resume file or CV should invoke this skill. Especially strong for DevOps, SRE, Cloud, Platform, and Infrastructure engineering resumes, but works for any technical resume.
Workbench agent panel system — ef-edit CustomEvent pipeline, registry roll-up, selector grouping, and element property schema. Use when adding new GUI edit capture points, expanding the inspector schema, or continuing development of the EFAgentPanel feature.
A comprehensive guide to implementing Syncfusion Angular Input components, including Uploader, NumericTextBox, TextBox, Signature, CheckBox, OTP Input, RangeSlider, and TextArea. This guide is intended for building Angular applications with file upload UIs supporting async and chunked uploads, drag‑and‑drop functionality, numeric inputs with validation and formatting, text inputs with floating labels and custom adornments, digital signature capture with undo, redo, and export capabilities, checkbox multi‑select and indeterminate states, seamless form integration, accessibility compliance, one‑time password (OTP) inputs, programmatic row adjustments, and slider tick customization and styling.
Comprehensive guide for implementing Syncfusion Angular button components including Button, ButtonGroup, DropDownButton, Floating Action Button (FAB), ProgressButton, RadioButton, Switch, Speed Dial, SplitButtons. Use this when implementing and styling these components - covering visual styles (primary, outline, toggle, icon, round, block), grouping, dropdowns with popup items and animations, FAB positioning/scoping, Speed Dial linear/radial action items, progress-enabled buttons, and toggle/radio controls.
Find keywords competitors rank for that the target property does not, and prioritize them by opportunity. Uses Ahrefs MCP for keyword and competitor data. Use this skill when planning content investment, identifying quick wins, building a content calendar against a competitor set, or scoping a market entry. Triggers on keyword gap, content gap, competitor keywords, opportunity keywords, what should we target, where are competitors winning, keyword opportunity. Also triggers when planning content for a new market or after losing organic share to a specific competitor.
Use when fixing, editing, changing, or debugging existing TypeScript code and keeping changes small and proportional to what was touched.