AI Studio's chat composer is now richer. Point the AI at specific files with @, and start common integrations with / skills. Responses also stream in more smoothly.

### The challenge

To point the AI at a particular file, or to ask for a common integration, you had to describe it in plain text and hope it was understood. Streaming replies could also look jumpy while they rendered.

### What's new

• **@ file references (Code view):** Type @ to pick a project file, optionally down to a line or range. It appears as a pill in the composer and in sent messages.

• **/ skills (Builder):** Type / to pick a built-in skill: Database Optimization, Form Tracking, Calendar Integration, Payment Integration or Chat Widget. You can use one skill per message, and integration skills ask you to choose the integration before they run.

• Smoother streaming: Replies appear smoothly as they stream, Markdown renders without stutter, and reduced-motion settings are respected.
• Rich composer: Image attachments, selected-element context, international keyboard (IME) input and the 50,000-character limit all work as before.

### How this helps your business

• More precise edits: Tell the AI exactly which file or lines to change.
• Faster integrations: Start forms, calendars, payments and chat widgets in one step.
• Cleaner experience: Responses are easier to follow as they arrive.
• More accessible: Pickers work with keyboards and screen readers, and reduced motion is supported.

### How to get started

1. Navigate to AI Studio, open a project, then go to Chat.
2. Activate: type @ in Code view to reference a file, or / in Builder to choose a skill.
3. Enjoy: for example, type /, choose Payment Integration, pick your integration, and send.

### Good to know

• @ file references work in Code view only. / skills work in Builder only.
• A file reference tells the AI which file you mean. It does not pin the file's contents into context.
• Typing / or @ as plain text still works. If nothing matches, Enter sends the message normally (e.g. "fix the /pricing page").
• Database Optimization is unavailable while there's a Cloud status error. The other skills are unaffected.
• No data migration is needed. Existing chats and skill follow-ups keep working.