performance-optimization
Use as a router only for broad performance tasks when the bottleneck is unknown. Prefer frontend-performance for frontend speed, backend-performance for server speed, and database-performance for SQL/database bottlenecks.
Works with
--- name: performance-optimization description: Use as a router only for broad performance tasks when the bottleneck is unknown. Prefer frontend-performance for frontend speed, backend-performance for server speed, and database-performance for SQL/database bottlenecks. license: MIT --- # Performance Optimization ## Workflow 1. Define the performance target and user-visible symptom. 2. Measure before changing code and identify the hot path. 3. Route to `frontend-performance`, `backend-performance`, or `database-performance` once the bottleneck is known. 4. Choose the smallest optimization that addresses the measured bottleneck. 5. Preserve correctness and avoid trading reliability for speed invisibly. ## Guidance - Frontend symptoms: use `frontend-performance`. - Backend symptoms: use `backend-performance`. - Database symptoms: use `database-performance`. - Build-only symptoms may stay here if no narrower build skill exists. ## Verification - Report before and after measurements using the same method. - Run correctness tests near the optimized code. - Document remaining bottlenecks and tradeoffs.
More Performance skills
seo-audit
coreyhaines31/marketingskills
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.
competitor-profiling
coreyhaines31/marketingskills
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.
prospecting
coreyhaines31/marketingskills
When the user wants to find, qualify, and build a list of prospects to reach out to — across B2B SaaS, general B2B, or local small businesses. Also use when the user mentions "prospecting," "build a prospect list," "find prospects," "find leads," "lead gen list," "find SaaS companies that," "find B2B companies," "find local businesses," "ICP-fit accounts," "who should we go after," "outbound list," "target account list," "find clients near me," "businesses without websites," "prospect research," "qualified leads," "find my first customers," "early adopters," "design partners," "beta users," or "who has this problem." Use this for the list-building and qualification phase. For writing the outbound copy after the list is built, see cold-email. For deep competitive research on specific accounts, see competitor-profiling.
