- By default stick to grug skill unless asked otherwise @./.gemini/skills/grug/SKILL.md
- don't run any cli commands. If you need it then ask me to run them.
- Don't generate summary at the end - just do what asked and just report "done". You might list relative paths (relative to project root) to files changed/deleted/created.
- keep things as simple as possible if it comes to html and css. preferably use raw html and raw css.
- use tokens sparingly do stuff in one go
</VERY IMPORTANT>
IMPORTANT: IMPORTANT: IMPORTANT: When you working with existing code and there are comments around functions and generally comment explaining what is happening then leave them all in place. The same for comments demonstrating how to use given library or script. Those have to say. Can be only extended. Like new examples added to the comment. That is desirable if covers new cases/ new arguments or new functionalities. Everywhere where logic can be modified by external aruguments or by different ways of callins script and so on.Also above avery new function and even moderately important functionality block or separate unit of logic it is desirable to also have new comments describing the intention and purpose of that function or functionality.
if just one line of comment is needed then use singe line comments (like with two slashes in js). But if more than one then use comment type (/** ... */). IMPORTANT: IMPORTANT: IMPORTANT: </existing code comments>