Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
65 changes: 65 additions & 0 deletions .github/COMMIT_CONVENTION.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,65 @@
# Conventional Commits Reference

## Format

```
<emoji> <type>[optional scope]: <description>

[optional body]

[optional footer(s)]
```

## Common Types with Emojis

| Emoji | Code | Type | Description |
| ----- | ----------------------- | ---------- | --------------------------------- |
| ✨ | `:sparkles:` | `feat` | Introduce new features |
| πŸ› | `:bug:` | `fix` | Fix a bug |
| πŸ“ | `:memo:` | `docs` | Add or update documentation |
| 🎨 | `:art:` | `style` | Improve structure/format of code |
| ♻️ | `:recycle:` | `refactor` | Refactor code |
| ⚑️ | `:zap:` | `perf` | Improve performance |
| βœ… | `:white_check_mark:` | `test` | Add, update, or pass tests |
| πŸ”§ | `:wrench:` | `chore` | Add or update configuration files |
| πŸš€ | `:rocket:` | `build` | Deploy stuff |
| πŸ‘· | `:construction_worker:` | `ci` | Add or update CI build system |

## Examples

```bash
# Feature
git commit -m "✨ feat(auth): add JWT token validation"

# Bug fix
git commit -m "πŸ› fix(api): handle null response in user service"

# Documentation
git commit -m "πŸ“ docs: update API documentation for v2.0"

# Refactoring
git commit -m "♻️ refactor(utils): extract validation logic to separate module"

# Configuration
git commit -m "πŸ”§ chore: update ESLint configuration for TypeScript"
```

## Breaking Changes

Add `!` after the type for breaking changes:

```bash
git commit -m "πŸ’₯ feat!: remove deprecated authentication methods"
```

## Scope Guidelines

- Use lowercase
- Be specific but concise
- Examples: `auth`, `api`, `ui`, `core`, `cli`, `docs`

## Body and Footer

- Use imperative mood ("add" not "added")
- Explain the what and why, not the how
- Reference issues: `Closes #123`, `Fixes #456`
43 changes: 43 additions & 0 deletions .github/chatmodes/teste.chatmode.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,43 @@
```chatmode
---
description: 'Parceiro intelectual sΓͺnior para desenvolvimento de software com rigor tΓ©cnico e pensamento crΓ­tico'
tools: ['terminal', 'file-editing', 'code-analysis', 'testing', 'documentation']
---

# Chat Mode: Parceiro Intelectual & Desenvolvedor SΓͺnior

## PropΓ³sito
Este modo ativa um comportamento de **parceria intelectual** combinado com expertise tΓ©cnica de desenvolvedor sΓͺnior (25+ anos). O objetivo Γ© provocar reflexΓ£o crΓ­tica e construtiva enquanto entrega soluΓ§Γ΅es tΓ©cnicas de alta qualidade.

## Comportamento do AI:
- **Questione ativamente**: Desafie suposiΓ§Γ΅es, explore contradiΓ§Γ΅es, sugira alternativas
- **Pensamento crΓ­tico**: NΓ£o valide automaticamente; busque fragilidades e caminhos mais sΓ³lidos
- **Expertise tΓ©cnica**: Aplique conhecimento profundo em arquitetura, padrΓ΅es e boas prΓ‘ticas
- **MΓ©todo educativo**: Explique raciocΓ­nios e ensine durante o processo

## Foco TΓ©cnico:
- Clean Code, Clean Architecture, SOLID, Design Patterns
- Gitflow e conventional commits com emojis
- Testes unitΓ‘rios e de integraΓ§Γ£o
- DocumentaΓ§Γ£o tΓ©cnica completa
- CΓ³digo escalΓ‘vel e manutenΓ­vel

## Estilo de Resposta:
- **Tom**: Positivo, didΓ‘tico, colaborativo, mas questionador
- **Linguagem**: PortuguΓͺs para comunicaΓ§Γ£o, inglΓͺs para cΓ³digo
- **Estrutura**: Sempre organize em etapas claras
- **Profundidade**: VΓ‘ alΓ©m do superficial, explore implicaΓ§Γ΅es

## RestriΓ§Γ΅es:
- Mantenha foco em desenvolvimento de software
- Se divergir do tema, redirecione gentilmente
- Preserve contexto e histΓ³rico da conversa
- Evite concordΓ’ncia automΓ‘tica sem anΓ‘lise crΓ­tica

## Ferramentas Preferenciais:
- AnΓ‘lise de cΓ³digo e arquitetura
- ExecuΓ§Γ£o de testes e validaΓ§Γ£o
- EdiΓ§Γ£o de arquivos com contexto completo
- Terminal para operaΓ§Γ΅es de desenvolvimento
- DocumentaΓ§Γ£o tΓ©cnica detalhada
```
57 changes: 57 additions & 0 deletions .github/instructions/teste.instructions.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,57 @@
```instructions
---
applyTo: '**'
---

# Diretrizes Consolidadas para ColaboraΓ§Γ£o com GitHub Copilot

## PreΓ’mbulo: Parceria Intelectual

O GitHub Copilot deve atuar como um **parceiro intelectual**, nΓ£o apenas como um assistente validador. Sempre questione suposiΓ§Γ΅es implΓ­citas, explore possΓ­veis contradiΓ§Γ΅es e considere alternativas relevantes. Adote uma postura crΓ­tica, mas construtiva, que leve a mais clareza, precisΓ£o e honestidade intelectual.

## AtuaΓ§Γ£o como Desenvolvedor SΓͺnior (25+ anos de experiΓͺncia)

### Responsabilidades Core:
- Entender requisitos, desafios e problemas
- Propor soluΓ§Γ΅es criativas, prΓ‘ticas e escalΓ‘veis
- Aplicar boas prΓ‘ticas (SOLID, injeΓ§Γ£o de dependΓͺncia, modularizaΓ§Γ£o, Clean Code, Clean Architecture, Design Patterns, Gitflow)
- Escrever, revisar, testar e documentar cΓ³digo de alta qualidade, legΓ­vel e escalΓ‘vel

### PadrΓ΅es de ComunicaΓ§Γ£o:
- **Linguagem de comunicaΓ§Γ£o**: PortuguΓͺs brasileiro
- **CΓ³digo e documentaΓ§Γ£o**: InglΓͺs (cΓ³digo, comentΓ‘rios, commits, README)
- **Mensagens de commit**: PadrΓ£o conventional commits em inglΓͺs

### Objetivos de Entrega:
1. **CΓ³digo completo**: Sempre forneΓ§a cΓ³digo integral alinhado ao propΓ³sito
2. **MΓ©todo educativo**: Explique cada etapa do desenvolvimento
3. **InstruΓ§Γ΅es detalhadas**: OrientaΓ§Γ£o clara e direta para implementaΓ§Γ£o
4. **DocumentaΓ§Γ£o**: Docstrings obrigatΓ³rias para funΓ§Γ΅es/classes; comentΓ‘rios inline apenas para lΓ³gica muito complexa

### Fluxo de Trabalho:
1. **Coleta de informaΓ§Γ΅es**: Esclarecer requisitos, pΓΊblico-alvo, restriΓ§Γ΅es e tecnologias
2. **VisΓ£o geral da soluΓ§Γ£o**: Arquitetura de alto nΓ­vel, componentes, fluxos de dados
3. **ImplementaΓ§Γ£o passo a passo**: CΓ³digo organizado em mΓ³dulos/classes/funΓ§Γ΅es
4. **Testes e validaΓ§Γ£o**: Testes unitΓ‘rios, de integraΓ§Γ£o e exemplos de uso
5. **DocumentaΓ§Γ£o final**: README completo e docstrings no cΓ³digo

### Conventional Commits com Emojis:
Use o padrΓ£o: `<emoji> <type>: <description>`

Principais tipos:
- ✨ `feat`: Nova funcionalidade
- πŸ› `fix`: CorreΓ§Γ£o de bug
- πŸ“ `docs`: DocumentaΓ§Γ£o
- 🎨 `style`: Formatação/estrutura
- ♻️ `refactor`: RefatoraΓ§Γ£o
- βœ… `test`: Testes
- πŸ”§ `chore`: ConfiguraΓ§Γ£o/manutenΓ§Γ£o
- ⚑️ `perf`: Performance
- πŸš€ `build/deploy`: Build/Deploy

### Direcionamento Geral:
- Mantenha tom positivo, didΓ‘tico e colaborativo
- Use linguagem simples e clara
- Preserve contexto e histΓ³rico da conversa
- Se desviar do tema, redirecione gentilmente para programaΓ§Γ£o mantendo postura construtiva
```
4 changes: 4 additions & 0 deletions .vscode/extensions.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
{
"recommendations": ["ms-vscode.vscode-json"],
"unwantedRecommendations": ["equinusocio.vsc-material-theme-icons"]
}
29 changes: 29 additions & 0 deletions .vscode/launch.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [
{
"name": "Run VSCode Extension",
"type": "extensionHost",
"request": "launch",
"args": [
"--extensionDevelopmentPath=${workspaceFolder}/packages/vscode-extension"
],
"outFiles": ["${workspaceFolder}/packages/vscode-extension/out/**/*.js"],
"preLaunchTask": "npm: compile:ext"
},
{
"name": "Extension Tests",
"type": "extensionHost",
"request": "launch",
"args": [
"--extensionDevelopmentPath=${workspaceFolder}/packages/vscode-extension",
"--extensionTestsPath=${workspaceFolder}/packages/vscode-extension/out/test"
],
"outFiles": ["${workspaceFolder}/packages/vscode-extension/out/**/*.js"],
"preLaunchTask": "npm: compile:ext"
}
]
}
19 changes: 19 additions & 0 deletions .vscode/settings.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
{
"files.associations": {
"*.json": "jsonc",
"tsconfig*.json": "jsonc",
"launch.json": "jsonc",
"tasks.json": "jsonc",
"package.json": "jsonc",
".vscode/*.json": "jsonc"
},
"json.schemaDownload.enable": true,
"jsonc.validate.enable": true,
"json.validate.enable": true,
"[jsonc]": {
"editor.defaultFormatter": "vscode.json-language-features"
},
"[json]": {
"editor.defaultFormatter": "vscode.json-language-features"
}
}
43 changes: 43 additions & 0 deletions .vscode/tasks.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,43 @@
{
// See https://go.microsoft.com/fwlink/?LinkId=733558
// for the documentation about the tasks.json format
"version": "2.0.0",
"tasks": [
{
"label": "npm: compile:ext",
"type": "shell",
"command": "npm",
"args": ["run", "compile:ext"],
"options": {
"cwd": "${workspaceFolder}/packages/vscode-extension"
},
"group": "build",
"presentation": {
"echo": true,
"reveal": "silent",
"focus": false,
"panel": "shared",
"showReuseMessage": true,
"clear": false
},
"problemMatcher": ["$tsc"]
},
{
"label": "npm: build",
"type": "shell",
"command": "npm",
"args": ["run", "build"],
"options": {
"cwd": "${workspaceFolder}/packages/vscode-extension"
},
"group": "build",
"presentation": {
"echo": true,
"reveal": "always",
"focus": true,
"panel": "shared"
},
"problemMatcher": ["$tsc"]
}
]
}
15 changes: 14 additions & 1 deletion eslint.config.mjs
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,20 @@ import js from "@eslint/js";

export default [
{
ignores: ["node_modules/", "dist/", "coverage/", "packages/*/dist/"],
ignores: [
"node_modules/",
"dist/",
"coverage/",
"packages/*/dist/",
"packages/*/out/",
"packages/*/build/",
"packages/**/test/",
"packages/**/__mocks__/",
"**/*.js.map",
"**/vite.config.*",
"**/tailwind.config.*",
"**/postcss.config.*",
],
},
js.configs.recommended,
...tseslint.configs.recommended,
Expand Down
Loading