Skip to content
Skills Library
Programming · Analysis

uds-performance-optimization

/uds-performance-optimization

Use when a website, mobile app, backend, or database has a measurable speed, latency, CPU, memory, energy, load, or performance-budget problem.

Licence
MIT
Last repository change
27.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when a website, mobile app, backend, or database has a measurable speed, latency, CPU, memory, energy, load, or performance-budget problem.

Original author description

Use when a website, mobile app, backend, or database has a measurable speed, latency, CPU, memory, energy, load, or performance-budget problem.

How it works

  1. Scope and inputs
  2. Procedure
  3. Output and verification
  4. Core rules
Original SKILL.md headings · 22 lines, 280 words
SKILL.md preview
---
name: uds-performance-optimization
description: "Use when a website, mobile app, backend, or database has a measurable speed, latency, CPU, memory, energy, load, or performance-budget problem."
---
# Evidence-based performance optimization

## Scope and inputs
Optimization needs a symptom, goal, or budget, not merely a technical task. Inputs include affected route/operation, user symptom, project profile, load/devices, available logs/metrics, and a safe profiling environment.

## Procedure
1. Select task-relevant success metrics and a reproduction scenario: CWV p75, TTFB, bundle KiB, API p95, query count, memory, battery, or startup.
2. Record baseline conditions: hardware/network, cold/warm cache, release/development mode, and sample size.
3. Form hypotheses from profiler/trace/EXPLAIN/waterfall/heap evidence; rank bottlenecks by impact.
4. For web, inspect server waterfalls, render critical path, images/fonts, hydration, blocking tasks, layout shifts, cache/invalidation, and offscreen work as relevant.
5. For backend/data, inspect N+1, query-plan-based indexes, pooling, timeouts, backpressure, and batching. Caches need TTL/invalidation and personal-data protection.
6. For mobile, inspect startup, frame jank, main-thread work, memory, wakeups/network/battery, and resource size with platform-appropriate tools.
7. Change one bottleneck per iteration while preserving behavior, consistency, security, and accessibility.
8. Repeat comparable measurements; check correctness, errors, and relevant regressions. State uncertainty explicitly.
9. Record metrics, commands, profiles, and trade-offs. One Lighthouse run is not field p75 or a guarantee for all users.

## Output and verification
Update the existing performance report or use PERFORMANCE_AUDIT.md when appropriate. Include bottleneck → change → comparable measurements, diff, regression evidence, and affected budget. Completion requires a baseline, evidence-supported hypothesis, comparable after measurement, working functionality, and stated measurement limits.
## Core rules
Use the sibling [core workflow](../unified-development-standard/SKILL.md) once per context; reuse it if already read. Then read only relevant sections of: 17-PERFORMANCE. Apply core 00-GOVERNANCE scope. Do not recursively rediscover profiles/core or load the full corpus for a local edit. If core is unavailable, report that limitation without claiming compliance with unread rules.

Versions

The database has no other skills named uds-performance-optimization.

Database snapshot: 13.11.2026 · package version 937abb0bcd7b (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100performance-optimization
    Measure, diagnose, and improve application, API, database, frontend, build, and infrastructure performance. Use when latency, throughput, memory, CPU, bundle size, startup time, or operating cost is a material concern.
  • 95performance-profiling
    Guide performance profiling with Instruments, diagnose hangs, memory issues, slow launches, and energy drain. Use when reviewing app performance or investigating specific bottlenecks.
  • 100performance-profiling
    Finds and fixes backend and application performance problems by measuring first - define the target metric, reproduce under realistic load, profile CPU, memory, I/O and locks, fix the biggest bottleneck, re-measure, and add a regression guard. Use when code or a service is slow,…
  • 90uds-backend
    Use when changing server-side business operations, HTTP APIs, integrations, authorization, or backend reliability.
  • 100performance-profiling
    Use when a ticket is about speed or resource use — a slow endpoint, a hot loop, memory growth, a test suite that takes too long, "make X faster" — and the change must be driven by a measurement, not a hunch, and proven with a before/after number under the same conditions. Invoke…
  • 100performance-review
    Performance optimization analysis: CPU/memory profiling, caching strategies, database query optimization, connection pooling, concurrency patterns, memory leak detection, and throughput improvement. Use when code is slow, memory usage is high, latency needs reduction, or…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.