Fetches axiom-energy-ref from charleswiltgen/axiom and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/axiom-energy-ref
Restart Cursor to activate axiom-energy-ref. Access via /axiom-energy-ref in your agent's command palette.
⚠
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Complete API reference for iOS energy optimization, with code examples from WWDC sessions and Apple documentation.
Related skills: axiom-energy (decision trees, patterns), axiom-energy-diag (troubleshooting)
Part 1: Power Profiler Workflow
Recording a Trace with Instruments
Tethered Recording (Connected to Mac)
1. Connect iPhone wirelessly to Xcode
- Xcode → Window → Devices and Simulators
- Enable "Connect via network" for your device
2. Profile your app
- Xcode → Product → Profile (Cmd+I)
- Select Blank template
- Click "+" → Add "Power Profiler"
- Optionally add "CPU Profiler" for correlation
3. Record
- Select your app from target dropdown
- Click Record (red button)
- Use app normally for 2-3 minutes
- Click Stop
4. Analyze
- Expand Power Profiler track
- Examine per-app lanes: CPU, GPU, Display, Network
Important: Use wireless debugging. When device is charging via cable, system power usage shows 0.
On-Device Recording (Without Mac)
From WWDC25-226: Capture traces in real-world conditions.
1. Enable Developer Mode
Settings → Privacy & Security → Developer Mode → Enable
2. Enable Performance Trace
Settings → Developer → Performance Trace → Enable
Set tracing mode to "Power Profiler"
Toggle ON your app in the app list
3. Add Control Center shortcut
Control Center → Tap "+" → Add a Control → Performance Trace
4. Record
Swipe down → Tap Performance Trace icon → Start
Use app (can record up to 10 hours)
Tap Performance Trace icon → Stop
5. Share trace
Settings → Developer → Performance Trace
Tap Share button next to trace file
AirDrop to Mac or email to developer
Interpreting Power Profiler Metrics
Lane
Meaning
What High Values Indicate
System Power
Overall battery drain rate
General energy consumption
CPU Power Impact
Processor activity score
Computation, timers, parsing
GPU Power Impact
Graphics rendering score
Animations, blur, Metal
Display Power Impact
Screen power usage
Brightness, content type
Network Power Impact
Radio activity score
Requests, downloads, polling
Key insight: Values are scores for comparison, not absolute measurements. Compare before/after traces on the same device.
Comparing Before/After (Example from WWDC25-226)
// Before optimization: CPU Power Impact = 21VStack{ForEach(videos){ video inVideoCardView(video: video)}}// After optimization: CPU Power Impact = 4.3LazyVStack{ForEach(videos){ video inVideoCardView(video: video)}}
Part 2: Timer Efficiency APIs
NSTimer with Tolerance
// Basic timer with tolerancelet timer =Timer.scheduledTimer( withTimeInterval:1.0, repeats:true){[weakself]_inself?.updateUI()}timer.tolerance =0.1// 10% minimum recommended// Add to run loop (if not using scheduledTimer)RunLoop.current.add(timer, forMode:.common)// Always invalidate when donedeinit{ timer.invalidate()}
let queue =DispatchQueue(label:"com.app.timer")let timer =DispatchSource.makeTimerSource(queue: queue)// Set interval with leeway (tolerance)timer.schedule( deadline:.now(), repeating:.seconds(1), leeway:.milliseconds(100)// 10% tolerance)timer.setEventHandler {[weakself]inself?.performWork()}timer.resume()// Cancel when donetimer.cancel()
For DispatchSourceTimer lifecycle safety and crash prevention, see axiom-timer-patterns.
Event-Driven Alternative to Timers
From Energy Efficiency Guide: Prefer dispatch sources over polling.
›Access to product documentation and roadmap tools (Jira, Notion, etc.)
›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
1Install product management skill
2Start with user story generation for known feature
3Progress to competitive analysis: research 2-3 competitors
4Use for roadmap prioritization: apply RICE/ICE scoring
5Draft stakeholder communications and refine based on feedback
6Build template library for recurring PM tasks
7Share effective prompts with product team
Common Pitfalls
⚠Not validating competitive research—verify facts before sharing
⚠Accepting user stories without involving engineering team
⚠Over-relying on frameworks without qualitative judgment
⚠Not customizing outputs to company culture and communication style
⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
+Validate research and competitive analysis with real data
+Collaborate with engineering when generating technical requirements
+Customize frameworks and templates to your company context
+Use skill for first drafts, refine with stakeholder input
+Document successful prompt patterns for PM tasks
+Combine AI efficiency with human judgment and intuition
✗ Don't
−Don't publish competitive analysis without fact-checking
−Don't finalize user stories without engineering review
−Don't make prioritization decisions solely on AI scoring
−Don't skip customer validation of generated requirements
−Don't ignore company-specific context and culture
💡 Pro Tips
★Provide context: company goals, constraints, customer feedback
★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
1Basic: user stories, feature specs, status updates
