Claude Code plugin for Siemens engineering workflows

Bring structure to TIA Portal automation.

Totally Integrated Claude routes engineering tasks to the correct implementation path, keeping Python TIA Scripting and C# Openness workflows separate and correctly scoped.

TIA Portal V17+ Python TIA Scripting C# Openness Skill-based routing
Get started See example prompts 
Task: Read all PLC tag tables from an open TIA project

→ Load routing skill: tia-openness-roadmap
→ Decide execution path:
  • Python for routine engineering access
  • C# for advanced object-model work
→ Activate the correct domain skill
→ Return implementation guidance

Output:
✓ Minimal setup
✓ Correct API path
✓ Lower agent confusion
✓ Faster engineering iteration

What this project actually solves

Most TIA automation work fails before coding starts: the agent picks the wrong API surface, the wrong language, or the wrong abstraction level. This project routes the task correctly first.

Correct path selection

Routine PLC, HMI, and project tasks are pushed toward Python TIA Scripting. Advanced object-model workflows move toward C# Openness.

Skill-based decomposition

Instead of one overloaded prompt, the plugin splits the TIA domain into focused skills for projects, devices, PLC, HMI, networks, drives, import/export, and Add-Ins.

Better authoring ergonomics

An LSP layer adds code intelligence for Siemens PLC source files, reducing friction when generating, reviewing, or transforming code artifacts.

Why this approach works

TIA Portal automation is not one uniform problem space. Different tasks belong on different API paths, and the plugin is designed around that constraint from the start.

1

Route the task before writing code

The first decision is not syntax. It is whether the task belongs on Python TIA Scripting or C# Openness.

2

Use the lowest-friction path

Routine engineering work should stay fast and practical. Advanced object-model workflows can move to the heavier path only when needed.

3

Keep the domain context narrow

Focused skills for PLC, HMI, devices, networks, and import/export reduce ambiguity and improve output quality.

What users get in practice

The routing model removes a decision that currently costs time on every automation project.

✓
Clear entry point: start from one routing skill instead of guessing the correct implementation layer.
Better implementation choices: use Python where speed matters and C# where deeper access is required.
Faster first result: move from engineering task to a valid technical direction with less backtracking.

Core skill layout

Each skill covers a focused slice of the TIA domain. The routing skill selects and loads only what the current task requires.

tia-openness-roadmap

Entry routing skill. Chooses the implementation path and loads the correct domain context first.

tia-python

Python TIA Scripting for practical PLC, HMI, library, and project lifecycle operations.

tia-csharp-common

C# Openness foundations: attach, transactions, exclusive access, and safe lifecycle patterns.

addin-operations

Authoring and deploying TIA Portal Add-Ins with a clearer development workflow.

tia-project-general

Project lifecycle, archive/open/save flows, multiuser context, language, and diagnostics concerns.

tia-devices-general

Device catalog access, hardware hierarchy traversal, software containers, slot, and subslot operations.

tia-plc-operations

PLC blocks, tags, UDTs, software units, compare/download flows, and security-oriented operations.

tia-hmi-operations

Unified HMI screens, items, tags, scripts, and runtime-oriented engineering work.

tia-networks

Network and subnet configuration, interface assignment, and connection-level engineering operations.

tia-simatic-drives

Drive object access, parameter handling, and drive-specific engineering workflows within TIA Portal.

tia-import-export

XML-based import and export for blocks, tags, HMI data, and cross-project transfer workflows.

Routing workflow

Every task enters through the routing skill. The path to Python or C# is selected based on what the API surface actually requires, not what feels more familiar.

User Task Any TIA Portal request tia-openness- roadmap Classify task type Select language path Load domain skill Python path Routine engineering C# path Advanced object model DOMAIN SKILLS tia-project-general tia-devices-general tia-plc-operations tia-hmi-operations tia-networks tia-simatic-drives tia-import-export

Quick Start

claude plugin marketplace add Czarnak/totally-integrated-claude

Point Claude Code at the cloned skills directory and issue a task-oriented prompt. The routing skill handles path selection automatically.

Baseline environment

All three implementation paths require an active TIA Portal installation. Each path adds its own environment layer on top.

Area Baseline
TIA Portal V17 or later
Python path TIA Scripting Python package available
C# path Openness assemblies and .NET environment available
LSP path Siemens PLC source files available locally

Example prompts

These prompts show how natural language maps to a specific implementation path and domain skill.

PLC engineering

How do I read all PLC tag tables from an open TIA Portal project?

HMI export

Export all WinCC Unified screens and HMI tags from the current project.

Device hierarchy

Create a C# Openness workflow to traverse devices, device items, slots, and subslots.