How I used Claude to build Ignition Perspective pages and Jython scripts with fewer hallucinations (99% of the time)

If you want an AI agent to stop making up fake system.* functions or writing Python 3 when the gateway needs Jython, I don’t think the answer is just “write a better prompt.”

The way I’m doing it is by creating a skill and running it through a goal loop in tools like Claude or Codex.

The skill gives the agent context for:

• how Ignition 8.1+ Jython actually works
• what valid Perspective page/view JSON should look like
• which system.* functions are real
• which patterns are project-specific
• how to test assumptions instead of guessing

Then you give the agent a way to interact with the gateway.

For Ignition 8.1+, that usually means writing your own API through the Web Dev module.

For Ignition 8.3, the built-in API should be a good starting point, but depending on what you want the agent to inspect or validate, you may still need extra endpoints.

The loop is basically:

1. Give the agent the skill.
2. Let it inspect the gateway/project.
3. Have it create a test plan before it writes anything.
4. Dry-run the change.
5. Validate the Perspective JSON, Jython, bindings, logs, SQL, etc.
6. Save the evidence.
7. Only promote what worked back into the skill.

I’ve had this run for over 36 hours validating scripts and tightening the skill from actual test results.

I also built a workflow where, if the agent does not have direct access to Ignition, it can generate an importable Perspective zip file that I can download and upload into the host gateway.

Some skills I’ve built that I think are useful:

• UDT creator/importer
• importable Perspective pages
• Perspective performance review
• Gateway Perspective page builder
• Jython 2.7.3 script creator
• expression language creator
• SQL query builder
• HMI/SCADA style guide tester using ISA-101
• historian forensic helper
• alarm pipeline orchestrator
• AI log assistant

The main point is this: don’t just dump docs into a prompt and hope the agent gets smarter.

Give it context, give it tools, make it test, make it save evidence, and only let proven patterns become part of the skill.

If you’re trying to set something like this up, feel free to reach out. I don’t mind helping people get their first skill/gateway loop working.

I also posted a YouTube video walking through the process. Search “Building Perspective Pages in Ignition 8.1 with AI Agents” and it should come up.