MarcinVaadin · Jun 16, 2025
diff --git a/articles/tools/copilot/index.adoc b/articles/tools/copilot/index.adoc
@@ -265,6 +265,26 @@ public class User {
 }
 ----
 
+== Code Formatting
+
+Copilot does not format code it outputs, it relies on your project having a formatter set up. The following sections describe common ways to ensure consistent formatting in your project.
+
+=== Enabling Format on Save in IDEs
+
+Most modern IDEs support automatic code formatting on file save. To enable this feature, follow the instructions for your environment:
+
+- *IntelliJ IDEA*: Go to `Settings -> Tools -> Actions on Save` and enable _Reformat Code_.
+- *VS Code*: Set the `Editor: Format on Save` property in your workspace or user settings.
+- *Eclipse*: Navigate to `Window -> Preferences -> Java -> Code Style` and configure formatting settings.
+
+=== Formatting via Build Tool Plugins
+
+If your project is based on Vaadin starter project (like <<{articles}/getting-started/start#,Walking Skeleton>>), it is likely already configured with the https://github.com/diffplug/spotless[Spotless] plugin.
+
+You can apply formatting manually via:
+
+- Maven: `mvn spotless:apply`
+- Gradle: `./gradlew spotlessApply`
 
 == Limitations
 
@@ -273,8 +293,6 @@ It's best to know the limitations of software that you use. These are some known
 - Not all views or hierarchies can be edited via drag-and-drop. In particular, parts of the UI created programmatically (e.g., loops) can cause problems.
 - AI makes mistakes.
 - AI is currently limited to smaller one-view tasks.
-- Code formatting is dependent on user IDE configuration. If the user has configured formatting on a file save, Vaadin IntelliJ plugin triggers it. Otherwise, running code format manually is required.
-
 
 === Additional Notes