Loading...
Loading...
You are a Gemini agent working on the ExoMonad codebase. Follow these rules strictly.
# ExoMonad — Gemini Agent Rules You are a Gemini agent working on the ExoMonad codebase. Follow these rules strictly. ## Critical: Non-Interactive Commands You are running headless. Any command that launches a TUI, pager, or interactive prompt will hang forever. ```bash # git: ALWAYS disable pager git --no-pager log git --no-pager diff # NEVER run these without --no-pager — they will hang: # git log, git diff ``` ## Git Hygiene - **Always `git add` specific files by name.** Never use `git add .` or `git add -A`. - **Never commit files under `target/` or build artifact directories.** - Check `git status` before committing to verify you're only staging what you changed. ## Haskell WASM - **LANGUAGE pragmas**: The closing delimiter is `#-}` not `#}`. Triple-check after editing .hs files. - **No trailing whitespace** on lines you edit. - **Build with**: `just wasm-all` (inside nix develop shell) ## Rust - **Build with**: `cargo check --workspace` or `cargo test --workspace` (inside nix develop shell) - **No new dependencies** unless explicitly told to add them. ## Architecture Read `CLAUDE.md` for full architecture docs. Key points: - All MCP tool logic lives in Haskell WASM (`haskell/wasm-guest/src/ExoMonad/Guest/Tools/`) - Rust is the I/O runtime — it executes effects, never defines tool schemas - Proto files define the FFI boundary between Haskell and Rust
You are a **senior Rust systems engineer** specializing in **high-performance, low-resource web platforms**.
This document provides a comprehensive guide for Gemini, the AI assistant, to effectively contribute to the AGP (Análisis General de Postaciones) project. It synthesizes all project-specific rules, architectural patterns, and development guidelines.
This document outlines the strict, non-negotiable rules and development protocol for the AI agent responsible for writing the source code of the **ProFiT** framework. The agent's primary directive is to produce code that is robust, maintainable, testable, and perfectly aligned with the technical specification. Adherence to this protocol is mandatory for every code generation task.
FIM One is an AI-powered **Connector Hub** that serves as a bridge between disjointed enterprise systems (ERP, CRM, OA, Databases) through autonomous AI agents.