Slow applications lose users and make incidents harder to diagnose. This skill gives Claude, Codex, and Claude Code practical patterns for faster systems.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "Performance Optimization" from https://skillstore.io/skills/ariegoldkin-performance-optimization.md and its manifest at https://skillstore.io/api/skills/ariegoldkin-performance-optimization/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.
Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
All 36 static findings are false positives caused by Markdown formatting, TypeScript syntax, local diagnostics, and ordinary performance examples. No malicious commands, credential exposure, reconnaissance, prompt injection, or uncontrolled code loading were found.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Review database access patterns, find likely query bottlenecks, and plan indexing or pagination changes.
Improve Frontend Responsiveness
Apply bundle splitting, memoization, virtualization, and layout fixes to reduce load time and interaction delay.
Set Performance Guardrails
Define budgets, metrics, and launch checks that keep API latency and Core Web Vitals within targets.
Try These Prompts
Find Basic Bottlenecks
Review this feature for likely performance bottlenecks. Focus on database queries, API responses, frontend rendering, and missing measurements.
Plan Database Fixes
Analyze these database access patterns. Recommend indexes, query changes, pagination, and N+1 fixes with clear tradeoffs.
Optimize Frontend Rendering
Review this React screen for rendering and bundle performance. Recommend code splitting, memoization, virtualization, and layout improvements.
Design Performance Strategy
Create a full-stack performance plan for this application. Include targets, instrumentation, caching, database changes, API changes, and rollout checks.
Best Practices
Measure before and after every optimization so improvements are tied to real performance data.
Prioritize bottlenecks by user impact, frequency, and cost instead of optimizing isolated code paths.
Pair caching with explicit invalidation rules, observability, and safe fallback behavior.
Avoid
Do not add indexes, caches, or memoization without a measured bottleneck and validation plan.
Do not load full datasets when cursor pagination or bounded queries can satisfy the workflow.
Do not treat a high lab score as proof that real user performance is healthy.
Frequently Asked Questions
Does this skill run performance tests automatically?
No. It provides guidance, templates, and review prompts that help an agent plan and implement performance improvements.
Which parts of the stack does it cover?
It covers database queries, caching, API responses, React rendering, bundle size, metrics, and performance budgets.
Can it improve Core Web Vitals?
Yes. It includes targets and frontend patterns that can improve LCP, INP, CLS, and TTFB when applied correctly.
Is it specific to one framework?
No. Some examples use React, Express, PostgreSQL, and Redis, but the optimization principles are broadly useful.
Can it replace production monitoring?
No. It helps design metrics and budgets, but production systems still need real monitoring and alerting.
How should teams validate recommendations?
Teams should compare baseline and post-change metrics, including latency, query time, bundle size, and real user experience.