iaud-report-structure

Identify and summarize i-AUD report structures including .aud.json and .mtsd files.

3|1|Updated Jun 12, 2025
One-click install
npx skills add https://github.com/AUD-DEV-TEAM/i-AUD-Developer-Kit --skill iaud-report-structure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: iaud-report-structure
Source: https://github.com/AUD-DEV-TEAM/i-AUD-Developer-Kit/tree/main/.claude/skills/iaud-report-structure
Command: npx skills add https://github.com/AUD-DEV-TEAM/i-AUD-Developer-Kit --skill iaud-report-structure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide clarifies the i-AUD report/program structure and file layout, helping new developers understand how reports are organized and how components relate.

Core Features & Use Cases

  • Provides a clear map of i-AUD project skeleton, including .aud.json, .mtsd, DataSource, ServerScript, and client script locations.
  • Useful for onboarding, documentation generation, and impact analysis when modifying reports or deploying updates.
  • Use case: a developer reviewing an existing i-AUD project to identify where the data sources are defined and how server scripts connect to client scripts.

Quick Start

Identify the folder and file layout of an i-AUD report, including .aud.json, .mtsd, DataSource, and ServerScript structures.

Frequently Asked Questions about iaud-report-structure

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

FAQPage Schema
What is the file structure of an i-AUD report project?

An i-AUD report project structure is organized around core files like .aud.json and .mtsd, alongside specific directories for DataSource, ServerScript, and client scripts to define program layout and component relationships.

How do I locate data sources and server scripts in an i-AUD project?

You can locate i-AUD data sources and server scripts by reviewing the project folder layout, which maps core files like .aud.json and .mtsd to identify where DataSource and ServerScript components are defined and connected.

Can I generate documentation for an existing i-AUD report layout?

Yes, you can generate documentation for an i-AUD report layout by summarizing the module relationships, file metadata, and core file locations like .aud.json and .mtsd to enable accurate discovery and reuse.

Does the i-AUD structure guide help with impact analysis before modifying reports?

Yes, the i-AUD structure guide supports impact analysis by clarifying how server scripts connect to client scripts and data sources, helping you document module relationships before deploying report updates.

Do I need prior knowledge of .aud.json and .mtsd files to understand the i-AUD project structure?

No prior knowledge of .aud.json or .mtsd files is needed, as the guide provides a clear map of the i-AUD project skeleton designed for quick onboarding of new developers and data analysts.