hazo_notify 1.0.0

package/.cursor/rules/design.mdc

@@ -0,0 +1,16 @@
+---
+alwaysApply: true
+---
+
+[Behaviour]
+- for any alerts, error, information messages where the user should acknowledge, don't use the standard javascript alert. Instead use the shadcn alert dialog component with just the ok button.  For messages where the user does not need to acknowledge, use a shadcn sonnen instead.
+- for any notifications or updates where the user should be notified but not necessarily need to acknowledge, use the shadcn sonner component
+
+[Edit_Field_Behaviour]
+- For a given single field that is to be editable, have a lucide icon pencil next to the field , then when in editing mode, show a green lucide circle-check for the save/submit button, and a red lucide circle-x for the cancel button.
+
+
+[Style]
+- include seo friendly alt text for all images and components and buttons
+- when any pages are loading,  then show a shadcn spinner
+- in dialog boxes, action buttons, etc, always have the positive action on the left and negative action on the right. For example, the "save" button should be on the left and "cancel" button on the right.

package/.cursor/rules/general.mdc

@@ -0,0 +1,49 @@
+---
+description: General rules always to be used
+globs: *
+alwaysApply: true
+---
+
+[General]
+- Start all chats wtih 🐸
+- Only implement if you're 90% sure of requirement or the fix.  Otherwise ask questions or things for me to check.
+- Continuously update the detailed technical design of the application in a file called techdoc.md in the root directory.  In this file include a section for Overall (general technical details including file architecture, key files), a section for each major component, API routes and their use, example code, constraints. This is an internal document to help with maintainability.
+
+
+[Style]
+- Always use snake_case
+- Include a description of purpose of file at top of each new file
+- Include comments at the top of each function or major section of code
+- Add comments for each file and also major section
+- Add a class name identifier for div tags prefixed with "cls_" so that they can be easily identified and searched.  Reused divs should have the same name.
+
+[UI_Behaviour]
+- All data input fields (not interaction fields), it should be non-editable but there is a lucide pencil icon next to it.  When pressed, it'll allow to edit the inptu field, and a lucide circle-check-big will be used for the "Submit"/"save"/"update" button, and a lucide circle-x will be used for the cancel button.
+
+
+[Technology]
+- use the following tech stack:
+  - React
+  - Next.js
+  - TailwindCSS
+  - TypeScript
+  - Shadcn/UI
+- use npm shadcn@latest add * to add components. Do not use shadcn-ui
+
+[Architecture]
+- store all configuration values in hazo_notify_config.ini file.  Always put hard coded values that have chance to change in config.ini
+- store any sensitive data in .env file (to be excluded in git)
+- create reusable components to prevent having redundant code and to improve maintainability
+- Ensure you have a minimum of one file per route
+- Group pages into directories for maintainability
+
+[Database]
+- database schema can be gound on .cursor/rules/db_schema.md
+
+[Logging]
+- use main app logging service for backend logging  
+-  When there's an error that happens, always log on the serverside.
+- Use the config.
+- In the logging, always include the filename, line number, message and relevant data to help troubleshoot in future in the json log entry
+- When error messages are shown to the user, they should always be logged verbatem in the serverside log file as well 
+- don't import the logger in the client side code