@netoalmanca/advpl-sensei 1.1.0

package/commands/generate.md

@@ -0,0 +1,111 @@
+---
+description: Generate ADVPL/TLPP code - functions, classes, MVC structures, REST APIs, Web Services, and entry points for TOTVS Protheus
+allowed-tools: Read, Write, Edit, Glob, Grep, Bash, Agent, Skill, WebSearch, WebFetch
+argument-hint: "<type> [name] [--module module]"
+---
+
+# /advpl-specialist:generate
+
+**IMPORTANT:** Always respond in the same language the user is writing in. If the user writes in Portuguese, respond in Portuguese. If in English, respond in English. Adapt all explanations and suggestions to the user's language. Code comments may remain in English or match the user's language.
+
+Generate new ADVPL or TLPP code following Protheus conventions and best practices.
+
+## Usage
+
+```bash
+/advpl-specialist:generate <type> [name] [--module <module>]
+```
+
+## Types
+
+| Type | Description | Output |
+|------|------------|--------|
+| `function` | User Function | .prw file |
+| `class` | TLPP class | .tlpp file |
+| `mvc` | MVC structure (MenuDef, ModelDef, ViewDef) | .prw file |
+| `rest` | REST API endpoint | .prw or .tlpp file |
+| `ponto-entrada` | Entry point | .prw file |
+| `webservice` | SOAP Web Service | .prw file |
+| `treport` | TReport report | .prw file |
+| `fwformbrowse` | FWFormBrowse/FWExecView screen | .prw file |
+| `job` | Batch job / scheduled process | .prw or .tlpp file |
+| `workflow` | Approval workflow process | .prw file |
+
+## Options
+
+| Flag | Description | Default |
+|------|------------|---------|
+| `--module` | Module prefix (COM, FAT, FIN, etc.) | Ask user |
+| `--lang` | Language: advpl or tlpp | advpl for function/mvc/pe, tlpp for class |
+| `--output` | Output file path | Auto-generated based on name |
+
+## Process
+
+**MANDATORY: Always enter planning mode before generating code. Never skip planning.**
+
+### Planning Phase (REQUIRED)
+1. **Parse arguments** - Extract type, name, and flags
+2. **Ask missing details** - If name or module not provided, ask the user
+3. **Ask business requirements** - What should the code do?
+4. **Load skill** - Invoke `advpl-code-generation` skill
+5. **Load patterns** - Read appropriate supporting file for the type
+6. **Search TDN for entry points** - **If the type is `ponto-entrada`**, ALWAYS search the TDN (TOTVS Developer Network) for the entry point name before generating code. Use `WebSearch` to find the official documentation page (e.g., search for `"ENTRY_POINT_NAME site:tdn.totvs.com"`). Extract from the TDN page: PARAMIXB parameters (types, positions, descriptions), expected return type and value, which standard routine calls this entry point, and any caveats or version-specific behavior. This ensures the generated code uses the correct parameters and return type as defined by TOTVS.
+7. **Enter plan mode** - Use `EnterPlanMode` to create a structured implementation plan
+8. **Present plan** - Show the user a clear plan including:
+   - File(s) to be created (name, path, extension)
+   - Code structure (functions, classes, methods to implement)
+   - Includes and dependencies
+   - Key patterns to apply (MVC, REST, SOAP, etc.)
+   - Naming conventions to follow (Hungarian notation, module prefix)
+   - Error handling and DB operation patterns
+   - **For entry points:** TDN documentation found (PARAMIXB parameters, return type, calling routine)
+9. **Wait for approval** - The user must approve the plan before any code is written. If the user requests changes, revise the plan.
+10. **Exit plan mode** - Use `ExitPlanMode` after approval
+
+### Implementation Phase (only after approval)
+11. **Generate code** - Create complete, production-ready code following the approved plan
+12. **Write file** - Save with correct extension (.prw or .tlpp)
+13. **Report** - Show what was created and key decisions
+
+## Examples
+
+```bash
+# Create a User Function for billing module
+/advpl-specialist:generate function FATA050 --module FAT
+
+# Create a TLPP service class
+/advpl-specialist:generate class PedidoService
+
+# Create complete MVC CRUD
+/advpl-specialist:generate mvc CadProduto --module EST
+
+# Create a REST API endpoint
+/advpl-specialist:generate rest ClienteAPI --lang tlpp
+
+# Create an entry point
+/advpl-specialist:generate ponto-entrada MT100LOK
+
+# Create a SOAP Web Service
+/advpl-specialist:generate webservice WSPedido
+
+# Create a TReport report
+/advpl-specialist:generate treport RelProdutos --module EST
+
+# Create a FWFormBrowse screen
+/advpl-specialist:generate fwformbrowse CadFornecedores --module COM
+
+# Create a batch processing job
+/advpl-specialist:generate job JobProcessaNotas --module FAT
+
+# Create an approval workflow
+/advpl-specialist:generate workflow AprovacaoPedido --module COM
+```
+
+## Output
+
+A complete, compilable source file saved to the project directory with:
+- Protheus.doc documentation header
+- Proper includes/namespace declarations
+- Full implementation following conventions
+- Error handling
+- Area save/restore for DB operations

package/commands/migrate.md

@@ -0,0 +1,81 @@
+---
+description: Migrate ADVPL procedural code to TLPP object-oriented code with classes, namespaces, and modern patterns
+allowed-tools: Read, Write, Edit, Glob, Grep, Bash, Agent, Skill, WebSearch, WebFetch
+argument-hint: "<file.prw> [--output file.tlpp] [--dry-run]"
+---
+
+# /advpl-specialist:migrate
+
+**IMPORTANT:** Always respond in the same language the user is writing in. If the user writes in Portuguese, respond in Portuguese. If in English, respond in English. Adapt all explanations and suggestions to the user's language. Code comments may remain in English or match the user's language.
+
+Convert ADVPL procedural code to TLPP with object-oriented patterns.
+
+## Usage
+
+```bash
+/advpl-specialist:migrate <file.prw> [options]
+```
+
+## Options
+
+| Flag | Description | Default |
+|------|------------|---------|
+| `--output` | Output .tlpp file path | Same name with .tlpp extension |
+| `--dry-run` | Show migration plan without generating files | false |
+| `--keep-original` | Keep the original .prw file | true |
+| `--wrapper` | Generate backward compatibility wrapper | true |
+| `--namespace` | Override namespace | Auto-detect from module |
+
+## Process
+
+**MANDATORY: Always enter planning mode before migrating code. Never skip planning.**
+
+### Analysis Phase
+1. **Read source file** - Read the .prw file completely
+2. **Analyze structure** - Identify functions, dependencies, shared variables
+3. **Search for callers** - Grep codebase for `u_FunctionName` references
+
+### Planning Phase (REQUIRED)
+4. **Load skill** - Invoke `advpl-to-tlpp-migration` skill for rules and checklist
+5. **Enter plan mode** - Use `EnterPlanMode` to create a structured migration plan
+6. **Design class structure** - Map functions to classes and methods
+7. **Present plan** - Show the user a detailed migration plan including:
+   - Source file analysis (functions found, dependencies, shared variables)
+   - External callers that will be impacted
+   - Target class structure (class name, namespace, properties, methods)
+   - Mapping: which function becomes which method (public/private)
+   - Private/Public variables to convert to class properties
+   - Includes to update (TOTVS.CH -> tlpp-core.th, etc.)
+   - Whether a backward compatibility wrapper is needed
+   - Any risks or breaking changes
+8. **Wait for approval** - The user must approve the plan before any code is written. If the user requests changes, revise the plan.
+9. **If --dry-run** - Stop here after showing the plan
+10. **Exit plan mode** - Use `ExitPlanMode` after approval
+
+### Implementation Phase (only after approval)
+11. **Execute migration** - Generate .tlpp file(s) following the approved plan and `advpl-to-tlpp-migration` skill
+12. **Generate wrapper** - Create backward compatibility .prw wrapper if --wrapper
+13. **Run checklist** - Validate against migration-checklist.md
+14. **Report** - Show summary of changes
+
+## Examples
+
+```bash
+# Migrate a file (shows plan first, then generates)
+/advpl-specialist:migrate src/FATA001.prw
+
+# Preview migration without generating files
+/advpl-specialist:migrate src/FATA001.prw --dry-run
+
+# Specify output path and namespace
+/advpl-specialist:migrate src/FATA001.prw --output src/tlpp/PedidoService.tlpp --namespace mycompany.faturamento
+
+# Migrate without backward compatibility wrapper
+/advpl-specialist:migrate src/FATA001.prw --wrapper false
+```
+
+## Output
+
+- `.tlpp` file with migrated class-based code
+- Optional `.prw` wrapper for backward compatibility
+- Migration summary with what changed and why

package/commands/process.md

@@ -0,0 +1,111 @@
+---
+description: Consult Protheus ERP business processes, module workflows, routines and integrations
+allowed-tools: Read, Glob, Grep, WebSearch, WebFetch, Skill, Bash, EnterPlanMode, ExitPlanMode, browser_navigate, browser_snapshot, browser_take_screenshot, browser_fill_form, browser_click, browser_close
+argument-hint: "<process|routine|module> [--type process|routine|module|integration]"
+agent: process-consultant
+---
+
+# /advpl-specialist:process
+
+**IMPORTANT:** Always respond in the same language the user is writing in. If the user writes in Portuguese, respond in Portuguese. If in English, respond in English. Adapt all explanations, process descriptions, and references to the user's language.
+
+Consult Protheus ERP business processes, module workflows, routines, and integrations.
+
+## Usage
+
+```bash
+/advpl-specialist:process <query> [options]
+```
+
+## Options
+
+| Flag | Description | Default |
+|------|------------|---------|
+| `--type` | Query type: `process`, `routine`, `module`, `integration` | auto-detect |
+
+## Process
+
+1. **Load skill** - Invoke `protheus-business` skill
+2. **Parse query** - Extract search term and options
+3. **Classify query type** - If `--type` not specified, auto-detect:
+   - Contains routine code (e.g. MATA410, FINA040) -> routine
+   - Contains module name (Compras, Faturamento, Estoque, etc.) -> module
+   - Contains two module names or keywords like "integracao" / "integration" -> integration
+   - Otherwise -> process
+4. **Search local reference** - Check protheus-business skill module files (modulo-compras.md, modulo-estoque.md, etc.)
+5. **Search TDN** - If not found locally, search TDN online:
+   - Process: `site:tdn.totvs.com "<process>" protheus fluxo`
+   - Routine: `site:tdn.totvs.com "<ROUTINE_CODE>" rotina`
+   - Module: `site:tdn.totvs.com "<module>" modulo protheus`
+   - Integration: `site:tdn.totvs.com "<moduleA>" "<moduleB>" integracao`
+6. **Playwright fallback** - If WebSearch/WebFetch fail:
+   - If URL available: `browser_navigate` -> `browser_snapshot` -> `browser_take_screenshot` if needed
+   - If no URL: `browser_navigate` to `https://tdn.totvs.com` -> `browser_fill_form` search -> `browser_click` submit -> `browser_snapshot` results -> navigate to best result
+   - **Always** `browser_close` when finished to release resources
+7. **Deliver answer** - Format response based on query type
+
+## Response Format
+
+Adaptive based on query type:
+
+**Process query:**
+- Description of the process
+- Step-by-step flow with routines and tables at each step
+- Integrations with other modules
+- Available entry points
+
+**Routine query:**
+- What the routine does
+- Tables it reads/writes
+- MV parameters it uses
+- Which process it belongs to
+- Available entry points
+
+**Module query:**
+- Module overview
+- Main tables
+- Main routines
+- Key business processes
+- Integrations with other modules
+
+**Integration query:**
+- Data flow between modules
+- Linking tables
+- Routines involved at each side
+- Direction of data flow
+
+## Cross-References
+
+When the user needs more detail, load additional skills:
+- **protheus-reference** - for native function details (syntax, parameters, return values)
+- **advpl-code-generation** - for code examples and implementation patterns
+- **embedded-sql** - for query examples using Embedded SQL
+
+## Examples
+
+```bash
+# Understand a business process
+/advpl-specialist:process fluxo de compras
+
+# Look up a specific routine
+/advpl-specialist:process MATA410
+
+# Understand a module
+/advpl-specialist:process modulo Faturamento --type module
+
+# Understand integration between modules
+/advpl-specialist:process integracao Compras Estoque --type integration
+
+# Ask in natural language
+/advpl-specialist:process como funciona o processo de faturamento no Protheus?
+
+# Look up financial process
+/advpl-specialist:process contas a pagar
+```
+
+## Output
+
+- Clear, structured explanation adapted to query type
+- References to routines, tables, and entry points
+- Source citation (local reference or TDN)
+- Suggestions for related skills when further detail is needed

package/commands/refactor.md

@@ -0,0 +1,65 @@
+---
+description: Refactor ADVPL/TLPP code - extract functions, simplify logic, remove dead code, improve naming
+allowed-tools: Read, Write, Edit, Glob, Grep, Bash, Agent, Skill, WebSearch, WebFetch
+argument-hint: "<file> [--dry-run]"
+---
+
+**IMPORTANT:** Always respond in the same language the user is writing in. If the user writes in Portuguese, respond in Portuguese. If in English, respond in English.
+
+# /advpl-specialist:refactor
+
+Analyze and refactor ADVPL/TLPP code to improve structure without changing behavior.
+
+## Usage
+
+```bash
+/advpl-specialist:refactor <target> [options]
+```
+
+## Options
+
+| Flag | Description | Default |
+|------|------------|---------|
+| `--dry-run` | Show suggestions without applying changes | false |
+
+## Refactoring Patterns
+
+| ID | Pattern | Risk |
+|----|---------|------|
+| RF-001 | Extract Function (>100 lines) | Low |
+| RF-002 | Simplify Conditionals (>3 levels) | Low |
+| RF-003 | Remove Dead Code | Low |
+| RF-004 | Improve Naming (Hungarian notation) | Low |
+| RF-005 | Eliminate Duplication | Medium |
+| RF-006 | Reduce Parameters (>5 params) | Medium |
+
+## Process
+
+**MANDATORY: Always enter planning mode before applying changes. Never refactor without approval.**
+
+1. **Parse arguments** — Identify target file(s) and flags
+2. **Load refactoring skill** — Invoke `advpl-refactoring` skill
+3. **Delegate to refactorer agent** — Pass target and options to the refactorer agent
+4. **Present plan** — Structured list of refactorings with before/after for each
+5. **Wait for approval** — User must approve before changes are applied
+6. **Apply changes** — One refactoring at a time (unless --dry-run)
+7. **Report** — Summary of changes applied
+
+## Examples
+
+```bash
+# Refactor a source file (interactive, with approval)
+/advpl-specialist:refactor src/FATA001.prw
+
+# Show suggestions without applying
+/advpl-specialist:refactor src/FATA001.prw --dry-run
+
+# Refactor all files in a directory
+/advpl-specialist:refactor src/
+```
+
+## Output
+
+- List of refactoring opportunities found, ordered by priority
+- Before/after code for each suggestion
+- Summary of improvements (function count, max length, naming compliance)

package/commands/review.md

@@ -0,0 +1,60 @@
+---
+description: Review ADVPL/TLPP code for best practices, performance, security, and modernization
+allowed-tools: Read, Glob, Grep, Bash, Agent, Skill, WebSearch, WebFetch
+argument-hint: "<file|directory> [--focus category]"
+---
+
+**IMPORTANT:** Always respond in the same language the user is writing in. If the user writes in Portuguese, respond in Portuguese. If in English, respond in English. Adapt all explanations, error descriptions, and suggestions to the user's language. Code comments may remain in English or match the user's language.
+
+# /advpl-specialist:review
+
+Review ADVPL/TLPP code for best practices, performance, security, and modernization opportunities.
+
+## Usage
+
+```bash
+/advpl-specialist:review <target> [--focus category]
+```
+
+## Focus Categories
+
+| Focus | Description |
+|-------|------------|
+| `boas-praticas` | Best practices: variables, locks, error handling, naming |
+| `performance` | Performance: queries, loops, indexing |
+| `seguranca` | Security: SQL injection, input validation, credentials |
+| `modernizacao` | Modernization: ADVPL→TLPP, legacy patterns |
+| `all` | All categories (default) |
+
+## Process
+
+1. **Parse arguments** - Identify target file(s) and optional `--focus` category
+2. **Load review skill** - Invoke `advpl-code-review` skill and read relevant rules files
+3. **Delegate to code-reviewer agent** - Pass targets and focus to the code-reviewer agent for systematic analysis
+4. **Present findings** - Structured report grouped by severity with actionable fix suggestions
+
+## Examples
+
+```bash
+# Review a single source file (all categories)
+/advpl-specialist:review src/FATA001.prw
+
+# Review an entire directory focusing on performance
+/advpl-specialist:review src/ --focus performance
+
+# Review REST endpoints for security issues
+/advpl-specialist:review src/REST/*.tlpp --focus seguranca
+
+# Review current directory for modernization opportunities
+/advpl-specialist:review . --focus modernizacao
+
+# Review specific files for best practices
+/advpl-specialist:review src/MATA010.prw --focus boas-praticas
+```
+
+## Output
+
+- Findings grouped by file and severity (CRITICAL, WARNING, INFO)
+- Each finding includes: rule ID, file:line reference, current code, suggested fix, and explanation
+- Summary table with counts per category and severity
+- Actionable recommendations prioritized by impact

package/commands/sxgen.md

@@ -0,0 +1,98 @@
+---
+description: Generate Protheus SX data dictionary configuration scripts - SX3 fields, SIX indexes, SX1 questions, SX5 generic tables
+allowed-tools: Read, Write, Glob, Grep, Bash, Agent, Skill
+argument-hint: "[--type sx3|six|sx1|sx5] [--output path]"
+---
+
+**IMPORTANT:** Always respond in the same language the user is writing in. If the user writes in Portuguese, respond in Portuguese. If in English, respond in English.
+
+# /advpl-specialist:sxgen
+
+Generate Protheus data dictionary configuration scripts for SX tables.
+
+## Usage
+
+```bash
+/advpl-specialist:sxgen [options]
+```
+
+Describe what you need in natural language after the command. The agent will parse your description and generate the configuration.
+
+## Options
+
+| Flag | Description | Default |
+|------|------------|---------|
+| `--type` | SX type: `sx3`, `six`, `sx1`, `sx5` | Auto-detect from description |
+| `--output` | Save script to file path | Display in chat |
+
+## Configuration Types
+
+| Type | What it generates |
+|------|-------------------|
+| `sx3` | Field definitions (X3_ARQUIVO, X3_CAMPO, X3_TIPO, etc.) + SX7 triggers |
+| `six` | Index definitions (INDICE, ORDEM, CHAVE, NICKNAME) |
+| `sx1` | Report question definitions (X1_GRUPO, X1_PERGUNT, X1_TIPO) |
+| `sx5` | Generic table entries (X5_TABELA, X5_CHAVE, X5_DESCRI) |
+
+## Auto-Validations
+
+The command automatically:
+- Validates field types and sizes
+- Generates pictures based on type (currency, date, code)
+- Adds NaoVazio() for required fields
+- Adds ExistCpo() for fields with F3 lookup
+- Adds Pertence() for fields with combo options
+- Generates SX7 triggers for F3 lookup fields
+- Includes 3-language support (pt-BR, es, en)
+- Ensures FILIAL is first in indexes
+
+## Process
+
+1. **Parse input** — Identify type and field specifications from natural language
+2. **Load SX configuration skill** — Invoke `sx-configuration` skill
+3. **Delegate to sx-configurator agent** — Pass parsed requirements
+4. **Validate** — Check types, sizes, pictures, validations
+5. **Generate script** — Formatted key-value blocks with all fields
+6. **Deliver** — Display or save to output file
+
+## Examples
+
+```bash
+# Generate SX3 field definitions from description
+/advpl-specialist:sxgen --type sx3
+Criar campos para tabela ZA1 - Ordens de Servico:
+- ZA1_CODIGO: codigo da OS, char 6, obrigatorio
+- ZA1_DESCRI: descricao do servico, char 40, obrigatorio
+- ZA1_CLIENT: codigo do cliente, char 6, valida na SA1
+- ZA1_STATUS: status, char 1, combo 1=Aberta;2=Em Andamento;3=Concluida;4=Cancelada
+
+# Generate SIX index definitions
+/advpl-specialist:sxgen --type six
+Indices para ZA1:
+- Indice 1: filial + codigo (unico)
+- Indice 2: filial + cliente + data abertura
+
+# Generate SX1 report questions
+/advpl-specialist:sxgen --type sx1
+Perguntas para relatorio de OS (grupo ZA1):
+- Data abertura de/ate
+- Status de/ate
+- Cliente de/ate
+
+# Generate SX5 generic table
+/advpl-specialist:sxgen --type sx5
+Tabela generica ZZ para tipos de servico:
+01=Preventiva, 02=Corretiva, 03=Instalacao
+
+# Save to file
+/advpl-specialist:sxgen --type sx3 --output config/ZA1-campos.txt
+```
+
+## Output
+
+Formatted configuration script with:
+- Header with table name, date, and generator info
+- Complete field definitions with all required attributes
+- Auto-generated validations and pictures
+- SX7 triggers (for SX3 with F3 lookups)
+- Ready for manual input in Configurador or reference for APSDU/UPDDISTR import

package/commands/test.md

@@ -0,0 +1,103 @@
+---
+description: Generate ProBat unit tests for TLPP classes and functions
+allowed-tools: Read, Write, Edit, Glob, Grep, Bash, Agent, Skill, WebSearch, WebFetch
+argument-hint: "<file.tlpp|function> [--type unit|api] [--output path]"
+---
+
+# /advpl-specialist:test
+
+**IMPORTANT:** Always respond in the same language the user is writing in. If the user writes in Portuguese, respond in Portuguese. If in English, respond in English. Adapt all explanations and suggestions to the user's language. Code comments may remain in English or match the user's language.
+
+Generate ProBat unit tests for TLPP classes and functions on TOTVS Protheus.
+
+## Usage
+
+```bash
+/advpl-specialist:test <target> [options]
+```
+
+Where `<target>` is a `.tlpp` file path or a function/class name.
+
+## Types
+
+| Type | Description | Output |
+|------|------------|--------|
+| `unit` | Unit test for functions or class methods | `.tlpp` file with `@TestFixture` and assertions |
+| `api` | REST API endpoint test | `.tlpp` file using `tlpp.rest.runTestSimple` |
+
+## Options
+
+| Flag | Description | Default |
+|------|------------|---------|
+| `--type` | Test type: `unit` or `api` | `unit` |
+| `--output` | Output file path | `test/unit/test_<name>.tlpp` |
+| `--suite` | Suite name for grouped execution | None |
+| `--owner` | Team/author identifier for `@TestFixture` | Ask user |
+
+## Important: ProBat is TLPP Only
+
+ProBat only works with TLPP (`.tlpp` files). If a `.prw` file is passed:
+
+1. Inform the user that ProBat requires TLPP
+2. Suggest using `/advpl-specialist:migrate` first to convert the source to TLPP
+3. The test file itself is always `.tlpp`, even when testing ADVPL functions
+
+## Process
+
+1. **Parse arguments** - Extract target file/function, type, and flags
+2. **Read target source** - Analyze the file or function to understand what to test
+3. **Load skill** - Invoke `probat-testing` skill
+4. **Load patterns** - Read `patterns-unit-tests.md` for the appropriate template
+5. **Identify test cases** - Determine:
+   - Functions/methods to test
+   - Input parameters and expected outputs
+   - Edge cases (NIL values, empty strings, invalid types, boundary values)
+   - Error scenarios
+6. **Present plan** - Show the user:
+   - Test file name and path
+   - Test class/function name
+   - List of test methods with descriptions
+   - Assertions to be used
+   - Setup/TearDown needs (if any)
+7. **Wait for approval** - The user must approve before generating code
+8. **Generate test code** - Create the `.tlpp` test file following ProBat conventions:
+   - `#include "tlpp-probat.th"` (and `"tlpp-core.th"` if needed)
+   - Proper namespace (`test.<module>` or `custom.tests.<module>`)
+   - `@TestFixture` with `owner` and `target` properties
+   - `@Test` with descriptive mandatory descriptions
+   - Typed variable declarations
+   - Appropriate assertions from the ProBat assertion library
+9. **Write file** - Save with `.tlpp` extension
+10. **Report** - Show what was created and how to run the tests
+
+## Examples
+
+```bash
+# Generate unit tests for a TLPP file
+/advpl-specialist:test src/calculadora.tlpp
+
+# Generate API tests for a REST endpoint
+/advpl-specialist:test src/customer_api.tlpp --type api
+
+# Generate tests with a specific output path
+/advpl-specialist:test src/pedido_service.tlpp --output test/unit/test_pedido.tlpp
+
+# Generate tests for a specific function
+/advpl-specialist:test U_calculateTotal --type unit
+
+# Generate tests grouped in a suite
+/advpl-specialist:test src/financeiro/ --suite financeiro
+```
+
+## Output
+
+A complete, compilable `.tlpp` test file saved to the project with:
+
+- `#include "tlpp-probat.th"` header
+- Proper namespace declaration
+- `@TestFixture` with owner and target metadata
+- Test methods with `@Test` annotations and descriptive names
+- Typed local variables
+- Appropriate assertions (`assertEquals`, `assertTrue`, etc.)
+- Setup/TearDown methods when needed (`@OneTimeSetUp`, `@Setup`, `@TearDown`, `@OneTimeTearDown`)
+- Return `.T.` from all test functions/methods

package/dist/index.d.ts

@@ -0,0 +1,2 @@
+export {};
+//# sourceMappingURL=index.d.ts.map

package/dist/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":""}