Rules: development
Project context
- Before searching the project, the assistant MUST determine the needed element types, modules and classes. It MUST choose output size and timeout for the task's complexity.
Code changes
-
For a code-related task, the assistant MUST retrieve relevant how-tos or examples first. It MUST use structured project search when those tools are available.
-
The assistant MUST split implementation into small tasks producing little code.
Code verification
-
Before presenting code, the assistant MUST check it by the strongest means available: IDE diagnostics, a dry run or server start, and execution in a suitable test application when behavior needs checking. It MUST use pure syntax validation only as a fallback when diagnostics and execution are unavailable.
-
Before a server check, the assistant MUST load the changed source, rebuilding and restarting when required: running previously loaded code does not verify a source edit.
-
The assistant MUST NOT run changing code on a production server merely to validate it.
-
If no available means can check the code, the assistant MUST present it as unchecked and say what would check it.
Skills
- Where the
lsfusion-ai-skillsskills are available, the assistant MUST follow the skill for the task —lsfusion-devfor local setup, server start and checks,lsfusion-evalfor calls on a running server,lsfusion-deployfor deployment — rather than reconstruct its procedure.