Simplified home screen

.github/prompts/compile.prompt.md

@@ -3,5 +3,5 @@ mode: agent
 ---
 
 - Update the app to follow [the specification](../../main.md)
-- Build the code with the VS Code tasks. Avoid asking me to run `go build` or `go test` commands manually.
+- Build and run the code with `scripts/run`. Avoid asking me to run `go build` or `go test` commands manually.
 - Fetch the GitHub home page for each used library to get a documentation and examples. Avoid the weird go code inspections you like to do.

.github/skills/testing/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: testing
-description: Guide for testing TUI (terminal user interface) applications. Use this when asked to verify code changes.
+description: Guide for testing and verifying code changes in this TUI application. Use this skill after making ANY code changes to main.go or main.md to verify they work correctly.
 ---
 
 # Testing
@@ -9,17 +9,20 @@ This skill helps you create and run tests for terminal user interface (TUI) appl
 
 ## When to use this skill
 
-Use this skill when you need to:
-- Verify that code changes work as intended
-- Ensure existing functionality as specified in `maind.md` and `README.md` is not broken
+Use this skill:
+
+- **After making ANY code changes** to verify they work correctly
+- When modifying UI elements, menus, or display logic
+- When changing application behavior or adding features
+- To ensure existing functionality as specified in `main.md` and `README.md` is not broken
 
 ## Starting the application
 
 - Run `scripts/run` where the user would normally run `github-brain`
   - `scripts/run pull` equivalently runs `github-brain pull`
-  - `scripts/run mcp` equivalently runs `github-brain mcp` 
+  - `scripts/run mcp` equivalently runs `github-brain mcp`
 - Ensure `.env` files is configured to use the `github-brain-test` organization
 - Use GitHub MCP to add new issue/PRs/discussions as needed for testing
 - Simulate user input: Send key presses, control combinations, or specific commands to the running application.
--  Capture and analyze screen output: The testing tool captures the terminal display (or buffer) at specific moments in time.
+- Capture and analyze screen output: The testing tool captures the terminal display (or buffer) at specific moments in time.
 - Make assertions: Verify that the screen content matches the expected output (e.g., checking if specific text is present at certain coordinates or if the cursor position is correct).