diff --git a/.agent/rules/svelte-rules.md b/.agent/rules/svelte-rules.md new file mode 100644 index 0000000..30b100a --- /dev/null +++ b/.agent/rules/svelte-rules.md @@ -0,0 +1,28 @@ +--- +trigger: glob +globs: **/*.svelte.ts,**/*.svelte +--- + +You are able to use the Svelte MCP server, where you have access to comprehensive Svelte 5 and SvelteKit documentation. Here's how to use the available tools effectively: + +## Available MCP Tools: + +### 1. list-sections + +Use this FIRST to discover all available documentation sections. Returns a structured list with titles, use_cases, and paths. +When asked about Svelte or SvelteKit topics, ALWAYS use this tool at the start of the chat to find relevant sections. + +### 2. get-documentation + +Retrieves full documentation content for specific sections. Accepts single or multiple sections. +After calling the list-sections tool, you MUST analyze the returned documentation sections (especially the use_cases field) and then use the get-documentation tool to fetch ALL documentation sections that are relevant for the user's task. + +### 3. svelte-autofixer + +Analyzes Svelte code and returns issues and suggestions. +You MUST use this tool whenever writing Svelte code before sending it to the user. Keep calling it until no issues or suggestions are returned. + +### 4. playground-link + +Generates a Svelte Playground link with the provided code. +After completing the code, ask the user if they want a playground link. Only call this tool after user confirmation and NEVER if code was written to files in their project. diff --git a/apps/web/src/routes/(dashboard)/ti/configuracoes-email/+page.svelte b/apps/web/src/routes/(dashboard)/ti/configuracoes-email/+page.svelte index 15a7f1a..3e316e6 100644 --- a/apps/web/src/routes/(dashboard)/ti/configuracoes-email/+page.svelte +++ b/apps/web/src/routes/(dashboard)/ti/configuracoes-email/+page.svelte @@ -1,574 +1,544 @@ -
- Configurar servidor de email para envio de notificações -
-+ Configurar servidor de email para envio de notificações +
+| Provedor | -Servidor | -Porta | -Segurança | -
|---|---|---|---|
| Gmail | -smtp.gmail.com | -587 | -TLS | -
| Outlook/Office365 | -smtp.office365.com | -587 | -TLS | -
| Yahoo | -smtp.mail.yahoo.com | -465 | -SSL | -
| SendGrid | -smtp.sendgrid.net | -587 | -TLS | -
| Provedor | +Servidor | +Porta | +Segurança | +
|---|---|---|---|
| Gmail | +smtp.gmail.com | +587 | +TLS | +
| Outlook/Office365 | +smtp.office365.com | +587 | +TLS | +
| Yahoo | +smtp.mail.yahoo.com | +465 | +SSL | +
| SendGrid | +smtp.sendgrid.net | +587 | +TLS | +
- Dica de Segurança: Para Gmail e outros provedores, você - pode precisar gerar uma "senha de app" específica em vez de usar sua senha - principal. -
-- Gmail: Conta Google → Segurança → Verificação em duas etapas → Senhas de - app -
-+ Dica de Segurança: Para Gmail e outros provedores, você pode precisar gerar + uma "senha de app" específica em vez de usar sua senha principal. +
++ Gmail: Conta Google → Segurança → Verificação em duas etapas → Senhas de app +
+