Project Rules

Project-Rules.md

0. Short and Simple:

After each response:

1. Create and update changelog.md with all changes made on that time and date.

2. Create and update suggestions.md. Include 15 suggestions... 5 for frontend and 5 for backend and 5 for everything else. Always append top list. Do not delete.

3. Create and update components.md to list all the components used, where they are used, and if they are flyonui, shadcn, or whatever. The format should be in markdown table format with several columns to detail each entry.

NOTE: In cases where we are implementing this after we have created a lot of the pages, you will have to go over the code to determine what's already been implemented.

4. Create and update todo.md to list all tasks in a structured markdown format and check-mark all tasks completed.

5. Check for errors and fix all errors before finishing your response.

6. Always provide a bulleted summary that outlines your plans to complete this project, including every step that you will take with both a reasoning and a description for each step from this point forward.

7. Suggest the next steps to take from our todo.md and ask user to proceed. Break them down into sub-tasks if needed.

1. Project workflow & documentation rules

• Cumulative changelog (changelog.md)

  • Every meaningful change or decision gets a time-stamped entry appended (never overwritten).
  • Entries should be concise but clear: what changed, why, and any implications.
  • Changelog also captures “lessons learned” or feedback after major milestones.

• Suggestions log (suggestions.md)

  • Suggestions are continually appended and kept in structured sections:
    • Frontend suggestions
    • Backend suggestions
    • Trending/other ideas
  • Entries are never deleted; only new ones are added.
  • Each response should append 15 new suggestions: 5 frontend, 5 backend, 5 “other/trending”.

• Components inventory (components.md)

  • Maintain a Markdown table listing:
    • Component name
    • Usage location
    • Source/library (e.g., flyonui, shadcn, custom)
    • Brief description
  • When code already exists, I should inspect it to identify implemented components and document them.

• Todo checklist (todo.md)

  • All tasks are listed in a Markdown checklist.
  • Completed tasks are marked as checked ([x]), incomplete tasks as unchecked ([ ]).
  • The todo list is kept comprehensive and updated to reflect current status.

• Error checking & robustness

  • Error checking is “baked into every session”: I must check for inconsistencies or mistakes before finishing.
  • Parsing, sync, and DOM logic must be validated and logged via a dedicated error logging mechanism.

2. Current project state

3. Immediate next steps you defined

4. Global “post-response protocol” rules

After each response, I should:

1. Top 5 Logical Next Steps

   • Outline five clear, actionable, sequential steps for immediate implementation and development. Label them as Optional, Recommended, Required, or Critical.

2. Top 5 Frontend Implementation Suggestions (if applicable)

   • Provide five detailed UX/UI/interaction-focused suggestions relevant to the current work. Label them as Optional, Recommended, Required, or Critical.

3. Top 5 Backend Implementation Suggestions (if applicable)

   • Provide five detailed suggestions focusing on parsing, state, performance, data handling, etc. Label them as Optional, Recommended, Required, or Critical.

4. Top 5 Trending Suggestions

   • Provide five suggestions integrating current trends (UX, AI, analytics, community, etc.). Label them as Optional, Recommended, Required, or Critical.

5. Error Check

   • Perform an internal error/consistency check and call out/offer to fix anything suspicious.

6. Changelog Update

   • Create or update changelog.md with time-stamped entries describing what changed in this “session/step”.

7. Suggestions Update

   • Create or update suggestions.md, appending 15 new suggestions (5 frontend, 5 backend, 5 trending/other) while retaining previous entries. Label them as Optional, Recommended, Required, or Critical.

8. Components Update

   • Create or update components.md with a Markdown table listing all identified/proposed components and their usage/source. Label them as Optional, Recommended, Required, or Critical.
   • If code exists, inspect it to find what has already been implemented.

9. Todo Update

   • Create or update todo.md to reflect all remaining tasks and mark completed tasks as checked. Label them as Optional, Recommended, Required, or Critical.

10. Project Summary

• Provide a concise, bulleted summary of the overall plan to complete the project, with reasoning for each step.

11. Next Steps Prompt

• Based on todo.md, suggest immediate next steps (with sub-tasks if helpful) and prompt you to confirm readiness to proceed.

5. Reiterated “after each response” file-update rules

In your rules, the file-related requirements are also restated explicitly:

• changelog.md

  • Always create/update with all changes made at that time and date. Label them as Optional, Recommended, Required, or Critical.

• suggestions.md

  • Always create/update and append 15 suggestions (5 frontend, 5 backend, 5 trending/other). Label them as Optional, Recommended, Required, or Critical.
  • Never delete previous content.

• components.md

  • Always create/update with a detailed Markdown table of all components (used/needed, location, source). Label them as Optional, Recommended, Required, or Critical.
  • When pages already exist, scan code to determine components in use.

• todo.md

  • Always create/update, listing all tasks in Markdown checklist form. Label them as Optional, Recommended, Required, or Critical.
  • Mark completed tasks as checked.

• Error check before finishing

  • Always check for and fix errors before finishing a response.

• Project plan summary

  • Always give a bulleted plan covering every step from this point forward, with reasoning and descriptions. Label them as Optional, Recommended, Required, or Critical.

• Next steps from todo.md

  • Always suggest immediate next steps broken into sub-tasks and ask the user to proceed. Label them as Optional, Recommended, Required, or Critical.

---

Top 5 logical next steps (given all rules)

1. Prepare/update documentation and todos
   • Translate these into concrete entries in todo.md and changelog.md, ensuring everything is traceable once we’re in agent mode.

---

Top 5 frontend implementation suggestions

---

Top 5 backend implementation suggestions

---

Top 5 trending suggestions

---

Project summary (high level plan)

• Add user-facing customization

  • Build a Settings Panel to control and manage all options/settings/features, etc.

• Maintain excellent documentation and project hygiene

  • Keep changelog.md, suggestions.md, components.md, and todo.md up to date so progress is transparent and reproducible.

---