skills.rest
IntentArchitect
IntentArchitectOFFICIAL
Explore all skills by this author →
WebsiteGitHub

module-debugging

Insert temporary log statements into designer scripts and module C# code to inspect runtime values.

23|10|Updated Aug 31, 2017
Search Tags:#debugging#troubleshooting#logging#software factory#intent architect#designer script#csharp templates
One-click install
npx skills add https://github.com/IntentArchitect/Intent.Modules --skill module-debugging-intentarchitect
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: module-debugging
Source: https://github.com/IntentArchitect/Intent.Modules/tree/main/Tests/ModuleBuilderSkills/.opencode/skills/module-debugging
Command: npx skills add https://github.com/IntentArchitect/Intent.Modules --skill module-debugging-intentarchitect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a designer script or generated template in an Intent Architect module behaves unexpectedly, there is no interactive debugger available, making it impossible to see actual runtime values without a dedicated diagnostic approach. ## Core Features & Use Cases - Designer Script Logging: Add temporary console.log, console.warn, or console.error calls inside run_designer_script code and read the captured output returned in the result. - Module C# Logging: Write runtime values from templates, factory extensions, and registrations to Intent Architect's log file using the Logging.Log API with Debug, Info, Warning, or Failure levels. - Log File Discovery: Locate the day-rolling, per-process log files under the OS temp directory in logs/software-factory or logs/module-tasks, then grep for a distinctive prefix like [AI-DEBUG] to isolate your output. - Use Case: A template generates wrong attribute counts for a model. Add a prefixed Logging.Log.Debug line, rerun the Software Factory, find the newest log file, grep for the prefix, confirm the actual value, then remove the temporary statement. ## Quick Start Add a temporary [AI-DEBUG] log statement to my module template, run the Software Factory, and show me the matching lines from the newest Intent Architect log file.

Frequently Asked Questions about module-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a designer script in Intent Architect?▼

Add console.log, console.warn, or console.error calls inside the script. The run_designer_script tool captures these calls and returns them in the result output, which is the only visibility into a script's runtime values.

How do I log runtime values from module C# templates?▼

Use Logging.Log from Intent.Utils with Debug, Info, Warning, or Failure levels to write values to Intent Architect's log file. There is no interactive debugger since module code runs inside the Software Factory process.

Where are Intent Architect Software Factory log files located?▼

Log files live under the OS temp directory at IntentArchitect/logs/software-factory/sf-{contextId}-{pid}-{date}.log. They are day-rolling and per-process, so list the folder and pick the most recently modified file rather than guessing a name.

What logging levels does the Intent Architect Logging.Log API support?▼

Only Debug, Info, Warning, and Failure exist on the ITracing interface. There is no Error, Trace, or Fatal level and no structured templated overloads, so build the full message string yourself before passing it in.

Why can't I find my debug output in the Intent Architect log?▼

The log file also contains Intent Architect's internal lines, making blind searches slow. Prefix your statements with a distinctive marker like [AI-DEBUG] and grep the newest log file for that exact prefix.

Should temporary debug log statements stay in shipped module code?▼

No. Temporary console.log and Logging.Log statements are for diagnosis only and must be removed once the runtime value is confirmed. They are not intended as permanent logging in released module code.

Related Skills

Explore More Software Engineering Skills→
Rune-kitRune-kit
82

debug

Trace errors through code and stack traces to identify root causes.

Official
Advanced
FRIKKernFRIKKern
6

doey-reset

Reset Doey to factory defaults by regenerating templates and reinstalling agents.

Community
Intermediate
shin0720shin0720

auto-canary

Automate pre-deployment verification including builds, E2E tests, and browser checks.

Community
Intermediate
sergio-bershadskysergio-bershadsky
15

frappe-test

Generate pytest-compatible unit and integration tests for Frappe Framework v15 DocTypes and APIs.

Community
Advanced