Patedam/Juliet
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

updating coding guidelines + plan for full juliet serialization and entity system

Browse Source
This commit is contained in:
Patedam
2026-09-06 12:08:57 -04:00
parent 62e6284976
commit 1a045c3578
7 changed files with 4400 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.agent/rules/coding-guidelines.md
+1 -1
View File
@@ -5,7 +5,7 @@ trigger: always_on
Code compiles with all warning active and warning as errors.
use static_cast or reinterpret_cast but not parenthesis for casting.
No exceptions
Use [[nodiscard]]
Use [[nodiscard]] when risk of memory leak (anything returning pointer)
auto is allowed but when its a pointer add the * and when reference adds the &
Member variable are CamelCase
Types are CamelCase
.agent/skills/cpp_game_engine_programmer/SKILL.md
+1 -1
View File
@@ -11,7 +11,7 @@ trusted_commands:
You are a senior engine architect for the Juliet project. Your expertise lies in high-performance C++ systems programming, specifically within the context of game engine development. You value performance, memory efficiency, and maintainability.
## Coding Guidelines
You must follow the project's `coding-guidelines.md` (always loaded). Do not deviate from any rule. Pay special attention to `static_cast`/`reinterpret_cast` (never C-style casts), `auto*`/`auto&`, mandatory braces, and `[[nodiscard]]`.
You must follow the project's `coding-guidelines.md` (always loaded). Do not deviate from any rule. Pay special attention to `static_cast`/`reinterpret_cast` (never C-style casts), `auto*`/`auto&`, mandatory braces, and `[[nodiscard]]` when needed.
## Focus Areas
1. **High Performance**: Always consider cache locality and CPU cycle cost.
.agent/skills/debugger_programmer/SKILL.md
+1 -1
View File
@@ -11,7 +11,7 @@ trusted_commands:
You are a senior engine architect for the Juliet project. Your expertise lies in debugging C++ game engines. You add logs and use debug tricks to find the root cause of issues.
## Coding Guidelines
You must follow the project's `coding-guidelines.md` (always loaded). Do not deviate from any rule. Even in debug/diagnostic code, use proper casts, braces, and `[[nodiscard]]`.
You must follow the project's `coding-guidelines.md` (always loaded). Do not deviate from any rule. Even in debug/diagnostic code, use proper casts, braces, and `[[nodiscard]]` when needed.
## Workflows
- **Building**: Use the `/build` workflow to compile the project.