@brookmind/ai-toolkit 1.0.5 → 1.1.1

package/mcps/pg-aiguide/README.md

@@ -1,275 +0,0 @@
-# pg-aiguide
-
-**AI-optimized PostgreSQL expertise for coding assistants**
-
-pg-aiguide helps AI coding tools write dramatically better PostgreSQL code. It provides:
-
-- **Semantic search** across the official PostgreSQL manual (version-aware)
-- **AI-optimized “skills”** — curated, opinionated Postgres best practices used automatically by AI agents
-- **Extension ecosystem docs**, starting with TimescaleDB, with more coming soon
-
-Use it either as:
-
-- a **public MCP server** that can be used with any AI coding agent, or
-- a **Claude Code plugin** optimized for use with Claude's native skill support.
-
-## ⭐ Why pg-aiguide?
-
-AI coding tools often generate Postgres code that is:
-
-- outdated
-- missing constraints and indexes
-- unaware of modern PG features
-- inconsistent with real-world best practices
-
-pg-aiguide fixes that by giving AI agents deep, versioned PostgreSQL knowledge and proven patterns.
-
-### See the difference
-
-https://github.com/user-attachments/assets/5a426381-09b5-4635-9050-f55422253a3d
-
-<details>
-<summary>Video Transcript </summary>
-
-Prompt given to Claude Code:
-
-> Please describe the schema you would create for an e-commerce website two times, first with the tiger mcp server disabled, then with the tiger mcp server enabled. For each time, write the schema to its own file in the current working directory. Then compare the two files and let me know which approach generated the better schema, using both qualitative and quantitative reasons. For this example, only use standard Postgres.
-
-Result (summarized):
-
-- **4× more constraints**
-- **55% more indexes** (including partial/expression indexes)
-- **PG17-recommended patterns**
-- **Modern features** (`GENERATED ALWAYS AS IDENTITY`, `NULLS NOT DISTINCT`)
-- **Cleaner naming & documentation**
-
-Conclusion: _pg-aiguide produces more robust, performant, maintainable schemas._
-
-</details>
-
-## 🚀 Quickstart
-
-pg-aiguide is available as a **public MCP server**:
-
-[https://mcp.tigerdata.com/docs](https://mcp.tigerdata.com/docs)
-
-<details> 
-<summary>Manual MCP configuration using JSON</summary>
-
-```json
-{
-  "mcpServers": {
-    "pg-aiguide": {
-      "url": "https://mcp.tigerdata.com/docs"
-    }
-  }
-}
-```
-
-</details>
-
-Or it can be used as a **Claude Code Plugin**:
-
-```bash
-claude plugin marketplace add timescale/pg-aiguide
-claude plugin install pg@aiguide
-```
-
-### Install by environment
-
-#### One-click installs
-
-[![Install in Cursor](https://img.shields.io/badge/Install_in-Cursor-000000?style=flat-square&logoColor=white)](https://cursor.com/en/install-mcp?name=pg-aiguide&config=eyJuYW1lIjoicGctYWlndWlkZSIsInR5cGUiOiJodHRwIiwidXJsIjoiaHR0cHM6Ly9tY3AudGlnZXJkYXRhLmNvbS9kb2NzIn0=)
-[![Install in VS Code](https://img.shields.io/badge/Install_in-VS_Code-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://vscode.dev/redirect/mcp/install?name=pg-aiguide&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.tigerdata.com%2Fdocs%22%7D)
-[![Install in VS Code Insiders](https://img.shields.io/badge/Install_in-VS_Code_Insiders-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://insiders.vscode.dev/redirect/mcp/install?name=pg-aiguide&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.tigerdata.com%2Fdocs%22%7D&quality=insiders)
-[![Install in Visual Studio](https://img.shields.io/badge/Install_in-Visual_Studio-C16FDE?style=flat-square&logo=visualstudio&logoColor=white)](https://vs-open.link/mcp-install?%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.tigerdata.com%2Fdocs%22%7D)
-[![Install in Goose](https://block.github.io/goose/img/extension-install-dark.svg)](https://block.github.io/goose/extension?cmd=&arg=&id=pg-aiguide&name=pg-aiguide&description=MCP%20Server%20for%20pg-aiguide)
-[![Add MCP Server pg-aiguide to LM Studio](https://files.lmstudio.ai/deeplink/mcp-install-light.svg)](https://lmstudio.ai/install-mcp?name=pg-aiguide&config=eyJuYW1lIjoicGctYWlndWlkZSIsInR5cGUiOiJodHRwIiwidXJsIjoiaHR0cHM6Ly9tY3AudGlnZXJkYXRhLmNvbS9kb2NzIn0=)
-
-<details>
-<summary>Claude Code</summary>
-
-This repo serves as a claude code marketplace plugin. To install, run:
-
-```bash
-claude plugin marketplace add timescale/pg-aiguide
-claude plugin install pg@aiguide
-```
-
-This plugin uses the skills available in the `skills` directory as well as our
-publicly available MCP server endpoint hosted by TigerData for searching PostgreSQL documentation.
-
-</details>
-
-<details>
-<summary> Codex </summary>
-
-Run the following to add the MCP server to codex:
-
-```bash
-codex mcp add --url "https://mcp.tigerdata.com/docs" pg-aiguide
-```
-
-</details>
-
-<details>
-<summary> Cursor </summary>
-
-One-click install:
-
-[![Install MCP Server](https://cursor.com/deeplink/mcp-install-dark.svg)](https://cursor.com/en-US/install-mcp?name=pg-aiguide&config=eyJ1cmwiOiJodHRwczovL21jcC50aWdlcmRhdGEuY29tL2RvY3MifQ%3D%3D)
-
-Or add the following to `.cursor/mcp.json`
-
-```json
-{
-  "mcpServers": {
-    "pg-aiguide": {
-      "url": "https://mcp.tigerdata.com/docs"
-    }
-  }
-}
-```
-
-</details>
-
-<details>
-<summary> Gemini CLI </summary>
-
-Run the following to add the MCP server to Gemini CLI:
-
-```bash
-gemini mcp add -s user pg-aiguide "https://mcp.tigerdata.com/docs" -t http
-```
-
-</details>
-
-<details>
-<summary> Visual Studio </summary>
-
-Click the button to install:
-
-[![Install in Visual Studio](https://img.shields.io/badge/Install_in-Visual_Studio-C16FDE?style=flat-square&logo=visualstudio&logoColor=white)](https://vs-open.link/mcp-install?%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.tigerdata.com%2Fdocs%22%7D)
-
-</details>
-
-<details>
-<summary> VS Code </summary>
-
-Click the button to install:
-
-[![Install in VS Code](https://img.shields.io/badge/Install_in-VS_Code-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://vscode.dev/redirect/mcp/install?name=pg-aiguide&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.tigerdata.com%2Fdocs%22%7D)
-
-Alternatively, run the following to add the MCP server to VS Code:
-
-```bash
-code --add-mcp '{"name":"pg-aiguide","type":"http","url":"https://mcp.tigerdata.com/docs"}'
-```
-
-</details>
-
-<details>
-<summary> VS Code Insiders </summary>
-
-Click the button to install:
-
-[![Install in VS Code Insiders](https://img.shields.io/badge/Install_in-VS_Code_Insiders-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://insiders.vscode.dev/redirect/mcp/install?name=pg-aiguide&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.tigerdata.com%2Fdocs%22%7D&quality=insiders)
-
-Alternatively, run the following to add the MCP server to VS Code Insiders:
-
-```bash
-code-insiders --add-mcp '{"name":"pg-aiguide","type":"http","url":"https://mcp.tigerdata.com/docs"}'
-```
-
-</details>
-
-<details>
-<summary> Windsurf </summary>
-
-Add the following to `~/.codeium/windsurf/mcp_config.json`
-
-```json
-{
-  "mcpServers": {
-    "pg-aiguide": {
-      "serverUrl": "https://mcp.tigerdata.com/docs"
-    }
-  }
-}
-```
-
-</details>
-
-### 💡 Your First Prompt
-
-Once installed, pg-aiguide can answer Postgres questions or design schemas.
-
-**Simple schema example prompt**
-
-> Create a Postgres table schema for storing usernames and unique email addresses.
-
-**Complex schema example prompt**
-
-> You are a senior software engineer. You are given a task to generate a Postgres schema for an IoT device company.
-> The devices collect environmental data on a factory floor. The data includes temperature, humidity, pressure, as
-> the main data points as well as other measurements that vary from device to device. Each device has a unique id
-> and a human-readable name. We want to record the time the data was collected as well. Analysis for recent data
-> includes finding outliers and anomalies based on measurements, as well as analyzing the data of particular devices for ad-hoc analysis. Historical data analysis includes analyzing the history of data for one device or getting statistics for all devices over long periods of time.
-
-## Features
-
-### Semantic Search (MCP Tools)
-
-- [**`semantic_search_postgres_docs`**](API.md#semantic_search_postgres_docs)  
-  Performs semantic search over the official PostgreSQL manual, with results scoped to a specific Postgres version.
-
-- [**`semantic_search_tiger_docs`** ](API.md#semantic_search_tiger_docs)
-  Searches Tiger Data’s documentation corpus, including TimescaleDB and future ecosystem extensions.
-
-### Skills (AI-Optimized Best Practices)
-
-- **[`view_skill`](API.md#view_skill)**  
-  Exposes curated, opinionated PostgreSQL best-practice skills used automatically by AI coding assistants.
-
-  These skills provide guidance on:
-  - Schema design
-  - Indexing strategies
-  - Data types
-  - Data integrity and constraints
-  - Naming conventions
-  - Performance tuning
-  - Modern PostgreSQL features
-
-## 🔌 Ecosystem Documentation
-
-Supported today:
-
-- **TimescaleDB** (docs + skills)
-
-Coming soon:
-
-- **pgvector**
-- **PostGIS**
-
-We welcome contributions for additional extensions and tools.
-
-## 🛠 Development
-
-See [DEVELOPMENT.md](DEVELOPMENT.md) for:
-
-- running the MCP server locally
-- adding new skills
-- adding new docs
-
-## 🤝 Contributing
-
-We welcome:
-
-- new Postgres best-practice skills
-- additional documentation corpora
-- search quality improvements
-- bug reports and feature ideas
-
-## 📄 License
-
-Apache 2.0

package/mcps/pg-aiguide/skills/design-postgres-tables

@@ -1 +0,0 @@
-404: Not Found

package/mcps/pg-aiguide/skills/find-hypertable-candidates

@@ -1 +0,0 @@
-404: Not Found

package/mcps/pg-aiguide/skills/migrate-postgres-tables-to-hypertables

@@ -1 +0,0 @@
-404: Not Found

package/mcps/pg-aiguide/skills/setup-timescaledb-hypertables

@@ -1 +0,0 @@
-404: Not Found

package/mcps/pg-aiguide/skills.yaml

@@ -1,4 +0,0 @@
----
-local: 
-  type: local_collection
-  path: ./skills

package/skills/cloudflare-cli/SKILL.md

@@ -1,151 +0,0 @@
----
-name: cloudflare-cli
-description: This skill should be used when the user wants to interact with Cloudflare services including Workers, R2 buckets, KV namespaces, D1 databases, DNS, or any Cloudflare-related operations. Use the wrangler CLI instead of MCP tools.
----
-
-# Cloudflare CLI Skill
-
-This skill provides instructions for using the `wrangler` CLI to interact with Cloudflare, replacing the need for Cloudflare MCP servers.
-
-## Prerequisites
-
-Wrangler is already authenticated. Verify with:
-
-```bash
-npx wrangler whoami
-```
-
-Account: **DC** (fd6d187f67d843db47f1949aa701ee52)
-
-## R2 (Object Storage)
-
-```bash
-# List buckets
-npx wrangler r2 bucket list
-
-# Create bucket
-npx wrangler r2 bucket create <bucket-name>
-
-# Delete bucket
-npx wrangler r2 bucket delete <bucket-name>
-
-# List objects in bucket
-npx wrangler r2 object list <bucket-name>
-
-# Upload object
-npx wrangler r2 object put <bucket-name>/<key> --file=<path>
-
-# Download object
-npx wrangler r2 object get <bucket-name>/<key> --file=<path>
-
-# Delete object
-npx wrangler r2 object delete <bucket-name>/<key>
-```
-
-## KV (Key-Value Store)
-
-```bash
-# List namespaces
-npx wrangler kv namespace list
-
-# Create namespace
-npx wrangler kv namespace create <name>
-
-# Delete namespace
-npx wrangler kv namespace delete --namespace-id=<id>
-
-# List keys
-npx wrangler kv key list --namespace-id=<id>
-
-# Get value
-npx wrangler kv key get <key> --namespace-id=<id>
-
-# Put value
-npx wrangler kv key put <key> <value> --namespace-id=<id>
-
-# Delete key
-npx wrangler kv key delete <key> --namespace-id=<id>
-```
-
-## D1 (SQL Database)
-
-```bash
-# List databases
-npx wrangler d1 list
-
-# Create database
-npx wrangler d1 create <name>
-
-# Execute SQL query
-npx wrangler d1 execute <database-name> --command="SELECT * FROM table"
-
-# Execute SQL file
-npx wrangler d1 execute <database-name> --file=./schema.sql
-
-# Export database
-npx wrangler d1 export <database-name> --output=backup.sql
-```
-
-## Workers
-
-```bash
-# List workers
-npx wrangler deployments list
-
-# View worker details
-npx wrangler deployments status
-
-# Deploy worker
-npx wrangler deploy
-
-# Tail logs (real-time)
-npx wrangler tail <worker-name>
-
-# View worker code
-npx wrangler deployments view
-```
-
-## DNS & Zones
-
-```bash
-# List zones
-npx wrangler dns zones list
-
-# List DNS records
-npx wrangler dns records list <zone-id>
-
-# Create DNS record
-npx wrangler dns records create <zone-id> --type=A --name=sub --content=1.2.3.4
-```
-
-## Pages
-
-```bash
-# List projects
-npx wrangler pages project list
-
-# Deploy
-npx wrangler pages deploy <directory> --project-name=<name>
-
-# List deployments
-npx wrangler pages deployment list --project-name=<name>
-```
-
-## Secrets
-
-```bash
-# List secrets
-npx wrangler secret list
-
-# Add secret
-npx wrangler secret put <name>
-
-# Delete secret
-npx wrangler secret delete <name>
-```
-
-## Tips
-
-- Use `--json` flag for JSON output when available
-- Use `--help` on any command for detailed options
-- Most commands work with local `wrangler.toml` for project context

package/skills/docx/LICENSE.txt

@@ -1,30 +0,0 @@
-© 2025 Anthropic, PBC. All rights reserved.
-
-LICENSE: Use of these materials (including all code, prompts, assets, files,
-and other components of this Skill) is governed by your agreement with
-Anthropic regarding use of Anthropic's services. If no separate agreement
-exists, use is governed by Anthropic's Consumer Terms of Service or
-Commercial Terms of Service, as applicable:
-https://www.anthropic.com/legal/consumer-terms
-https://www.anthropic.com/legal/commercial-terms
-Your applicable agreement is referred to as the "Agreement." "Services" are
-as defined in the Agreement.
-
-ADDITIONAL RESTRICTIONS: Notwithstanding anything in the Agreement to the
-contrary, users may not:
-
-- Extract these materials from the Services or retain copies of these
-  materials outside the Services
-- Reproduce or copy these materials, except for temporary copies created
-  automatically during authorized use of the Services
-- Create derivative works based on these materials
-- Distribute, sublicense, or transfer these materials to any third party
-- Make, offer to sell, sell, or import any inventions embodied in these
-  materials
-- Reverse engineer, decompile, or disassemble these materials
-
-The receipt, viewing, or possession of these materials does not convey or
-imply any license or right beyond those expressly granted above.
-
-Anthropic retains all right, title, and interest in these materials,
-including all copyrights, patents, and other intellectual property rights.

package/skills/docx/SKILL.md

@@ -1,197 +0,0 @@
----
-name: docx
-description: "Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks"
-license: Proprietary. LICENSE.txt has complete terms
----
-
-# DOCX creation, editing, and analysis
-
-## Overview
-
-A user may ask you to create, edit, or analyze the contents of a .docx file. A .docx file is essentially a ZIP archive containing XML files and other resources that you can read or edit. You have different tools and workflows available for different tasks.
-
-## Workflow Decision Tree
-
-### Reading/Analyzing Content
-Use "Text extraction" or "Raw XML access" sections below
-
-### Creating New Document
-Use "Creating a new Word document" workflow
-
-### Editing Existing Document
-- **Your own document + simple changes**
-  Use "Basic OOXML editing" workflow
-
-- **Someone else's document**
-  Use **"Redlining workflow"** (recommended default)
-
-- **Legal, academic, business, or government docs**
-  Use **"Redlining workflow"** (required)
-
-## Reading and analyzing content
-
-### Text extraction
-If you just need to read the text contents of a document, you should convert the document to markdown using pandoc. Pandoc provides excellent support for preserving document structure and can show tracked changes:
-
-```bash
-# Convert document to markdown with tracked changes
-pandoc --track-changes=all path-to-file.docx -o output.md
-# Options: --track-changes=accept/reject/all
-```
-
-### Raw XML access
-You need raw XML access for: comments, complex formatting, document structure, embedded media, and metadata. For any of these features, you'll need to unpack a document and read its raw XML contents.
-
-#### Unpacking a file
-`python ooxml/scripts/unpack.py <office_file> <output_directory>`
-
-#### Key file structures
-* `word/document.xml` - Main document contents
-* `word/comments.xml` - Comments referenced in document.xml
-* `word/media/` - Embedded images and media files
-* Tracked changes use `<w:ins>` (insertions) and `<w:del>` (deletions) tags
-
-## Creating a new Word document
-
-When creating a new Word document from scratch, use **docx-js**, which allows you to create Word documents using JavaScript/TypeScript.
-
-### Workflow
-1. **MANDATORY - READ ENTIRE FILE**: Read [`docx-js.md`](docx-js.md) (~500 lines) completely from start to finish. **NEVER set any range limits when reading this file.** Read the full file content for detailed syntax, critical formatting rules, and best practices before proceeding with document creation.
-2. Create a JavaScript/TypeScript file using Document, Paragraph, TextRun components (You can assume all dependencies are installed, but if not, refer to the dependencies section below)
-3. Export as .docx using Packer.toBuffer()
-
-## Editing an existing Word document
-
-When editing an existing Word document, use the **Document library** (a Python library for OOXML manipulation). The library automatically handles infrastructure setup and provides methods for document manipulation. For complex scenarios, you can access the underlying DOM directly through the library.
-
-### Workflow
-1. **MANDATORY - READ ENTIRE FILE**: Read [`ooxml.md`](ooxml.md) (~600 lines) completely from start to finish. **NEVER set any range limits when reading this file.** Read the full file content for the Document library API and XML patterns for directly editing document files.
-2. Unpack the document: `python ooxml/scripts/unpack.py <office_file> <output_directory>`
-3. Create and run a Python script using the Document library (see "Document Library" section in ooxml.md)
-4. Pack the final document: `python ooxml/scripts/pack.py <input_directory> <office_file>`
-
-The Document library provides both high-level methods for common operations and direct DOM access for complex scenarios.
-
-## Redlining workflow for document review
-
-This workflow allows you to plan comprehensive tracked changes using markdown before implementing them in OOXML. **CRITICAL**: For complete tracked changes, you must implement ALL changes systematically.
-
-**Batching Strategy**: Group related changes into batches of 3-10 changes. This makes debugging manageable while maintaining efficiency. Test each batch before moving to the next.
-
-**Principle: Minimal, Precise Edits**
-When implementing tracked changes, only mark text that actually changes. Repeating unchanged text makes edits harder to review and appears unprofessional. Break replacements into: [unchanged text] + [deletion] + [insertion] + [unchanged text]. Preserve the original run's RSID for unchanged text by extracting the `<w:r>` element from the original and reusing it.
-
-Example - Changing "30 days" to "60 days" in a sentence:
-```python
-# BAD - Replaces entire sentence
-'<w:del><w:r><w:delText>The term is 30 days.</w:delText></w:r></w:del><w:ins><w:r><w:t>The term is 60 days.</w:t></w:r></w:ins>'
-
-# GOOD - Only marks what changed, preserves original <w:r> for unchanged text
-'<w:r w:rsidR="00AB12CD"><w:t>The term is </w:t></w:r><w:del><w:r><w:delText>30</w:delText></w:r></w:del><w:ins><w:r><w:t>60</w:t></w:r></w:ins><w:r w:rsidR="00AB12CD"><w:t> days.</w:t></w:r>'
-```
-
-### Tracked changes workflow
-
-1. **Get markdown representation**: Convert document to markdown with tracked changes preserved:
-   ```bash
-   pandoc --track-changes=all path-to-file.docx -o current.md
-   ```
-
-2. **Identify and group changes**: Review the document and identify ALL changes needed, organizing them into logical batches:
-
-   **Location methods** (for finding changes in XML):
-   - Section/heading numbers (e.g., "Section 3.2", "Article IV")
-   - Paragraph identifiers if numbered
-   - Grep patterns with unique surrounding text
-   - Document structure (e.g., "first paragraph", "signature block")
-   - **DO NOT use markdown line numbers** - they don't map to XML structure
-
-   **Batch organization** (group 3-10 related changes per batch):
-   - By section: "Batch 1: Section 2 amendments", "Batch 2: Section 5 updates"
-   - By type: "Batch 1: Date corrections", "Batch 2: Party name changes"
-   - By complexity: Start with simple text replacements, then tackle complex structural changes
-   - Sequential: "Batch 1: Pages 1-3", "Batch 2: Pages 4-6"
-
-3. **Read documentation and unpack**:
-   - **MANDATORY - READ ENTIRE FILE**: Read [`ooxml.md`](ooxml.md) (~600 lines) completely from start to finish. **NEVER set any range limits when reading this file.** Pay special attention to the "Document Library" and "Tracked Change Patterns" sections.
-   - **Unpack the document**: `python ooxml/scripts/unpack.py <file.docx> <dir>`
-   - **Note the suggested RSID**: The unpack script will suggest an RSID to use for your tracked changes. Copy this RSID for use in step 4b.
-
-4. **Implement changes in batches**: Group changes logically (by section, by type, or by proximity) and implement them together in a single script. This approach:
-   - Makes debugging easier (smaller batch = easier to isolate errors)
-   - Allows incremental progress
-   - Maintains efficiency (batch size of 3-10 changes works well)
-
-   **Suggested batch groupings:**
-   - By document section (e.g., "Section 3 changes", "Definitions", "Termination clause")
-   - By change type (e.g., "Date changes", "Party name updates", "Legal term replacements")
-   - By proximity (e.g., "Changes on pages 1-3", "Changes in first half of document")
-
-   For each batch of related changes:
-
-   **a. Map text to XML**: Grep for text in `word/document.xml` to verify how text is split across `<w:r>` elements.
-
-   **b. Create and run script**: Use `get_node` to find nodes, implement changes, then `doc.save()`. See **"Document Library"** section in ooxml.md for patterns.
-
-   **Note**: Always grep `word/document.xml` immediately before writing a script to get current line numbers and verify text content. Line numbers change after each script run.
-
-5. **Pack the document**: After all batches are complete, convert the unpacked directory back to .docx:
-   ```bash
-   python ooxml/scripts/pack.py unpacked reviewed-document.docx
-   ```
-
-6. **Final verification**: Do a comprehensive check of the complete document:
-   - Convert final document to markdown:
-     ```bash
-     pandoc --track-changes=all reviewed-document.docx -o verification.md
-     ```
-   - Verify ALL changes were applied correctly:
-     ```bash
-     grep "original phrase" verification.md  # Should NOT find it
-     grep "replacement phrase" verification.md  # Should find it
-     ```
-   - Check that no unintended changes were introduced
-
-
-## Converting Documents to Images
-
-To visually analyze Word documents, convert them to images using a two-step process:
-
-1. **Convert DOCX to PDF**:
-   ```bash
-   soffice --headless --convert-to pdf document.docx
-   ```
-
-2. **Convert PDF pages to JPEG images**:
-   ```bash
-   pdftoppm -jpeg -r 150 document.pdf page
-   ```
-   This creates files like `page-1.jpg`, `page-2.jpg`, etc.
-
-Options:
-- `-r 150`: Sets resolution to 150 DPI (adjust for quality/size balance)
-- `-jpeg`: Output JPEG format (use `-png` for PNG if preferred)
-- `-f N`: First page to convert (e.g., `-f 2` starts from page 2)
-- `-l N`: Last page to convert (e.g., `-l 5` stops at page 5)
-- `page`: Prefix for output files
-
-Example for specific range:
-```bash
-pdftoppm -jpeg -r 150 -f 2 -l 5 document.pdf page  # Converts only pages 2-5
-```
-
-## Code Style Guidelines
-**IMPORTANT**: When generating code for DOCX operations:
-- Write concise code
-- Avoid verbose variable names and redundant operations
-- Avoid unnecessary print statements
-
-## Dependencies
-
-Required dependencies (install if not available):
-
-- **pandoc**: `sudo apt-get install pandoc` (for text extraction)
-- **docx**: `npm install -g docx` (for creating new documents)
-- **LibreOffice**: `sudo apt-get install libreoffice` (for PDF conversion)
-- **Poppler**: `sudo apt-get install poppler-utils` (for pdftoppm to convert PDF to images)
-- **defusedxml**: `pip install defusedxml` (for secure XML parsing)