performance
Performance profiling and SwiftUI debugging skills — Instruments guidance, hangs, memory issues, slow launches, energy drain, unnecessary re-renders, and view identity problems. Use when an app is slow, janky, or resource-hungry.
Works with
--- name: performance description: Performance profiling and SwiftUI debugging skills — Instruments guidance, hangs, memory issues, slow launches, energy drain, unnecessary re-renders, and view identity problems. Use when an app is slow, janky, or resource-hungry. license: MIT --- # Performance Skills Diagnose and fix performance problems, from system-level profiling to SwiftUI render behavior. ## When This Skill Activates Use this skill when the user: - Reports the app is **slow, janky, or hanging** - Wants to profile with **Instruments** (Time Profiler, Allocations, Hangs) - Is investigating **memory issues, slow launches, or energy drain** - Sees SwiftUI views **re-rendering too often** or slow `body` evaluations - Asks about **view identity** problems or `_printChanges()` ## Available Skills Paths are relative to THIS file's directory — skills run with cwd set to the user's project, so resolve each path from this SKILL.md's own location. | Skill | Read | Covers | |-------|------|--------| | profiling | `profiling/SKILL.md` | Instruments workflows; hangs, memory, slow launch, energy diagnosis | | swiftui-debugging | `swiftui-debugging/SKILL.md` | Unnecessary re-renders, view identity, slow body evaluations | ## How to Route 1. Match the request to a row above — system-level symptoms → profiling; SwiftUI render symptoms → swiftui-debugging. 2. Read that SKILL.md (relative to this file) plus any reference files it lists. 3. Apply the guidance to the user's code.
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.
vercel-optimize
vercel-labs/agent-skills
Use for Vercel cost and performance optimization on deployed projects, especially Next.js, SvelteKit, Nuxt, and limited Astro apps. Collect Vercel metrics, usage, project config, and code scan results first; investigate only metric-backed candidates; produce ranked recommendations grounded in verified files and version-aware Vercel/framework docs. Trigger for Vercel bill reduction, slow or expensive routes, caching opportunities, Function Invocations, Build Minutes, Fast Data Transfer, Core Web Vitals, Bot Management, Fluid compute, or cost breakdown requests.
