balatrobot 0.6.0__tar.gz

balatrobot-0.6.0/.claude/commands/commit-msg.md

@@ -0,0 +1,43 @@
+Generate a conventional commit message for the current staged changes.
+
+Analyze the git diff of staged files and create a commit message following conventional commits specification:
+
+**Format:** `<type>(<scope>): <description>`
+
+**Types:**
+
+- feat: new feature
+- fix: bug fix
+- docs: documentation
+- style: formatting, missing semicolons, etc.
+- refactor: code change that neither fixes a bug nor adds a feature
+- test: adding or correcting tests
+- chore: maintenance tasks
+- ci: continuous integration changes
+- revert: reverts a previous commit
+
+**Scopes:**
+
+- api: Lua API and Python API communication
+- log: Logging and Replay functionality
+- bot: Python bot framework and base classes
+- examples: Example bots and usage samples
+- dev: Development tools and environment
+
+**Workflow:**
+
+1. Run `git status` to see overall repository state. If there are are no staged changes, exit.
+2. Run `git diff --staged` to analyze the actual changes
+3. Run `git diff --stat --staged` for summary of changed files
+4. Run `git log --oneline -10` to review recent commit patterns
+5. Choose appropriate type and scope based on changes
+6. Write concise description (50 chars max for first line)
+7. Include body if changes are complex
+8. Return the generated commit message enclosed in triple backticks
+
+**Notes**
+
+- Do not include emojis in the commit message.
+- Do not include `🤖 Generated with [Claude Code](https://claude.ai/code)` in the commit message.
+- If the list is empty, do not add any co-authors
+- Include in the body of the commit message the following line as last line: `# Co-Authored-By: Claude <noreply@anthropic.com>`

balatrobot-0.6.0/.claude/commands/commit.md

@@ -0,0 +1,53 @@
+Generate a conventional commit message for the current staged changes.
+
+Analyze the git diff of staged files and create a commit message following conventional commits specification:
+
+**Format:** `<type>(<scope>): <description>`
+
+**Types:**
+
+- feat: new feature
+- fix: bug fix
+- docs: documentation
+- style: formatting, missing semicolons, etc.
+- refactor: code change that neither fixes a bug nor adds a feature
+- test: adding or correcting tests
+- chore: maintenance tasks
+- ci: continuous integration changes
+- revert: reverts a previous commit
+
+**Scopes:**
+
+- api: Lua API and Python API communication
+- log: Logging and Replay functionality
+- bot: Python bot framework and base classes
+- examples: Example bots and usage samples
+- dev: Development tools and environment
+
+**Workflow:**
+
+1. Run `git status` to see overall repository state. If there are are no staged changes, exit.
+2. Run `git diff --staged` to analyze the actual changes
+3. Run `git diff --stat --staged` for summary of changed files
+4. Run `git log --oneline -10` to review recent commit patterns
+5. Choose appropriate type and scope based on changes
+6. Write concise description (50 chars max for first line)
+7. Include body if changes are complex
+8. Commit the staged changes with the generated message
+
+**Co-authors**
+Here is the collection of all previous co-authors of the repo as reference (names and emails):
+
+- claude: `Co-Authored-By: Claude <noreply@anthropic.com>`
+
+Here is a list of the co-authors which contributed to this commit:
+
+```
+$ARGUMENTS
+```
+
+**Notes**
+
+- Do not include emojis in the commit message.
+- Do not include `🤖 Generated with [Claude Code](https://claude.ai/code)` in the commit message.
+- If the list is empty, do not add any co-authors

balatrobot-0.6.0/.claude/commands/test.md

@@ -0,0 +1,3 @@
+Run tests following the testing guidelines in CLAUDE.md.
+
+See the Testing section in CLAUDE.md for complete instructions on prerequisites, workflow, and troubleshooting.

balatrobot-0.6.0/.claude/settings.json

@@ -0,0 +1,36 @@
+{
+  "permissions": {
+    "allow": [
+      "Bash(pytest:*)",
+      "Bash(ruff check:*)",
+      "Bash(ruff format:*)",
+      "Bash(basedpyright:*)"
+    ],
+    "deny": [
+      "Edit(CHANGELOG.md)",
+      "MultiEdit(CHANGELOG.md)",
+      "Write(CHANGELOG.md)"
+    ]
+  },
+  "hooks": {
+    "PostToolUse": [
+      {
+        "matcher": "Write|Edit|MultiEdit",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "stylua src/lua"
+          },
+          {
+            "type": "command",
+            "command": "ruff check --select I --fix . && ruff format -s ."
+          },
+          {
+            "type": "command",
+            "command": "mdformat ."
+          }
+        ]
+      }
+    ]
+  }
+}

balatrobot-0.6.0/.cursor/rules/docs-formatting.mdc

@@ -0,0 +1,51 @@
+---
+globs: docs/**/*.md
+alwaysApply: false
+description: Documentation formatting guidelines for files in the docs directory
+---
+
+# Documentation Formatting Guidelines
+
+When writing documentation files in the docs directory:
+
+## Header Structure
+
+- Use minimal header nesting - prefer level 1 (`#`) and level 2 (`##`) headers
+- Level 3 headers (`###`) are allowed when they significantly improve readability and document structure
+- **Method names, function signatures, and similar structured content** should use level 3 headers (`###`) for better navigation and clarity
+- For other sub-sections that would normally be level 3 or deeper, consider using **bold text** or other formatting instead
+- Preserve logical hierarchy and importance in your header structure
+
+## Spacing Requirements
+
+- Always leave a blank line after any title/header
+- Always leave a blank line before any list (bulleted or numbered)
+- This ensures proper visual separation and readability
+
+## Examples
+
+Good formatting:
+```markdown
+# Main Title
+
+Content here...
+
+## Section Title
+
+More content...
+
+### Method Name or Structured Content
+
+Detailed information...
+
+- List item 1
+- List item 2
+```
+
+Avoid:
+```markdown
+# Main Title
+Content immediately after title...
+#### Excessive nesting
+- List without spacing above
+```