langflow-mcp AGENTS.md

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

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.

---

Structural and Design Recommendations

• Use POM (Page Object Model) or layered architecture to separate UI, logic, and data.
• Maintain clear naming conventions for variables, functions, and classes.
• Avoid magic numbers and hardcoded values – use constants or enums.
• Keep functions small and focused – each should perform one logical action.
• Don't comment bad code – rewrite it.
• Write once, read many – optimize for readability and long-term maintenance.
• Prefer explicitness over implicitness – avoid hidden behavior or side effects.
• Consistent formatting and indentation – follow language style guides.
• Meaningful structure – organize code into logical, reusable modules.