fusion-tea: Skill for Claude Code

Before executing this skill, read .agentic-mbse/claude.md in Claude Code or .agentic-mbse/codex.md in Codex. Resolve supporting paths from this skill’s installed directory; keep generated outputs in the project or a temporary directory. Read referenced skills from .agents/skills/<name>/SKILL.md when their guidance is needed.

SysML Conventions

Canonical syntax rules, naming conventions, and patterns for writing correct SysML v2 models.

Core Principle

Every SysML element is either a definition (reusable type in library/) or a usage (specific instance in designs/). This distinction drives naming, file placement, and calculation architecture. When unsure, ask: "Could this apply to multiple designs?" Yes = definition, No = usage.

When to Reference

• /design-model — when specifying SysML structure and syntax in designs
• /implement-model — when writing SysML files (pre-flight syntax validation)
• /plan-model — when reviewing planned changes for syntax compliance
• /audit-models — when checking naming and syntax conformance

Naming Conventions

Element	Convention	Example
Definitions	'Title Case' with single quotes	part def 'Pump'
Usages	snake_case	part my_pump : 'Pump'
Attributes	snake_case	attribute flow_rate : Real
Packages	lowercase_underscores	package thermal_components

Quoted names are fine. Multi-word quoted names ('Fusion Power Plant', 'HIF Driver') are supported everywhere a name appears. Codegen sanitizes them to valid identifiers (Fusion_Power_Plant) — the identifier is derived, you do not write it. Use the readable quoted name.

Definition vs Usage Rule

Decision question: "Could this apply to multiple designs?"

// DEFINITION — reusable type (library/)
part def 'Heat Exchanger' {
    attribute heat_transfer_area : Real;
    attribute pressure_drop : Real;
}

// USAGE — specific instance (designs/)
part primary_hx : 'Heat Exchanger' {
    attribute heat_transfer_area : Real = 50.0 [m^2];
}