egorfedorov/slot-casino-game-developer-skills-for-stake-engine

cpp-engine-core

Develop and harden C++ engine core systems with correctness, stability, and performance controls. Use when implementing engine subsystems, refactoring core runtime paths, enforcing contract boundaries, or validating engine-core readiness.

First seen Mar 10, 2026

Installation

$ npx skills add egorfedorov/slot-casino-game-developer-skills-for-stake-engine --skill cpp-engine-core

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from egorfedorov/slot-casino-game-developer-skills-for-stake-engine · top by installs.

npx skills add egorfedorov/slot-casino-game-developer-skills-for-stake-engine

Browse all from egorfedorov/slot-casino-game-developer-skills-for-stake-engine

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 53
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,667 B
  • docs SUMMARY.md 261 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 14 installs

SKILL.md

C++ Engine Core

Use this skill to implement robust C++ engine core changes with strict correctness gates.

Workflow

  1. Define scope and constraints.
  • Define subsystem scope, invariants, and API boundaries.
  • Capture objective metrics, bounds, and release blockers.
  1. Design implementation plan.
  • Design module-level changes with safety/performance implications.
  • Keep ownership and dependency boundaries explicit.
  1. Execute and iterate.
  • Implement in small, traceable increments.
  • Record run/build context for reproducibility.
  1. Validate contract integrity.
  • Validate invariants, failure behavior, and benchmark regression gates.
  • Treat contract breaches as blockers.
  1. Prepare handoff.
  • Deliver patch map, risk notes, and verification commands.
  • Include exact commands and acceptance criteria.

Output Contract

Return:

  1. Context: goals, assumptions, constraints.
  2. Validation: pass/fail checks and key deltas.
  3. Changes: concrete file-level updates.
  4. Commands: commands and expected outputs.
  5. Risks: unresolved issues and limits.

References

  • references/workflow.md: detailed execution flow.
  • references/checklist.md: sign-off checklist.

Execution Rules

  • Keep decisions measurable and reversible.
  • Keep validation criteria explicit before iteration.
  • Escalate invariant breaks and regression-risky changes as blockers.