You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Generate a Token Model Protocol (TMP) JSON schema for the CLI tool "{{ tool }}".
2
+
3
+
A TMP schema defines the subcommand structure, parameters (flags and arguments), primitive token types, descriptions, and dynamic resolvers for a CLI tool.
4
+
5
+
Please design a comprehensive and detailed schema file for "{{ tool }}", mapping its most common subcommands, options, and parameters.
6
+
7
+
## Schema Specification and Format
8
+
The output MUST be a valid JSON object matching the following structure:
9
+
{
10
+
"meta": {
11
+
"tool": "{{ tool }}",
12
+
"description": "Short description of what the tool does."
13
+
},
14
+
"commands": [
15
+
{
16
+
"command": "{{ tool }} <subcommand>",
17
+
"description": "Short description of the subcommand.",
"resolver": "git:branches" | "git:status_files" | "cargo:packages" | "npm:scripts" | etc.
29
+
}
30
+
}
31
+
]
32
+
}
33
+
]
34
+
}
35
+
36
+
## Guidelines
37
+
1. The JSON must be valid and ready to be saved to `.waz/schemas/{{ tool }}.json`.
38
+
2. Do not wrap the JSON in markdown code blocks or add conversational commentary; output ONLY the raw, clean JSON content.
39
+
3. Make sure to define the correct `token_type` for each parameter. Use "Boolean" for flags that take no values (like --force or -f), "Enum" for parameters with specific values, "File" for paths/files, and "String" for generic text.
0 commit comments