Fix llms_description for all docs

Author: roxblnfk

CLAUDE.md

@@ -112,12 +112,15 @@ llms_description: "Technical description of what LLM learns from this page"
 ```
 
 - `llms` — controls inclusion. Default is `true` (can be omitted). `"optional"` for secondary content, `false` to exclude
-- `llms_description` — short, technical description for LLM context. Lists key entities and concepts, not marketing text. Required for all included pages
-
-**Guidelines for `llms_description`:**
-- List specific classes, attributes, methods — not vague descriptions
-- Example: `"#[BeforeTest], #[AfterTest], #[BeforeClass], #[AfterClass] lifecycle hooks, execution order, priority"`
-- NOT: `"Learn about test lifecycle management"`
+- `llms_description` — brief, informative note helping an LLM understand what the page covers. Required for all included pages
+
+**Guidelines for `llms_description` (per [llmstxt.org](https://llmstxt.org) spec):**
+- Start with the page's purpose ("How to ...", "Parameterized tests with ..."), then mention key entities in context
+- Use concise, clear natural language — not a raw comma-separated list of class names
+- Include specific classes/attributes/methods, but woven into a readable sentence
+- Example: `"How to run code before/after tests. #[BeforeTest], #[AfterTest], #[BeforeClass], #[AfterClass] lifecycle hooks, execution order, priority, class instantiation behavior"`
+- NOT: `"Learn about test lifecycle management"` (too vague, no entities)
+- NOT: `"BeforeTest, AfterTest, BeforeClass, AfterClass, priority"` (raw list, no context)
 
 **When adding new doc pages:** add `llms_description` to the English version frontmatter. Do NOT add llms frontmatter to blog posts.
 

docs/events.md

@@ -1,5 +1,5 @@
 ---
-llms_description: "PSR-14 event system: TestSuite/TestCase/Test event hierarchy, lifecycle event ordering, polymorphic listeners, custom dispatchers"
+llms_description: "How to react to test lifecycle with events. PSR-14 event system with TestSuite/TestCase/Test hierarchy, event ordering rules, polymorphic listeners for catching multiple event types, custom event dispatchers."
 ---
 
 # Events

docs/getting-started.md

@@ -1,6 +1,6 @@
 ---
 faqLevel: 2
-llms_description: "Installation via Composer, testo.php configuration, writing first test class, running tests, IDE plugin setup"
+llms_description: "Getting started with Testo. Installation via Composer, testo.php configuration file, writing your first test class with #[Test], running tests from CLI, PhpStorm plugin setup."
 ---
 
 # Getting Started

docs/plugins.md

@@ -2,7 +2,7 @@
 faqLevel: 2
 outline: [2, 3]
 llms: true
-llms_description: "PluginConfigurator interface, creating plugins with interceptors and event listeners, FallbackInterceptor for attribute-based extensions"
+llms_description: "How to extend Testo with plugins. PluginConfigurator interface with three extension points: interceptors (InterceptorCollector), event listeners (EventListenerCollector, PSR-14), and container bindings (bind/set/make/get). Container scopes per Test Suite. Full examples: failure logger plugin, GitHub PR flaky reporter. Plugins without configurator via FallbackInterceptor."
 ---
 
 # Plugins

docs/plugins/convention.md

@@ -1,6 +1,6 @@
 ---
 llms: "optional"
-llms_description: "Convention-based test discovery: *Test class suffix, test* method/function prefix"
+llms_description: "Convention-based test discovery without attributes. NamingConventionPlugin with configurable *Test class suffix, test* method prefix, and allowPrivate option."
 ---
 
 # Naming Conventions

docs/writing-tests.md

@@ -1,6 +1,6 @@
 ---
 outline: [2, 3]
-llms_description: "Test approaches: separate tests in classes/functions (#[Test], conventions), inline tests (#[TestInline]), benchmarks (#[Bench]), folder structure, suite configuration"
+llms_description: "How to write tests in Testo. Three approaches: separate tests in classes/functions (#[Test] attribute, naming conventions), inline tests (#[TestInline]) on the method itself, and benchmarks (#[Bench]). Folder structure and suite configuration."
 ---
 
 # Writing Tests