4D Project Info

Analyze a 4D project and produce a JSON summary of its structure.

Usage

python3 scripts/project_info.py [path] [--format json|human|terse] [--compact]

• path: Any path inside a 4D project, the project root itself, the Project/ directory, or a direct path to the .4DProject file. Defaults to current directory.
• --format: json for structured output, human for a readable text summary, terse for a token-light text summary. Aliases: text, token, tokens, toon.
• --compact: For json output, return only names and counts instead of full per-file details.

If no project root can be resolved, the script still exits with an error, but it also returns a list of nearby .4DProject files to use explicitly on the next run.

Output

JSON compact mode

{
  "project_root": "/path/to/project",
  "settings": { "project_file": "MyProject.4DProject", "compatibility_version": 2100 },
  "summary": {
    "methods_count": 12,
    "classes_count": 5,
    "forms_count": 3,
    "database_methods": ["onStartup"],
    "has_catalog": true,
    "total_code_lines": 1847,
    "dependencies": { "file_exists": true, "dependencies": { "SemVer": { "github": "mesopelagique/SemVer" } } }
  },
  "method_names": ["test_Feature", "utils_helper"],
  "class_names": ["Employee", "DataStore"],
  "form_names": ["MainForm", "Dialog_Settings"]
}

Human mode

Returns a short readable summary with project settings, counts, and comma-separated names.

Terse mode

Returns the same key facts in a token-light text format.

JSON full mode

Adds per-method line counts and per-class details (properties, functions, extends).

When to Use

• Before any refactoring or migration task
• When the user asks "what's in this project?"
• To provide project context to other skills (e.g., 4d-migrate-syntax, 4d-generate-doc)
• When onboarding onto an unfamiliar 4D codebase