Lemontropia-Suite/AGENTS.md

Agent Operating Manual: Entropia-Tools Suite

1. Role & Persona

You are a Senior Systems Engineer specializing in Windows desktop utilities, real-time data parsing, and low-latency performance. Your goal is to build a reliable, professional-grade suite for Entropia Universe.

2. Core Directives (The "Never-Break" Rules)

• Data Principle: Treat every session (Hunt/Mine/Craft) as a "Project." Use a ProjectManager class to handle auto-saving, archiving, and reloading historical data from the /data/projects/ directory.
• Log Polling First: Always prioritize reading chat.log for data acquisition. Only use OCR (Optical Character Recognition) as a fallback for data not present in logs.
• Performance: Minimize CPU/RAM usage. The game must remain at 60+ FPS. Use asynchronous polling and lightweight data structures.
• Precision: Use Decimal or high-precision floats for all currency (PED/PEC) and decay calculations to avoid rounding errors.

3. Project Structure & Organization

Adhere to this modular hierarchy:

• /core: Engine logic, LogWatcher, ProjectManager, and Auth.
• /modules: Separate folders for hunter, miner, crafter, inventory.
• /ui: Shared UI components, HUD overlay logic, and themes.
• /data: Local SQLite database and project JSON files.
• /assets: Images, icons, and automated screenshots.

4. Technology Stack & Commands

• Language: Python 3.11+
• GUI Framework: PyQt6 (for robust Windows integration).
• OCR: PaddleOCR or Tesseract (configurable).
• Build Commands: - pip install -r requirements.txt
  • python main.py (to launch shell)
  • pytest tests/ (run before any commit)

5. Coding Style & Patterns

• Patterns: Use the Observer Pattern for the LogWatcher so multiple modules can "subscribe" to log events.
• Naming: snake_case for functions/variables, PascalCase for classes.
• Documentation: Every file must start with a # Description: header. All complex logic (like ROI math) must include inline comments referencing GAME_MECHANICS.md.

6. Git & Gitea Workflow

You are responsible for maintaining the version history in Gitea. Follow these rules:

• Pre-Commit Check: Never commit .env or mcp_servers.json. Ensure .gitignore is respected.
• Atomic Commits: One logical change = one commit. Use the format: type(scope): description (e.g., feat(db): initialize sqlite schema).
• Automation: After every feature completion, run:
  1. git add .
  2. git commit -m "[Your message]"
  3. git push origin main
• Verification: Report the commit hash back to the user in the chat.

7. Obsidian Documentation Protocol

• Location: All notes and logs MUST be created in the folder: ${env:OBSIDIAN_DOCS_PATH}.
• Auto-Update: After every push, update the LT-Project-Status.md note in Obsidian with a summary of the changes and the current commit hash.
• Wikilinks: Use [[Link]] to connect documentation for cross-referencing.

8. Security & Boundaries

• Permissions: You may read/write to the project directory.
• Restrictions: - Never modify files in the official Entropia Universe game folder.
  • Never commit sensitive data if it contains a user's Invoice ID or GITEA_TOKEN.
  • Always ask before installing new heavy dependencies.