mirror of https://github.com/Donchitos/Claude-Code-Game-Studios.git synced 2026-10-16 01:37:05 +00:00

Files

T

DonchitosandClaude Opus 5.5 be8993bbc5 Release 1.1.3 — long skills keep their later steps

Fix release for 1.1.2: the 14 longest skills keep their later phases
after a compaction, a question nobody answered is never taken as an
answer, settings read the same from a subfolder, the commit check works
for a project in a subfolder of a larger repository, every skill opens
with a title, and the shipped allow rules no longer approve deleting a
branch or writing files without asking. Details in CHANGELOG.md; upgrade
steps in UPGRADING.md (v1.1.2 → v1.1.3).

Refs #83
Refs #133

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0185en4t76fPn7315q4c3nko

2026-10-08 17:52:48 +11:00

1017 B

Raw Blame History

/create-architecture — Phase 4: API Boundaries

Part of /create-architecture. SKILL.md names when to read this file; the settings it resolved and the rules under its later headings still apply here.

Phase 4: API Boundaries

Define the public contracts between modules. For each boundary:

What is the interface a module exposes to the rest of the system?
What are the entry points (functions/signals/properties)?
What invariants must callers respect?
What must the module guarantee to callers?

Write in pseudocode or the project's actual language (from technical preferences). These become the contracts programmers implement against.

Engine awareness check: If any interface uses engine-specific types (e.g. Node, Resource, Signal in Godot), flag the version and verify the type exists and has not changed signature in the target engine version.

Get user approval on the API boundaries, then record them in production/session-state/active.md; they are written at Phase 7.

1017 B Raw Blame History

/create-architecture — Phase 4: API Boundaries

Phase 4: API Boundaries

1017 B

Raw Blame History