SESP/sgse-app
2
0
Fork 0
Code Issues 3 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Refinament 1 #38

Merged
killer-cf merged 2 commits from refinament-1 into master 2025-11-22 13:26:25 +00:00
Conversation 1 Commits 2 Files Changed 3 +532 -534
3 changed files with 532 additions and 534 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
.agent/rules/svelte-rules.md Normal file
View File

@@ -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.

1034
apps/web/src/routes/(dashboard)/ti/configuracoes-email/+page.svelte
View File

File diff suppressed because it is too large Load Diff

4
packages/backend/convex/_generated/api.d.ts vendored
View File

@@ -29,8 +29,8 @@ import type * as cursos from "../cursos.js";
import type * as dashboard from "../dashboard.js"; import type * as dashboard from "../dashboard.js";
import type * as documentos from "../documentos.js"; import type * as documentos from "../documentos.js";
import type * as email from "../email.js"; import type * as email from "../email.js";
import type * as enderecosMarcacao from "../enderecosMarcacao.js";
import type * as empresas from "../empresas.js"; import type * as empresas from "../empresas.js";
import type * as enderecosMarcacao from "../enderecosMarcacao.js";
import type * as ferias from "../ferias.js"; import type * as ferias from "../ferias.js";
import type * as funcionarioEnderecos from "../funcionarioEnderecos.js"; import type * as funcionarioEnderecos from "../funcionarioEnderecos.js";
import type * as funcionarios from "../funcionarios.js"; import type * as funcionarios from "../funcionarios.js";
@@ -84,8 +84,8 @@ declare const fullApi: ApiFromModules<{
dashboard: typeof dashboard; dashboard: typeof dashboard;
documentos: typeof documentos; documentos: typeof documentos;
email: typeof email; email: typeof email;
enderecosMarcacao: typeof enderecosMarcacao;
empresas: typeof empresas; empresas: typeof empresas;
enderecosMarcacao: typeof enderecosMarcacao;
ferias: typeof ferias; ferias: typeof ferias;
funcionarioEnderecos: typeof funcionarioEnderecos; funcionarioEnderecos: typeof funcionarioEnderecos;
funcionarios: typeof funcionarios; funcionarios: typeof funcionarios;