diff --git a/src/components/chat/DyadMarkdownParser.tsx b/src/components/chat/DyadMarkdownParser.tsx index ea22f3d..a1d34da 100644 --- a/src/components/chat/DyadMarkdownParser.tsx +++ b/src/components/chat/DyadMarkdownParser.tsx @@ -9,6 +9,7 @@ import { DyadExecuteSql } from "./DyadExecuteSql"; import { DyadAddIntegration } from "./DyadAddIntegration"; import { DyadEdit } from "./DyadEdit"; import { DyadCodebaseContext } from "./DyadCodebaseContext"; +import { DyadThink } from "./DyadThink"; import { CodeHighlight } from "./CodeHighlight"; import { useAtomValue } from "jotai"; import { isStreamingAtom } from "@/atoms/chatAtoms"; @@ -119,6 +120,7 @@ function preprocessUnclosedTags(content: string): { "dyad-chat-summary", "dyad-edit", "dyad-codebase-context", + "think", ]; let processedContent = content; @@ -183,6 +185,7 @@ function parseCustomTags(content: string): ContentPiece[] { "dyad-chat-summary", "dyad-edit", "dyad-codebase-context", + "think", ]; const tagPattern = new RegExp( @@ -268,6 +271,18 @@ function renderCustomTag( const { tag, attributes, content, inProgress } = tagInfo; switch (tag) { + case "think": + return ( + + {content} + + ); case "dyad-write": return ( = ({ children, node }) => { + const state = node?.properties?.state as CustomTagState; + const inProgress = state === "pending"; + const [isExpanded, setIsExpanded] = useState(inProgress); + + // Collapse when transitioning from in-progress to not-in-progress + useEffect(() => { + if (!inProgress && isExpanded) { + setIsExpanded(false); + } + }, [inProgress]); + + return ( +
setIsExpanded(!isExpanded)} + role="button" + aria-expanded={isExpanded} + tabIndex={0} + onKeyDown={(e) => { + if (e.key === "Enter" || e.key === " ") { + e.preventDefault(); + setIsExpanded(!isExpanded); + } + }} + > + {/* Top-left label badge */} +
+ + Thinking + {inProgress && ( + + )} +
+ + {/* Indicator icon */} +
+ {isExpanded ? : } +
+ + {/* Main content with smooth transition */} +
+
+ {typeof children === "string" ? ( + + ) : ( + children + )} +
+
+
+ ); +}; diff --git a/src/prompts/system_prompt.ts b/src/prompts/system_prompt.ts index 74f004d..f4cbdf3 100644 --- a/src/prompts/system_prompt.ts +++ b/src/prompts/system_prompt.ts @@ -1,3 +1,55 @@ +export const THINKING_PROMPT = ` +# Thinking Process + +Before responding to user requests, ALWAYS use tags to carefully plan your approach. This structured thinking process helps you organize your thoughts and ensure you provide the most accurate and helpful response. Your thinking should: + +- Use **bullet points** to break down the steps +- **Bold key insights** and important considerations +- Follow a clear analytical framework + +Example of proper thinking structure for a debugging request: + + +• **Identify the specific UI/FE bug described by the user** + - "Form submission button doesn't work when clicked" + - User reports clicking the button has no effect + - This appears to be a **functional issue**, not just styling + +• **Examine relevant components in the codebase** + - Form component at \`src/components/ContactForm.jsx\` + - Button component at \`src/components/Button.jsx\` + - Form submission logic in \`src/utils/formHandlers.js\` + - **Key observation**: onClick handler in Button component doesn't appear to be triggered + +• **Diagnose potential causes** + - Event handler might not be properly attached to the button + - **State management issue**: form validation state might be blocking submission + - Button could be disabled by a condition we're missing + - Event propagation might be stopped elsewhere + - Possible React synthetic event issues + +• **Plan debugging approach** + - Add console.logs to track execution flow + - **Fix #1**: Ensure onClick prop is properly passed through Button component + - **Fix #2**: Check form validation state before submission + - **Fix #3**: Verify event handler is properly bound in the component + - Add error handling to catch and display submission issues + +• **Consider improvements beyond the fix** + - Add visual feedback when button is clicked (loading state) + - Implement better error handling for form submissions + - Add logging to help debug edge cases + + +After completing your thinking process, proceed with your response following the guidelines above. Remember to be concise in your explanations to the user while being thorough in your thinking process. + +This structured thinking ensures you: +1. Don't miss important aspects of the request +2. Consider all relevant factors before making changes +3. Deliver more accurate and helpful responses +4. Maintain a consistent approach to problem-solving +`; + export const SYSTEM_PROMPT = ` You are Dyad, an AI editor that creates and modifies web applications. You assist users by chatting with them and making changes to their code in real-time. You understand that users can see a live preview of their application in an iframe on the right side of the screen while you make code changes. Not every interaction requires code changes - you're happy to discuss, explain concepts, or provide guidance without modifying the codebase. When code changes are needed, you make efficient and effective updates to React codebases while following best practices for maintainability and readability. You take pride in keeping things simple and elegant. You are friendly and helpful, always aiming to provide clear explanations. @@ -290,6 +342,8 @@ 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't be edited, so make new components if you need to change them. +${THINKING_PROMPT} + # REMEMBER > **CODE FORMATTING IS NON-NEGOTIABLE:**