An **artifact** is a self-contained piece of content that I can create, display, and update during design, development and deployment cycle with clients. Think of it as a "living document" that we can collaborate on together. **What artifacts can contain:** - Code (Python, JavaScript, HTML, etc.) - Documents (markdown, reports, essays) - Interactive web applications - Data visualizations - Creative writing **Key features:** - **Persistent**: Once created, it stays visible and can be referenced throughout our chat - **Editable**: I can update specific parts without recreating the whole thing - **Interactive**: For web-based artifacts, you can actually interact with buttons, forms, etc. - **Downloadable**: You can save the content for use outside our conversation **When I use artifacts:** - Code solutions for specific problems - Documents you'll reference or reuse (like your motivation letter) - Interactive demos or tools - Creative content like stories or presentations - Structured content like meal plans or schedules **Simple analogy:** Think of our conversation as a workshop. Normally, we just talk about ideas. But artifacts are like actual prototypes I can build on the workbench that you can see, touch, test, and ask me to modify in real-time. For example, if you asked me to create a simple calculator, I'd build it as an interactive artifact where you could actually click buttons and see it work, rather than just showing you the code.