Modify a KUI project with an agent

Provide the project

Start from the settings project. Provide the SDK version, build command and source files, and use the compiler standard and runtime required by the selected SDK package. The interface uses HTML/CSS and native events; browser JavaScript dependencies are not assumed.

• Download the settings project →

Example task brief

This task changes a layout and one state field, with input, error and restore acceptance actions. Adapt it to your own business fields by updating the model and acceptance steps.

Project: Forge KUI settings-lab, Windows x64, C++.
Use the installed SDK version reported by CMake.
Add a workspace description field to HTML and SettingsState.
Read live input values with HTMLInputElement::value().
Keep the UI usable at 1000px and 640px window widths.
Build with CMake and run CTest.
Run the app: save, reject invalid data, restore unsaved edits.
Capture the resulting window. Report actual results and remaining issues.

Reference material

Check properties and values in the capability reference and APIs in SDK headers. Treat live values, default attributes, event threading and element lifetimes separately. Compile, run and inspect generated code; first-pass output does not replace acceptance.

• Form values and events →
• Capability reference →
• Debugging lesson →

Delivery checks

Report commands actually run, exit codes and window interaction results. A static screenshot is not an input test. A CSS declaration does not prove all combinations are supported.

• The project configures and builds from a new build directory.
• Success, validation failure and restore are operable.
• Resizing does not obscure text or leave controls unreachable.
• Screenshots come from the running target; unverified items include a reason.

Practice and acceptance

Use these actions to check completion; there is no need to copy the same code into another project.

• Change one interaction, such as explicit success feedback on save.
• Ask the agent to read current sources and APIs and report edits and build results.
• Verify valid/invalid input, restoring and narrow layout, then report findings.