erne-perf
- Repo stars 36
- License MIT
- Author updated Live
- Author repo everything-react-native-expo
- Domain
- AI
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 94 / 100 · audit passed
- Author / version / license
- @JubaKitiashvili · MIT
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- macOS · Linux · Windows
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Shell exec
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: erne-perf
description: ERNE — Performance profiling and optimization using the performance-profiler agent You are execu…
category: ai
runtime: no special runtime
---
# erne-perf output preview
## PART A: Task fit
- Use case: ERNE — Performance profiling and optimization using the performance-profiler agent You are executing the /erne-perf command. Use the performance-profiler agent to diagnose and fix performance issues. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Diagnostic Areas / 1. Rendering Performance (FPS) / 2. Time to Interactive (TTI)” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “ERNE — Performance profiling and optimization using the performance-profiler agent You are executing the /erne-perf command. Use the performance-profiler agent to diagnose and fix performance issues. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Diagnostic Areas / 1. Rendering Performance (FPS) / 2. Time to Interactive (TTI)” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, run shell commands, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, run shell commands, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source mentions slash commands such as `/erne-perf`; use them first when your agent supports command triggers.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, run shell commands, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Diagnostic Areas / 1. Rendering Performance (FPS) / 2. Time to Interactive (TTI)”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: erne-perf
description: ERNE — Performance profiling and optimization using the performance-profiler agent You are execu…
category: ai
source: JubaKitiashvili/everything-react-native-expo
---
# erne-perf
## When to use
- ERNE — Performance profiling and optimization using the performance-profiler agent You are executing the /erne-perf co…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Diagnostic Areas / 1. Rendering Performance (FPS) / 2. Time to Interactive (TTI)” and keep inference separate from source facts.
- read files, run shell commands, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "erne-perf" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Diagnostic Areas / 1. Rendering Performance (FPS) / 2. Time to Interactive (TTI)
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, run shell commands, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}/erne-perf — Performance Profiling
You are executing the /erne-perf command. Use the performance-profiler agent to diagnose and fix performance issues.
Diagnostic Areas
1. Rendering Performance (FPS)
- Check for unnecessary re-renders with React DevTools Profiler
- Identify components re-rendering without prop changes
- Look for missing
React.memo,useCallback,useMemo - Detect inline function/object creation in render
2. Time to Interactive (TTI)
- Analyze app startup sequence
- Check for heavy
useEffectchains on mount - Identify blocking operations on main thread
- Verify Hermes bytecode compilation
3. Bundle Size
- Run
npx react-native-bundle-visualizer - Identify large dependencies
- Check for unused imports and dead code
- Verify tree-shaking is working
4. Memory
- Check for listener/subscription cleanup in
useEffect - Identify large objects retained in closures
- Look for image caching issues
- Detect circular references
5. Animations
- Verify all animations use Reanimated (not Animated API)
- Check for JS thread bottlenecks in animation callbacks
- Identify layout thrashing during animations
- Measure actual FPS during animations
6. Hermes Engine
- Verify Hermes is enabled
- Check for unsupported JS features
- Profile with Hermes sampling profiler
- Analyze bytecode compilation output
Output Format
## Performance Metrics
| Metric | Current | Target | Status |
|--------|---------|--------|--------|
| JS FPS | 45 | 60 | ⚠️ |
| UI FPS | 58 | 60 | ✅ |
| TTI | 3.2s | <2s | ❌ |
| Bundle | 8.2MB | <5MB | ❌ |
## Critical Issues
[Issues that must be fixed]
## Optimization Opportunities
[Improvements ranked by impact]Notes
- If agent-device is available, measure actual FPS on device
- Reference
rules/common/performance.mdfor optimization patterns - Profile on real devices, not simulator/emulator
Decide Fit First
Design Intent
How To Use It
Boundaries And Review