Run any Skill in Manus with one click

bottleneck-patterns

Stars2

Forks0

UpdatedJune 26, 2026 at 09:48

This skill should be used when the user describes slow response times, high CPU usage, memory pressure or leaks, database slowness, network issues, frame drops, ANR errors, battery drain, app jank, a performance regression after deploy, or app lagging under load; or asks "my database queries are taking forever", "why does my Flutter app stutter", "what's causing my API to slow down under load", or describes any observable performance symptom. Provides domain-specific bottleneck pattern recognition and diagnostic guidance for web, mobile (Android/iOS/Flutter), desktop, and API/backend applications.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

sembraniteam

sembraniteam/claude-plugins

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

More from this repository

same repository

parallel-debug

sembraniteam/claude-plugins

This skill should be used when the user invokes /debugging-workflow:parallel-debug, asks to "debug in parallel", "try all hypotheses at once", "spawn multiple agents for this bug", "investigate multiple root causes", "parallel hypothesis testing", "parallel investigation", "I can't figure out what's causing this and have a few theories", "investigate from multiple angles", "I have multiple theories about this bug", or reports a complex or intermittent bug where the root cause is unclear and multiple theories need testing simultaneously.

2026-07-112

design

sembraniteam/claude-plugins

This skill should be used when the user wants to design a new application's architecture or infrastructure — says "design my architecture", "help me plan the architecture", "create architecture diagrams", "I need to plan a new system", or is starting a new project and needs a structured design process. Also trigger when the user mentions HLD, LLD, API contracts, or system design. Guides from requirements gathering through capacity planning, technology selection, diagram generation, low-level design, document saving, and code skeleton implementation.

2026-07-102

implement

sembraniteam/claude-plugins

This skill should be used when the user wants to turn an approved architecture document into working code, or wants to generate/scaffold a project after a design or review session — says "implement the architecture", "scaffold the project", "generate the code from my architecture", "create project files from the design", "turn my architecture into code", "create the folder structure", "start implementation", "let's start coding", or "generate the project skeleton".

2026-07-102

review

sembraniteam/claude-plugins

This skill should be used when the user wants to review or revise an existing architecture, says "review my architecture", "audit my architecture", "check my architecture", "my architecture needs review", "update my architecture document", "revise the architecture", "architecture drift", "compare design vs implementation", "architecture is outdated", "architecture inconsistency", "check if my code matches my design", or wants to compare their architecture document against their current codebase. Also trigger when the user mentions their architecture document needs updating after new features were added or requirements changed.

2026-07-102

generate-branch

sembraniteam/claude-plugins

This skill should be used when the user invokes /git-helper:generate-branch, asks to "create a branch name", "name my branch", "what should I name this branch", "suggest a branch name", "what prefix should I use", "what branch should I create for this", "branch for ticket

2026-07-102

generate-commit

sembraniteam/claude-plugins

This skill should be used when the user invokes /git-helper:generate-commit, or asks to "generate a commit message", "write a commit for me", "what should my commit message be", "help me commit my changes", "suggest a commit message", "prepare a commit", "what commit type should I use", "stage and commit my changes", "commit all my changes", "I'm done working on this", "commit everything I did", "write a commit for my changes", or describes a change they just made and needs a commit message for it. Produces a conventional commit with type, scope, subject, optional body, and breaking change footer.

2026-07-102

name	bottleneck-patterns
description	This skill should be used when the user describes slow response times, high CPU usage, memory pressure or leaks, database slowness, network issues, frame drops, ANR errors, battery drain, app jank, a performance regression after deploy, or app lagging under load; or asks "my database queries are taking forever", "why does my Flutter app stutter", "what's causing my API to slow down under load", or describes any observable performance symptom. Provides domain-specific bottleneck pattern recognition and diagnostic guidance for web, mobile (Android/iOS/Flutter), desktop, and API/backend applications.
argument-hint	[domain] e.g. web \| mobile \| api \| database \| memory \| cpu \| network
allowed-tools	Read

Bottleneck Patterns

Performance Bottleneck Patterns

Identify which domain matches the symptom, then apply the corresponding pattern. For the full symptom → pattern → fix lookup tables, see references/bottleneck-lookup.md.

Domain Quick Reference

Response Time: Tail latency (p99 >> p50), throughput ceiling, cold-path slowness, periodic spikes

Web: Render-blocking resources, large JS bundles, layout thrashing, missing CDN, high INP

API/Backend: N+1 queries, missing indexes, connection pool exhaustion, synchronous I/O, over-fetching

Memory: Monotonic heap growth (leak), burst allocation GC churn, premature promotion, unbounded cache

CPU: Busy-wait loops, hot codec (serialization), uncached regex, lock contention

Mobile (Android): ANR on main thread, UI jank, overdraw, WakeLock abuse, battery drain from background work

Mobile (iOS): Main thread I/O, deep autolayout graph, retain cycles, Core Data on main thread

Mobile (Flutter): Expensive build() methods, shader compilation jank, large isolate messages, heavy list cells

Networking: Chatty API, missing compression, no connection reuse, oversized images, sequential loading

Database: Missing indexes (EXPLAIN ANALYZE first), SELECT *, missing composite index, ORM over-fetching

Diagnostic Approach

Match the symptom to a domain from the quick reference above
Look up the specific pattern and fix in references/bottleneck-lookup.md
Confirm with data before implementing: run EXPLAIN ANALYZE, attach a profiler, or measure with a benchmark
Apply the impact-matrix skill to prioritize multiple findings

Cross-Domain Signals

Some symptoms span multiple domains — check these cross-cutting patterns first:

Periodic latency spikes → GC pause + background job + cache invalidation (all three at once)
Slow under load only → thread/connection pool contention (not a code bug)
Fast p50, slow p99 → lock wait or GC stop-the-world on a fraction of requests
Memory growing then dropping → burst allocation, not a leak; reduce short-lived object creation
First request slow, subsequent fast → cold-path (JIT, DNS, connection init) — warm up or cache

Additional Resources

references/bottleneck-lookup.md — Full symptom → pattern → fix lookup tables by domain (response time, web, API/backend, memory, CPU, mobile, networking, database)