docs: add better documentation for strategies

Author: S1M0N38

CLAUDE.md

@@ -183,6 +183,7 @@ src/balatrollm/
 └── strategies/                    # Strategy-based templates
     ├── default/                   # Conservative strategy
     └── aggressive/                # High-risk strategy
+        ├── manifest.json          # Strategy metadata
         ├── STRATEGY.md.jinja      # Strategy guide
         ├── GAMESTATE.md.jinja     # Game state representation
         ├── MEMORY.md.jinja        # Response history
@@ -230,9 +231,26 @@ The `--strategy` flag accepts built-in strategy names:
 - **Default** (`--strategy default`): Conservative, financially disciplined approach
 - **Aggressive** (`--strategy aggressive`): High-risk, high-reward approach with aggressive spending
 
-Each strategy directory must contain:
+Each strategy directory must contain **5 required files**:
 
+- `manifest.json`: Strategy metadata (name, description, author, version, tags)
 - `STRATEGY.md.jinja`: Strategy-specific guide
 - `GAMESTATE.md.jinja`: Game state representation
 - `MEMORY.md.jinja`: Response history tracking
 - `TOOLS.json`: Strategy-specific function definitions
+
+**manifest.json Structure**:
+
+```json
+{
+  "name": "Default",
+  "description": "Conservative, financially disciplined approach to Balatro",
+  "author": "BalatroBench",
+  "version": "0.1.0",
+  "tags": ["conservative", "financial"]
+}
+```
+
+All 5 fields are required. Strategy versions are independent from BalatroLLM versions.
+
+For comprehensive strategy documentation including Jinja2 templates, validation, and contribution guidelines, see [docs/strategies.md](https://s1m0n38.github.io/balatrollm/strategies/).

CONTRIBUTING.md

@@ -16,7 +16,7 @@ This document provides guidelines and instructions for contributing to the proje
 
 5. **Use Conventional Commits**: Follow the conventional commits specification for your commit messages.
 
-6. **Submit Strategies**: Community members can contribute new playing strategies by following the strategy submission guidelines below.
+6. **Submit Strategies**: Community members can contribute new playing strategies. See the [Strategies documentation](https://s1m0n38.github.io/balatrollm/strategies/) for detailed guidelines.
 
 ## Environment Setup
 
@@ -49,89 +49,3 @@ source .envrc
 ```
 
 > You can use [direnv](https://github.com/direnv/direnv) to automatically activate the environment when you enter the project directory.
-
-## Contributing Strategies
-
-Community members can contribute new playing strategies to enhance BalatroLLM's gameplay variety. Strategies define how the bot approaches decision-making during different game phases.
-
-### Strategy Structure
-
-Each strategy must be organized as a directory under `src/balatrollm/strategies/` containing exactly four files:
-
-```
-src/balatrollm/strategies/your_strategy_name/
-├── STRATEGY.md.jinja      # Strategy-specific guide and approach
-├── GAMESTATE.md.jinja     # Game state representation template
-├── MEMORY.md.jinja        # Response history tracking template
-└── TOOLS.json             # Strategy-specific function definitions
-```
-
-### Strategy Naming Requirements
-
-Strategy names must follow these rules:
-
-- **Lowercase letters and numbers only** (e.g., `aggressive`, `value_based`, `risky2`)
-- **Valid Python identifier** (cannot start with a number)
-- **Underscores allowed, hyphens forbidden** (e.g., `high_risk` allowed, `high-risk` forbidden)
-- **No spaces or special characters**
-
-### Creating Your Strategy
-
-1. **Study Existing Strategies**: Review `src/balatrollm/strategies/default/` and `src/balatrollm/strategies/aggressive/` to understand the template structure and content expectations.
-
-2. **Create Strategy Directory**: Create a new directory following the naming requirements:
-
-   ```bash
-   mkdir src/balatrollm/strategies/your_strategy_name
-   ```
-
-3. **Required Files**: Create all four required files using the existing strategies as templates:
-
-   - **STRATEGY.md.jinja**: Define your strategy's core philosophy, decision-making approach, and gameplay priorities
-   - **GAMESTATE.md.jinja**: Template for how game state information should be presented to the LLM
-   - **MEMORY.md.jinja**: Template for tracking and presenting response history
-   - **TOOLS.json**: Function definitions available to the LLM during gameplay
-
-4. **Template Compatibility**: Ensure your templates work with the Jinja2 templating system and provide all necessary context for LLM decision-making.
-
-### Submission Process
-
-1. **Fork the Repository**: Fork the BalatroLLM repository to your GitHub account
-
-2. **Create Feature Branch**: Create a new branch for your strategy:
-
-   ```bash
-   git checkout -b feat/add-strategy-your_strategy_name
-   ```
-
-3. **Implement Strategy**: Add your strategy directory with all required files
-
-4. **Test Your Strategy**: Run your strategy locally to ensure it works:
-
-   ```bash
-   balatrollm --strategy your_strategy_name
-   ```
-
-5. **Submit Pull Request**: Open a PR containing only your new strategy directory. The PR should:
-
-   - Have a clear title: `feat: add [strategy_name] strategy`
-   - Include a brief description of your strategy's approach and philosophy
-   - Follow conventional commit standards
-
-### Quality Standards
-
-- **Complete Implementation**: All four files must be present and functional
-- **Clear Documentation**: Strategy philosophy and approach should be well-documented
-- **Template Validation**: Ensure Jinja2 templates render correctly with game data
-- **Unique Approach**: Strategy should offer a meaningfully different gameplay style from existing strategies
-
-### Review Process
-
-Submitted strategies will be reviewed for:
-
-- Compliance with naming and structure requirements
-- Template functionality and Jinja2 compatibility
-- Strategy uniqueness and gameplay value
-- Code quality and documentation standards
-
-Once approved, your strategy will be available to all BalatroLLM users via the `--strategy` flag.

docs/index.md

@@ -1,8 +1,18 @@
 # BalatroLLM
 
-<!-- <figure markdown="span"> -->
+<!-- TODO: This should be uncommented when the balatrollm repo is public -->
 
-<!--   <figcaption>A Balatro bot powered by LLM</figcaption> -->
+<!-- <figure> -->
+
+<!--   <figcaption>BalatroLLM playing Balatro</figcaption> -->
+
+<!--   <video controls playsinline> -->
+
+<!--     <source src="https://github.com/user-attachments/assets/777d0c4f-d66a-47dd-9eab-7efb20beaaf2" type="video/mp4"> -->
+
+<!--     Your browser does not support the video tag. -->
+
+<!--   </video> -->
 
 <!-- </figure> -->
 
@@ -36,12 +46,16 @@ BalatroLLM is a bot that uses Large Language Models (LLMs) to play [Balatro](htt
 
     [:octicons-arrow-right-24: Analysis](analysis.md)
 
-- :octicons-sparkle-fill-16:{ .lg .middle } __Docs for LLM__
+- :material-strategy:{ .lg .middle } __Strategies__
 
     ---
 
-    Documentation in [llms.txt](https://llmstxt.org/) format. Just paste the following link (or its content) into the LLM chat.
+    Learn how strategies work, their structure using Jinja2 templates, and how to contribute your own.
 
-    [:octicons-arrow-right-24: llms-full.txt](llms-full.txt)
+    [:octicons-arrow-right-24: Strategies](strategies.md)
 
 </div>
+
+!!! tip "Docs for LLM"
+
+    Documentation in [llms.txt](https://llmstxt.org/) format. Just paste [this link](llms-full.txt) (or its content) into the LLM chat.