# Simscape Write Ssc

Use when writing or editing Simscape Language (.ssc) source files, components...

- Repository: https://github.com/matlab/simulink-agentic-toolkit (1305 stars)
- Category: Writing
- License: see repository
- Last updated: 2026-10-29
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add matlab/simulink-agentic-toolkit --skill simscape-write-ssc -g -a claude-code -y`
Codex: `npx skills add matlab/simulink-agentic-toolkit --skill simscape-write-ssc -g -a codex -y`
Cursor: `npx skills add matlab/simulink-agentic-toolkit --skill simscape-write-ssc -g -a cursor -y`
Gemini CLI: `npx skills add matlab/simulink-agentic-toolkit --skill simscape-write-ssc -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add matlab/simulink-agentic-toolkit`

## Description

Use when writing or editing Simscape Language (.ssc) source files, components, domains, or functions. Triggers include: model a physical component in .ssc; write physical equations for a Simscape block; add or modify physics or parameterization options in a Simscape component; build a composite component. Also use for validating .ssc syntax, fixing Simscape Language errors, or converting governing equations into working Simscape component code. Do NOT use for configuring or connecting existing Simscape blocks in a Simulink model, that is model building, not language authoring.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Simscape Language Authoring

Write .ssc files (components, domains, functions) that pass validation and are
physically correct.

## When to Use

- Writing a new .ssc component, domain, or function from scratch
- Adding or modifying physics, equations, or parameterization in an existing .ssc file
- Converting governing equations into a working Simscape component
- Adding mode charts, events, or switching logic to a component
- Building a composite component that connects subcomponents together
- Fixing Simscape Language syntax or validation errors

## When NOT to Use

- Configuring or connecting existing Simscape blocks in a Simulink model, use
  `building-simulink-models` instead
- Simulating a model or inspecting results, use `simulating-simulink-models`
- Setting block parameters from MATLAB or a script without editing .ssc source

---

# Workflow

## Designing a component

Below are the sections that make up a Simscape component. Include only what is needed.

### `nodes`, `inputs`, `outputs`

- **`nodes`**, quantity participates in bilateral energy exchange (the network
  enforces Across equalization + Through summation).
- **`inputs`**, physical signal imposed from outside (control signal, environment).
- **`outputs`**, physical signal for a measurement or computed result.

Node ports have a domain. Reuse an existing one, especially foundation; author a custom
domain only when none covers the physics.

| Physics | Domain path |
|---|---|
| Electrical (single-phase) | `foundation.electrical.electrical` |
| Rotational mechanical | `foundation.mechanical.rotational.rotational` |
| Translational mechanical | `foundation.mechanical.translational.translational` |
| Thermal (heat transfer) | `foundation.thermal.thermal` |

For fluid domains, polyphase electrical, position/angle-based mechanical variants, or any
domain not in the table, you must read: `references/foundation/domain-selection.md`.

### `parameters`, `variables`

The rest: https://github.com/matlab/simulink-agentic-toolkit/blob/HEAD/skills-catalog/physical-modeling/simscape-write-ssc/SKILL.md