Screens prepared with AI

An AI assistant can prepare screens for a project in two ways:

Way	How it works
Screen package	The assistant prepares a package of pages, symbols, popups and layouts with the YTCC design package; you import it (see Import a screen package).
AI access (MCP)	An assistant that supports MCP connects to the project with an access key and edits the screens directly. See AI access (MCP).

In both ways the assistant works only on the design. It cannot read live values, alarms or trends and cannot send commands to the field.

Screen packages

The YTCC design package, supplied with YTCC, tells the assistant the package format, the objects it may use, the style guide and a check tool. The assistant asks for the purpose, the signal list, a reference drawing and the style, plans the pages, symbols with parameters, popups and layouts, checks the package until it has no errors and returns a zip with a short report.

• The package uses the project's own objects only; invented settings have no effect.
• A package does not create signals. It binds objects to signal names; names that are not in the project are listed at import and are bound later in the editor.
• Errors block the import; warnings need Import anyway.

Which way to choose

Situation	Way
The assistant runs on another computer, or the design is prepared before the project exists on the server	Screen package
You work with the assistant on the server and want to see and correct the result at once in the editor	AI access (MCP)

Good to know

• A package can also be applied by an assistant connected with AI access, with the tool apply_design_package; see What the assistant can do.
• Text roles stored with a design standard appear in the editor as Text role; see Object appearance.