init-boot-sequence-expert

What problem does it solve?

Android boot failures and daemon misbehaviors are hard to debug because init spans system, vendor, and device overlays with strict timing, SELinux, and property constraints. This skill captures the init lifecycle, .rc syntax, property scoping, and vendor overlay expectations so you can diagnose why a service never starts, sockets are missing, or props trigger too early without wandering through irrelevant subsystems.

Core Features & Use Cases

• Path-aware boot architecture: The path scope table maps every relevant directory from system/core/init/ to vendor and device overlays, and the boot sequence intelligence summarizes how early-init, post-fs, and boot phases transition so you know where to look first.
• Syntax, property, and SELinux guardrails: The .rc reference catalog explains service blocks, actions, commands, property namespaces, and socket details, while the forbidden actions section keeps you aligned with SELinux-friendly domains, property timing, and vendor edit rules.
• Validation tooling and handoffs: Use the validate_rc_syntax.py script to flag missing users, seclabels, or bad triggers, and rely on the handoff table to defer SELinux, HAL, framework, build, or kernel issues to the right L2 expert when boot problems cross domains.

Quick Start

Use the init-boot-sequence-expert to scan adb logcat for init failures, align the triggers with documented init rc rules, and update vendor overlays with validated service definitions.