メニュー
Build the TML compiler from C++ sources. Use when the user says "build", "compila", "rebuild", or needs to recompile the compiler after C++ changes.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | build-compiler |
| description | Build the TML compiler from C++ sources. Use when the user says "build", "compila", "rebuild", or needs to recompile the compiler after C++ changes. |
| user-invocable | true |
| argument-hint | optional release, clean, all, mcp |
Delegation: Use the Agent tool to dispatch a build-engineer agent with model: haiku for this task.
Based on $ARGUMENTS:
Preferred: Use mcp__tml__project_build MCP tool with:
mode: "debug" or "release"clean: true if clean build requestedtarget: "compiler" (default, safe), "all", or "mcp"tests: false to skip test executable for faster buildsIMPORTANT: Default target is "compiler" (tml.exe only). This is intentional — building "all" or "mcp" kills the running MCP server connection.
Fallback (if MCP tool unavailable): Use the canonical Bash command:
cd /f/Node/hivellm/tml && cmd //c "scripts\\build.bat --no-tests" 2>&1
Add flags as needed:
release for release mode--clean for clean build--no-tests to skip test executable (default for quick builds)After build completes, report success/failure and the output path.
Detect and fix documentation violations across C++ compiler and TML library code. Scans for missing ///, undocumented public items, wrong comment styles, and auto-fixes using parallel agents. Use when the user says "fix docs", "audit docs", "documenta", "corrige docs", or wants to improve documentation coverage.
Deep knowledge of TML compiler internals. Inject before working on compiler C++ code. Maps the full pipeline with key functions, types, and cross-subsystem boundaries.
Deep knowledge of TML standard library structure, module dependencies, key types, and C runtime mapping. Inject before working on library code.
Detect which tests are affected by recent code changes. Use when the user wants to know what tests to run after making changes.
List build artifacts with sizes and ages. Use when the user asks about build outputs, compiled binaries, or disk usage.
Detect what changed and build only the necessary target. Use when the user says "build smart", "build inteligente", or wants an optimized build.