automotive-infotainment

Guides infotainment ECU development across connectivity, audio, HMI, and navigation topics per AUTOSAR and ISO 26262.

7|2|Updated May 19, 2026
One-click install
npx skills add https://github.com/pangzhenying2025/hermes-automotive-skills --skill automotive-infotainment-pangzhenying2025
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: automotive-infotainment
Source: https://github.com/pangzhenying2025/hermes-automotive-skills/tree/main/skills/automotive-infotainment
Command: npx skills add https://github.com/pangzhenying2025/hermes-automotive-skills --skill automotive-infotainment-pangzhenying2025

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Automotive infotainment development spans many subsystems—audio, Bluetooth, Wi-Fi, navigation, smartphone integration, OTA updates—each requiring compliance with AUTOSAR, ISO 26262, ISO 21434, and ASPICE. This Skill consolidates 252 topic-level instruction sets into one reference so engineers can apply a consistent, standards-aligned workflow to any infotainment task. ## Core Features & Use Cases - 14 Infotainment Subdomains: Covers app integration, audio systems, Bluetooth, connectivity, display systems, gesture control, HMI design, navigation, NFC, OTA updates, smartphone integration, telematics, voice control, and Wi-Fi. - Standards-Aligned Workflow: Each topic follows a four-step approach—analyze requirements against automotive standards, design with AUTOSAR patterns, implement with safety and security considerations, and validate per ISO 26262. - Defined Deliverables: Produces technical specifications, C/C++/model implementations, test cases and results, and safety documentation. - Use Case: When implementing a smartphone integration feature for a production head unit, use this Skill to structure the requirements analysis, AUTOSAR-compliant design, and ISO 26262 validation deliverables. ## Quick Start Ask the agent to design an AUTOSAR-compliant Bluetooth audio streaming component for an infotainment ECU with ISO 26262 validation deliverables.

Frequently Asked Questions about automotive-infotainment

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

FAQPage Schema
How do I develop an automotive infotainment feature compliant with ISO 26262?▼

Follow the four-step workflow: analyze requirements against automotive standards, design using AUTOSAR patterns, implement with safety and security considerations, then validate per ISO 26262. Deliverables include a technical specification, implementation, test cases, and safety documentation.

What infotainment subsystems does this skill cover?▼

It covers 14 subdomains: app integration, audio systems, Bluetooth, connectivity, display systems, gesture control, HMI design, navigation, NFC, OTA updates, smartphone integration, telematics, voice control, and Wi-Fi, with 18 topics each.

Which automotive standards apply to infotainment software development?▼

The skill references ASPICE Level 3 for process maturity, AUTOSAR 4.4 for software architecture, ISO 26262 for functional safety, and ISO 21434 for cybersecurity. These standards govern design, implementation, and validation activities.

What tools are required for AUTOSAR infotainment development?▼

The skill lists an AUTOSAR toolchain, MATLAB/Simulink for model-based design, static analyzers such as Polyspace or Klocwork, and Vector CANoe/CANalyzer for network testing and validation.

What are the limitations of this infotainment guidance?▼

The 252 topic sections share a generic repeated template rather than deep per-topic technical detail, so engineers must supply domain-specific design decisions themselves. It also assumes AUTOSAR architecture adherence and real-time CPU/memory constraints.