persona-performance

Diagnose and eliminate performance bottlenecks through measurement-driven profiling and optimization.

3|2|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/Yoodaddy0311/artibot --skill persona-performance-yoodaddy0311
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: persona-performance
Source: https://github.com/Yoodaddy0311/artibot/tree/main/plugins/artibot/skills/persona-performance
Command: npx skills add https://github.com/Yoodaddy0311/artibot --skill persona-performance-yoodaddy0311

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Slow load times, high latency, and resource waste often get "fixed" by guesswork, leading to wasted effort on the wrong layer. This Skill enforces a measure-first discipline so every optimization targets the actual bottleneck with verified before/after metrics. ## Core Features & Use Cases - Structured Optimization Process: A six-step workflow covering baseline measurement, bottleneck profiling, impact estimation, targeted fixes, verification, and documentation. - Performance Budgets: Concrete targets such as load under 3s on 3G, API p95 under 500ms, initial bundle under 500KB, and mobile memory under 100MB. - Anti-Pattern Detection: Flags common mistakes like optimizing without profiling, caching without eviction strategy, and micro-optimizing off the critical path. - Use Case: When a user reports that an API endpoint feels slow, the Skill guides profiling to find the real cause (e.g., N+1 queries), applies the smallest effective fix, and re-measures p95 latency to confirm the improvement. ## Quick Start Ask the agent to profile the slow endpoint or page, identify the real bottleneck, and propose one measured optimization with before and after metrics.

Frequently Asked Questions about persona-performance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find and fix performance bottlenecks in my application?▼

Start by measuring a baseline, then profile to locate the actual bottleneck rather than assuming one. Estimate the impact of each fix, apply the smallest change addressing the largest bottleneck, and re-measure to confirm improvement.

What performance metrics should I track for web applications?▼

Track load time under 3 seconds on 3G, API p95 latency under 500ms, initial bundle under 500KB, mobile memory under 100MB, and average CPU under 30%. Focus on p95 and p99 percentiles rather than averages.

When should I not optimize code performance?▼

Do not optimize when no profiling data or performance baseline exists to guide the work. Premature optimization without measurement risks rewriting the wrong layer and sacrificing readability for negligible gains.

Why is caching not always a good performance fix?▼

Caching introduces invalidation bugs, staleness, and cold-start cliffs, so it should only be applied after measuring confirms it addresses the real bottleneck. Caches without an eviction strategy create new failure modes.

What are common causes of slow API response times?▼

Common causes include N+1 database queries, missing indexes, oversized payloads, and unnecessary re-renders on the frontend. Profiling identifies which of these is the actual bottleneck before any fix is attempted.