imaginate-mcp AGENTS.md

AGENTS.md

Important Rules

1. Ask, don't assume. If something is unclear, ask before writing a single line. Never make silent assumptions about intent, architecture, or requirements.
2. Simplest solution first. Always implement the simplest thing that could work. Do not add abstractions or flexibility that weren't explicitly requested.
3. Don't touch unrelated code. If a file or function is not directly part of the current task, do not modify it, even if you think it could be improved.
4. Flag uncertainty explicitly. If you are not confident about an approach or technical detail, say so before proceeding. Confidence without certainty causes more damage than admitting a gap.
5. Do NOT change files unless you fully understand the project structure and intent.
6. Use a friendly tone and sound engaged with the project.
7. Always update the CHANGELOG.md and OVERVIEW.md after completing a task. Maintain all other documentation as needed or as instructed. Check the system date/time if necessary before updating CHANGELOG.md.
8. Use all available agents, skills, MCP, and any other tools/knowledge documents you have access to autonomously as needed. Never assume. If the information or tools required to get the information are available, use them.
9. Use web search and/or Context7 tools for up-to-date framework/API documentation. DO NOT ever assume you have all of the information needed if you are unfamiliar with the required packages or the using latest, new versions.
10. Always produce modern, elegant, and stylized solutions — avoid outdated or basic implementations.
11. No mocks, placeholders, stubs, or temporary implementations remain.
12. No files allowed above 500 lines, always run checks after making new files, keep things modular when you edit or create. Refactor when needed, ensure exact same form and function, you are simply making things modular. The 500 line limit does not apply to documentation files.
13. Write real, useful tests when the change warrants them. Do not run tests after every tiny fix, wording tweak, style adjustment, or small feature addition. Run only the smallest relevant test set needed to validate substantial code changes, risky logic changes, regressions, or larger features. Do not run the full test suite unless the scope of the change genuinely justifies it.
14. Use your "Chrome" plugin or browser verification only after substantial UI work, large scaffolds, major feature additions, broad layout changes, or a very large task list where end-to-end verification is useful. Do not launch Playwright, Chrome, or browser checks after every small fix, edit, style tweak, or minor feature. When browser verification is warranted, ensure you are connecting to the correct host:port and check the relevant desktop, mobile, theme, accessibility, keyboard, tap, touch, and mouse behavior as appropriate. If the server is not running, start it, verify the work, then shut it down.
15. Always remember this project is used on mobile heavily. We need to always ensure we design in a mobile friendly way, proper UX, add standard accesability, tooltips, we should always be able to fully control things from tap, touch, mouse, keyboard.
16. Always create an Apache 2.0 LICENSE if no license file exists.