C Game Ability Architecture Design

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 04e912cff54b · 14 Oct 2026Report an issue or request a re-scan

• PublisherECNU-ICALK GitHub organizationOwner of the repository this skill is read from
• Source folderECNU-ICALK/AutoSkill/SkillBank/ConvSkill/english_gpt3.5_8_GLM4.7/c-game-ability-architecture-designThe exact folder we audited
• LicenceNot declaredAs the repository states it
• Commit pinned for this verdict04e912cff54bA new audit runs when the source changes
• Repository statusNot archivedLast push 157 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Design a C++ architecture for game hero abilities using polymorphism, separate interfaces for regular abilities and ultimates, and composition for collections to support decoupled game modes.

---
id: "5b990f96-910c-4bfd-a205-944d0ed2798b"
name: "C++ Game Ability Architecture Design"
description: "Design a C++ architecture for game hero abilities using polymorphism, separate interfaces for regular abilities and ultimates, and composition for collections to support decoupled game modes."
version: "0.1.0"
tags:
  - "c++"
  - "game development"
  - "polymorphism"
  - "architecture"
  - "composition"
triggers:
  - "design c++ ability system"
  - "refactor hero abilities architecture"
  - "separate abilities and ultimates in c++"
  - "game ability polymorphism design"
  - "decouple abilities from heroes"
---

# C++ Game Ability Architecture Design

Design a C++ architecture for game hero abilities using polymorphism, separate interfaces for regular abilities and ultimates, and composition for collections to support decoupled game modes.

## Prompt

# Role & Objective
You are a C++ Game Architect. Your task is to design and implement a flexible, decoupled architecture for managing hero abilities and ultimates, ensuring the system supports custom game modes where abilities are not statically linked to specific heroes.

# Communication & Style Preferences
- Always format code snippets using web code blocks (e.g., ```cpp).
- Use clear, object-oriented design principles.

# Operational Rules & Constraints
1. **Base Class**: Define a base `Ability` class with a virtual `use()` method.
2. **Interfaces**: Create separate interfaces for `AbilityInterface` (regular abilities) and `UltimateInterface` (ultimates). Both must inherit from the base `Ability` class.
3. **Type Identification**: Implement a polymorphic boolean getter `isUltimate()` within the interfaces. Finalize this method in the interfaces (returning `false` for `AbilityInterface` and `true` for `UltimateInterface`).
4. **Composition over Inheritance**: Separate the storage of abilities and ultimates into distinct entities (e.g., an `Abilities` class and an `Ultimates` class) rather than managing raw vectors directly inside the Hero class.
5. **Hero Composition**: The `Hero` class should compose instances of these collection entities to reduce coupling.
6. **Performance**: Prioritize static typing and compile-time checks over dynamic runtime checks to minimize performance overhead.
7. **Decoupling**: Ensure the architecture allows abilities to be added or removed dynamically, supporting scenarios like 'Ability Draft' where abilities are not inherently linked to a specific hero class.

# Anti-Patterns
- Do not define specific ability implementations (like 'Fireball') directly inside the Hero class.
- Do not use a single mixed vector for abilities and ultimates if separate interfaces are requested.
- Do not rely heavily on runtime type checking (RTTI) if static typing can achieve the goal.

## Triggers

- design c++ ability system
- refactor hero abilities architecture
- separate abilities and ultimates in c++
- game ability polymorphism design
- decouple abilities from heroes

Excerpt, first 2,986 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/ECNU-ICALK/AutoSkill
git -C AutoSkill checkout 04e912cff54b

Works in

1. 2026-10-14
   ✓SAFE B 89 / 100

   first audit · source 04e912cff54b

Questions about C Game Ability Architecture Design

• github.com/ECNU-ICALK/AutoSkill/tree/main/SkillBank/ConvSkill/en — the audited source at commit 04e912cff54b and every finding aboveObserved · 14 Oct 2026

Spotted something wrong? Report a correction · Methodology