Performance Optimizer
Software development skill, available on Zeplik
Performance Optimizer is a ready-to-run software development skill on Zeplik. Measures the bottleneck, applies the fix, and proves the improvement with before/after numbers. Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer. It returns a structured document you can keep and reuse: bottleneck found, fix applied, before/after measurement, verification.
The Performance Optimizer skill loads automatically when your request matches it, or you can invoke it directly by typing /performance-optimizer in any chat. It works with attachments, connectors, and any model that supports the task, so you get the same expert method every time without setting anything up.
What the Performance Optimizer skill can do
- Profile app to locate the exact bottleneck with evidence
- Fix N+1 queries, missing indexes, and slow API calls
- Verify improvement with before and after timing numbers
- Apply frontend fixes like memoization, lazy loading, and code splitting
Try these prompts on Zeplik
Pick a prompt to open it in the Zeplik app. If you are not signed in yet, your prompt is waiting for you the moment you do.
How the Performance Optimizer skill works
Performance Optimizer
Find and fix performance bottlenecks. Measure, optimize, verify. Make it fast.
When to Use
App is slow or laggy; page load times high; API responses slow; database queries take too long; user mentions "slow", "lag", "performance", or "optimize".
The Optimization Process
- Measure first -- never optimize without a baseline. Time page load, API response, query time, function execution, memory, network requests.
- Find the bottleneck -- profile to locate the slow part. Browser DevTools Performance tab (long red tasks), Node
--prof, databaseEXPLAIN ANALYZE. - Optimize the slowest thing first (biggest impact), then measure again.
Common Optimizations
Database
- N+1 queries: replace per-row lookups in a loop with a single JOIN / populate.
- Missing index:
EXPLAINshowsSeq Scan-> add index on the filtered column -> re-check forIndex Scan. SELECT *: fetch only needed columns.- No pagination: use
LIMIT/OFFSETinstead of loading all rows.
API
- No caching: cache expensive computations with a short TTL instead of hitting the DB every request.
- Sequential awaits: run independent calls with
Promise.all(total becomes the max, not the sum). - Large payloads: return only the fields the client needs.
Frontend
- Unnecessary re-renders: memoize components (
React.memo) and expensive values (useMemo). - Large bundle: import only what you use (
lodash/debounce, not all oflodash). - No code splitting: lazy-load heavy components (
React.lazy+import()). - Unoptimized images: WebP,
srcset,loading="lazy", explicit dimensions.
Algorithms & Memory
- Inefficient algorithm: replace O(n^2) nested loops with an O(n)
Set/Mappass. - Repeated calculations: memoize results across calls/renders.
- Memory leak: clean up event listeners/timers in effect teardown.
- Large data in memory: stream large files instead of reading them whole.
Measuring Impact
Always capture before and after (e.g. 2341ms -> 23ms after adding an index). State the improvement factor.
Performance Budgets
Page Load: < 2s API Response: < 200ms DB Query: < 50ms
Bundle Size: < 200KB Time to Interactive: < 3s
Quick Wins
Add DB indexes on hot columns, enable gzip, cache expensive ops, lazy-load images/components, use a CDN, minify JS/CSS, drop unused deps, paginate, optimize images, enable HTTP/2.
Checklist
- Measured current performance
- Identified the bottleneck
- Applied the optimization
- Measured the improvement
- Verified functionality still works, no new bugs
- Documented the change
When NOT to Optimize
Premature optimization; micro-optimizations that save 1ms on a 5s page; readability sacrificed for tiny gains; it's already fast enough.
Output
A short optimization report: the bottleneck identified (with evidence), the fix applied, before/after measurements proving the gain, and confirmation that behavior is unchanged. Fix the biggest bottleneck first; follow the 80/20 rule.
How to use the Performance Optimizer skill
Sign in to Zeplik
Create a free Zeplik account or sign in. New accounts start with free credits, so you can try the Performance Optimizer skill right away.
Describe your software development task
Ask in plain language, or type /performance-optimizer to invoke the skill directly. Zeplik recognizes the Performance Optimizer skill and applies its method.
Review and refine the result
Zeplik returns a structured document you can edit, download, and reuse. Ask follow-ups to refine it.
Source and credit
- Author
- davila7 community
- License
- MIT
Adapted from the open-source davila7/claude-code-templates project and tuned to run natively on Zeplik. View source on GitHub.
Frequently asked questions
- What is the Performance Optimizer skill?
- Performance Optimizer is a ready-to-run software development skill on Zeplik. Measures the bottleneck, applies the fix, and proves the improvement with before/after numbers. Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer. It returns a structured document you can keep and reuse: bottleneck found, fix applied, before/after measurement, verification.
- How do I use Performance Optimizer on Zeplik?
- Sign in to Zeplik and ask in plain language, or type /performance-optimizer in any chat to invoke it directly. The skill applies its method and returns a result you can refine in the same conversation.
- Which AI model does the Performance Optimizer skill use?
- Any model you choose. Zeplik works across every model in one chat, so the Performance Optimizer skill runs on your preferred model for the task.
- Where does the Performance Optimizer skill come from?
- The Performance Optimizer skill is adapted from the open-source davila7/claude-code-templates project (MIT) and tuned to run natively on Zeplik. The original source is linked on this page.
- How much does the Performance Optimizer skill cost?
- Using the skill is free to start. You only spend Zeplik credits when the assistant runs, and new accounts begin with free credits.
Related software development skills
- .NET BackendBuild ASP.NET Core 8+ backends with EF Core: auth, background jobs, production API patterns
- Advanced Git WorkflowsUse for advanced Git surgery: interactive rebase, cherry-pick, bisect, reflog recovery, and history cleanup before merging. Not for parallel worktree workflows (use using-git-worktrees).
- Adversarial Code ReviewHunt for bugs in code the user shares by assuming defects exist and attacking the code through several distinct lenses, then report severity-ranked findings with evidence. Use for "review this", "what could go wrong", "bug hunt", or pre-merge scrutiny of a change. Read-only, it reports problems and does not rewrite the code. Not for style cleanup (use simplify-code) or for writing new code.
- AI Agent FrameworksUse when building multi-agent systems or agent orchestration -- LangChain/LangGraph, agent team design, task coordination, pipelines. Not for authoring a Zeplik skill (use skill-creator).
- Algolia SearchAdd Algolia search: indexing strategies, React InstantSearch, relevance tuning, search-as-you-type
- Android CI/CDAutomate Android CI/CD to Google Play: keystore, GitHub Secrets, multi-stage release workflow for RN, Flutter, native
More on Zeplik
Try Performance Optimizer on Zeplik
Every model, one chat. Bring the Performance Optimizer skill into your next conversation and let the assistant do the work.