Fireball Architecture

Codify Fireball architecture patterns and coding conventions for embedded projects.

1|Updated Dec 2, 2025

Search Tags:#architecture #embedded #design-principles #coding-standards #ioc #three-tier #fireball

Ready to run

npx skills add https://github.com/kmt-t/fireball --skill fireball-architecture

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Fireball Architecture
Source: https://github.com/kmt-t/fireball/tree/main/.agent/skills/fireball_architecture
Command: npx skills add https://github.com/kmt-t/fireball --skill fireball-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fireballプロジェクト固有のアーキテクチャパターン、コーディング規約、設計原則の一貫性を確保します。

Core Features & Use Cases

統一された命名規則と構造ルール: クラス/構造体/関数/変数の命名規則とファイル配置を標準化します。
設計原則の適用: IoC、3-Tier分離、RAII、データ/ビューの分離などの方針を組織全体で適用します。
ユースケース: 新規モジュールの設計時に、規約に沿ったアーキテクチャ案を迅速に評価・決定します。

Quick Start

Fireball アーキテクチャ設計を開始する際、以下の手順に従います。

このスキルの規約を参照してモジュール設計を実施します。
命名は snake_case を適用し、インターフェイスと実装を分離します。
IoC と 3-Tier 分離を適用し、設計決定をこの SKILL.md に記録します。

Frequently Asked Questions about Fireball Architecture

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

FAQPage Schema

How do I enforce coding standards and naming conventions for embedded system architecture?▼

To enforce embedded system architecture coding standards, apply standardized naming conventions like snake_case and separate interfaces from implementations. This ensures structural consistency across modules and standardizes file placement for system-level development.

What design principles should I apply when creating new modules for embedded projects?▼

Apply design principles including Inversion of Control (IoC), three-tier separation, RAII, and data/view separation when creating new modules. These principles guide architecture decisions and ensure project-wide consistency in embedded contexts.

How do I structure a three-tier architecture for embedded system modules?▼

Structure three-tier architecture for embedded modules by enforcing strict separation between interface definitions and implementations. Use standardized naming conventions and apply IoC patterns to isolate functional layers within system-level components.

Does this architecture guidance cover specific embedded component structures like COOS and IPC?▼

Yes, this architecture guidance covers specific embedded component structures including COOS, IPC, and vSoC. It provides structural rules and design principles tailored to these system-level development contexts for consistent module implementation.

What is the best way to standardize file placement and naming rules across an embedded codebase?▼

The best way to standardize file placement and naming rules is to codify structural conventions for classes, structs, functions, and variables. Enforcing snake_case naming and interface separation ensures consistent architecture across the codebase.