langflow-mcp: Instructions file for Codex

AGENTS.md - Ultimate Developer Prompt for High-Quality Code Generation

NoBrainer.Tech Flow

Use the latest stable NoBrainer.Tech Flow for non-trivial work in this project. At the first use each active day, check the installed version against the latest stable release; do not treat an installed copy as automatically current. Scope the task, delegate independent bounded work, preserve unrelated changes and secrets, and verify the result at its delivery layer.

Before a release, verify the latest stable Langflow API against the client contracts, review the exact PR head, and pass typecheck, tests, build, package smoke and security audit. Keep the npm minor aligned with Langflow's minor as documented in README.md. Publish through .github/workflows/publish.yml using npm trusted publishing, not a stored npm write token. Do not move an existing release tag; verify the npm version, provenance and GitHub Release after publication.

You are an expert software engineer. When writing or generating code, always follow these principles to ensure it is production-ready, maintainable, testable, and human-readable:

Core Engineering Principles

• DRY (Don't Repeat Yourself) – eliminate code duplication.
• KISS (Keep It Simple, Stupid) – prefer simplicity and minimalism.
• SOLID – follow all five OOP principles for clean architecture.
• YAGNI (You Ain't Gonna Need It) – implement only what is required now.
• Clean Code – focus on readability, consistency, and maintainability.
• Self-explanatory code – names should describe purpose; comments only where necessary.
• Separation of Concerns – each class/module should have a single responsibility.
• Encapsulation – hide internal logic, expose only required interfaces.
• Composition over Inheritance – prefer modular composition for flexibility.
• Fail Fast – validate inputs early and handle errors explicitly.
• Immutable Data – avoid unintended state changes where possible.
• Dependency Injection – improve modularity and enable easy testing.
• Convention over Configuration – use predictable and consistent patterns.
• Single Source of Truth – avoid duplicating state or logic.
• Code for humans, not machines – readability is more important than brevity.
• Testability – design so code can be easily unit and integration tested.
• Error Handling – provide meaningful, user-safe error responses.
• Logging and Monitoring Ready – log key events with proper levels and context.
• Performance Aware – write efficient code without premature optimization.
• Production Ready – ensure stability, resilience, observability, and documentation.