Updated AI_RULES.md
This commit is contained in:
parent
ad018e75d8
commit
ae24415f5a
1 changed files with 20 additions and 6 deletions
26
AI_RULES.md
26
AI_RULES.md
|
|
@ -2,11 +2,11 @@
|
|||
|
||||
- You are building a React application.
|
||||
- Use TypeScript.
|
||||
- Use React Router. KEEP the routes in src/App.tsx
|
||||
- Use React Router. KEEP the routes in src/App.tsx.
|
||||
- Always put source code in the src folder.
|
||||
- Put pages into src/pages/
|
||||
- Put components into src/components/
|
||||
- The main page (default page) is src/pages/Index.tsx
|
||||
- Put pages into src/pages/.
|
||||
- Put components into src/components/.
|
||||
- The main page (default page) is src/pages/Index.tsx.
|
||||
- UPDATE the main page to include the new components. OTHERWISE, the user can NOT see any components!
|
||||
- ALWAYS try to use the shadcn/ui library.
|
||||
- Tailwind CSS: always use Tailwind CSS for styling components. Utilize Tailwind classes extensively for layout, spacing, colors, and other design aspects.
|
||||
|
|
@ -18,8 +18,22 @@ Available packages and libraries:
|
|||
- You have ALL the necessary Radix UI components installed.
|
||||
- Use prebuilt components from the shadcn/ui library after importing them. Note that these files shouldn't be edited, so make new components if you need to change them.
|
||||
|
||||
---
|
||||
|
||||
Task List Management Rules:
|
||||
# Preservation & Safety Rules
|
||||
|
||||
- NEVER delete existing components, pages, or data structures unless explicitly instructed by the user.
|
||||
- When modifying files, UPDATE existing code in place rather than rewriting the entire file unless unavoidable.
|
||||
- Always preserve existing routes in `src/App.tsx`. Only ADD new routes; never remove existing ones unless explicitly requested.
|
||||
- For database schemas or data models, NEVER remove or rename fields without explicit user confirmation. Only add or extend.
|
||||
- Do not remove or overwrite existing styles, utility functions, or shared components. Extend or enhance them instead.
|
||||
- If an update requires removing or replacing something, ASK the user for confirmation before making the change.
|
||||
- Always show or describe a clear diff of proposed changes (what is added/modified vs. removed).
|
||||
- Default behavior: PRESERVE existing functionality and UI. All changes should be additive unless instructed otherwise.
|
||||
|
||||
---
|
||||
|
||||
# Task List Management Rules
|
||||
|
||||
- Always create a task list of all steps needed to build the app.
|
||||
- Provide feedback in the chat after each task is completed.
|
||||
|
|
@ -27,4 +41,4 @@ Task List Management Rules:
|
|||
- Add new tasks dynamically if additional steps are identified.
|
||||
- Keep the task list up to date throughout the entire development process.
|
||||
- Tasks should be actionable and clearly numbered or bulleted for easy tracking.
|
||||
- The user should be able to see progress and completed tasks at a glance.
|
||||
- The user should be able to see progress and completed tasks at a glance.
|
||||
|
|
|
|||
Loading…
Reference in a new issue