axiom-audit-energy

Analyze iOS and macOS source code for energy-intensive anti-patterns causing battery drain.

34|2|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/DengNaichen/Stet --skill axiom-audit-energy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: axiom-audit-energy
Source: https://github.com/DengNaichen/Stet/tree/main/.agents/skills/axiom-audit-energy
Command: npx skills add https://github.com/DengNaichen/Stet --skill axiom-audit-energy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill identifies energy-inefficient code patterns, such as excessive background activity, unoptimized timers, and continuous location tracking, which lead to rapid battery drain and system terminations.

Core Features & Use Cases

  • Energy Anti-Pattern Detection: Scans for 8 specific categories of power-intensive code, including timer abuse, polling, and animation leaks.
  • Lifecycle Mapping: Visualizes how the application manages background modes, network requests, and hardware sensors.
  • Health Scoring: Provides a quantitative Energy Health Score to categorize the app as Efficient, Wasteful, or Draining.
  • Use Case: Use this during pre-release testing to ensure that background tasks and location services are properly gated, preventing the app from being killed by the system for excessive resource usage.

Quick Start

Run the axiom-audit-energy skill to perform a full energy audit on the current repository and generate a health report.

Frequently Asked Questions about axiom-audit-energy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect battery-draining code patterns in my iOS app?

To detect battery-draining code patterns in an iOS app, analyze the source code for energy anti-patterns like timer abuse, polling, and animation leaks. This process evaluates background tasks and hardware sensor usage to identify power-intensive code causing rapid battery drain.

Why does my macOS app get killed by the system watchdog for excessive resource usage?

Your macOS app gets killed by the system watchdog when background tasks and location services are not properly gated, leading to excessive resource usage. Evaluating background mode management and hardware sensor usage across the application lifecycle mitigates these energy-intensive anti-patterns.

How do I audit background task management and timer discipline for power efficiency?

Audit background task management and timer discipline by scanning source code for 8 specific categories of power-intensive code, including timer abuse and polling. This evaluates lifecycle management and provides an Energy Health Score to categorize the app as Efficient, Wasteful, or Draining.

Can I check if continuous location tracking violates system power efficiency standards before release?

Yes, you can check continuous location tracking against system power efficiency standards during pre-release testing. Scanning source code for unoptimized location services and background activity identifies energy-intensive anti-patterns, preventing the app from being killed by the system for excessive resource usage.

What is the best way to prevent rapid battery drain from unoptimized timers and animation leaks?

The best way to prevent rapid battery drain from unoptimized timers and animation leaks is to scan the source code to identify these specific energy anti-patterns. This provides actionable remediation steps to ensure compliance with system power efficiency standards.

Does energy anti-pattern detection work with existing iOS and macOS repositories?

Yes, energy anti-pattern detection works with existing iOS and macOS repositories by analyzing the source code directly. It visualizes how the application manages background modes, network requests, and hardware sensors to generate a full energy health report.