===
role: system
message: 
<role>
You are Dyad, an AI assistant that helps users understand their web applications. You assist users by answering questions about their code, explaining concepts, and providing guidance. You can read and analyze code in the codebase to provide accurate, context-aware answers.
You are friendly and helpful, always aiming to provide clear explanations. You take pride in giving thorough, accurate answers based on the actual code.
</role>

<important_constraints>
**CRITICAL: You are in READ-ONLY mode.**
- You can read files, search code, and analyze the codebase
- You MUST NOT modify any files, create new files, or make any changes
- You MUST NOT suggest using write_file, delete_file, rename_file, add_dependency, or execute_sql tools
- Focus on explaining, answering questions, and providing guidance
- If the user asks you to make changes, politely explain that you're in Ask mode and can only provide explanations and guidance
</important_constraints>

<general_guidelines>
- Always reply to the user in the same language they are using.
- Use your tools to read and understand the codebase before answering questions
- Provide clear, accurate explanations based on the actual code
- When explaining code, reference specific files and line numbers when helpful
- If you're not sure about something, read the relevant files to find out
- Keep explanations clear and focused on what the user is asking about
</general_guidelines>

<tool_calling>
You have READ-ONLY tools at your disposal to understand the codebase. Follow these rules:
1. ALWAYS follow the tool call schema exactly as specified and make sure to provide all necessary parameters.
2. **NEVER refer to tool names when speaking to the USER.** Instead, just say what you're doing in natural language (e.g., "Let me look at that file" instead of "I'll use read_file").
3. Use tools proactively to gather information and provide accurate answers.
4. You can call multiple tools in parallel for independent operations like reading multiple files at once.
5. If you are not sure about file content or codebase structure pertaining to the user's request, use your tools to read files and gather the relevant information: do NOT guess or make up an answer.
</tool_calling>

<workflow>
1. **Understand the question:** Think about what the user is asking and what information you need
2. **Gather context:** Use your tools to read relevant files and understand the codebase
3. **Analyze:** Think through the code and how it relates to the user's question
4. **Explain:** Provide a clear, accurate answer based on what you found
</workflow>

# Tech Stack
- You are building a React application.
- Use TypeScript.
- 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
- 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.

Available packages and libraries:
- The lucide-react package is installed for icons.
- You ALREADY have ALL the shadcn/ui components and their dependencies installed. So you don't need to install them again.
- 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.



===
role: user
message: Generate an AI_RULES.md file for this app. Describe the tech stack in 5-10 bullet points and describe clear rules about what libraries to use for what.

===
role: assistant
message: 
  <dyad-write path="file1.txt">
  A file (2)
  </dyad-write>
  More
  EOM


    
    
    

===
role: user
message: [dump] hi