goga-cells-by-brainstorm

Create Cells

Purpose

Creates new cells and modifies existing cells based on the architecture plan defined in the path printed by goga history path -f arch.md. Materializes the plan into the cell file structure: CODEMANIFEST, .usages/.

---

Phases

Phase 1: Load DSL specification and DSL application principles

Step 1: Load the DSL specification

To understand cell definitions and CODEMANIFEST file contents, invoke the goga-cell skill via the Skill tool. Use the goga-cell skill to:

• Understand cell structure — cell composition (CODEMANIFEST, .usages/), document organization (header, body, footer)
• Understand CODEMANIFEST directive purposes — responsibilities of Imports, Usages, Annotations, types, mutations, embeddings
• Verify syntactic correctness — key casing, signature rules, location constraints, declaration structure

Step 2: Load DSL application principles

To understand principles for working with cells and CODEMANIFEST files, invoke the goga-cookbook skill via the Skill tool. Use the goga-cookbook skill to:

• Determine whether to create a cell — when to extract a standalone cell versus extending an existing one
• Choose between Entity and Routine — when a type requires methods/properties versus a single operation
• Determine granularity — appropriate cell size, indicators of over- or under-splitting
• Select the Usages connection form — file, inline, or URL, and when each applies
• Establish the design order — design cells from leaves to root; cells without dependencies first
• Decide when to use mutations (Object::Target) and embeddings (->Entity: {}) versus Imports alone
• Write usage files in <cell_path>/.usages/ — structure, content, and quality guidelines

Step 3: Load language implementation rules

Invoke the goga-lang-disp skill via the Skill tool to obtain the target language skill. The language skill defines implementation conventions: cell structure, facade, signature rules, and naming. Examples in other skills may use naming conventions from one language (e.g., snake_case), while the target language requires different conventions (e.g., PascalCase). The language skill provides authoritative rules for the target language.