How do I install the Advpl To Tlpp Migration skill?

Run npx skillmds@latest add thalysjuvenal/advpl-to-tlpp-migration in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Advpl To Tlpp Migration safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Advpl To Tlpp Migration?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Advpl To Tlpp Migration free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Advpl To Tlpp Migration?

thalysjuvenal (@thalysjuvenal) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Advpl To Tlpp Migration by thalysjuvenal

Name: Advpl To Tlpp Migration
Author: thalysjuvenal

Advpl To Tlpp Migration

Use when the user asks to migrate, convert, compatibilize, or modernize legacy ADVPL procedural code to TLPP object-oriented classes on TOTVS Protheus -- turning User Functions/Static Functions into namespaced classes with methods and data properties, replacing Private/Public scoping, and preserving backward-compatible wrappers for existing callers. Also triggers on Portuguese phrasing like "migrar para tlpp", "compatibilizar fonte", "converter prw para tlpp", "transformar em classe", "modernizar rotina", or requests naming a `custom.<agrupador>.<servico>` / `totvs.protheus.<segmento>.<agrupador>` namespace.

thalysjuvenal Updated Sep 17, 2026

File contents

ADVPL to TLPP Migration

This skill guides the conversion of legacy .prw procedural code (User Functions, Static Functions, Private/Public variables) into modern .tlpp classes with namespace declarations, data properties, and public/private methods -- following the official TOTVS naming conventions (lowercase dot-separated namespaces, PascalCase classes, camelCase methods, no underscores). It defines the migration workflow (analyze -> identify -> map to class design -> user approval -> generate -> checklist -> validate) and mandates keeping the original .prw User Function as a thin backward-compatible wrapper delegating to the new class.

Activate this skill when the user wants an existing procedural routine converted to TLPP, needs help deciding a namespace, or is modernizing multiple #Include directives to .th includes. It does not cover generating brand-new TLPP code that has no ADVPL predecessor (see advpl-code-generation), behavior-preserving cleanup of code that stays in ADVPL (see advpl-refactoring), auditing code quality before migration (see advpl-code-review), or fixing errors encountered during or after migration (see advpl-debugging).

Reference file	Read when
reference.md	Always -- overview, migration strategy flow, core conversion rules table, TLPP naming conventions, full before/after example, key migration decisions, common mistakes
migration-rules.md	Needing the complete mapping of every ADVPL construct (preprocessor directives, database operations, error handling, UI elements) to its TLPP equivalent
migration-checklist.md	Verifying a completed migration is thorough before declaring it done

---name: advpl-to-tlpp-migrationdescription: Use when the user asks to migrate, convert, compatibilize, or modernize legacy ADVPL procedural code to TLPP object-oriented classes on TOTVS Protheus -- turning User Functions/Static Functions into namespaced classes with methods and data properties, replacing Private/Public scoping, and preserving backward-compatible wrappers for existing callers. Also triggers on Portuguese phrasing like "migrar para tlpp", "compatibilizar fonte", "converter prw para tlpp", "transformar em classe", "modernizar rotina", or requests naming a `custom.<agrupador>.<servico>` / `totvs.protheus.<segmento>.<agrupador>` namespace.---# ADVPL to TLPP MigrationThis skill guides the conversion of legacy `.prw` procedural code (User Functions, Static Functions, Private/Public variables) into modern `.tlpp` classes with `namespace` declarations, `data` properties, and `public`/`private` methods -- following the official TOTVS naming conventions (lowercase dot-separated namespaces, PascalCase classes, camelCase methods, no underscores). It defines the migration workflow (analyze -> identify -> map to class design -> user approval -> generate -> checklist -> validate) and mandates keeping the original `.prw` User Function as a thin backward-compatible wrapper delegating to the new class.Activate this skill when the user wants an existing procedural routine converted to TLPP, needs help deciding a namespace, or is modernizing multiple `#Include` directives to `.th` includes. It does not cover generating brand-new TLPP code that has no ADVPL predecessor (see `advpl-code-generation`), behavior-preserving cleanup of code that stays in ADVPL (see `advpl-refactoring`), auditing code quality before migration (see `advpl-code-review`), or fixing errors encountered during or after migration (see `advpl-debugging`).| Reference file | Read when ||---|---|| reference.md | Always -- overview, migration strategy flow, core conversion rules table, TLPP naming conventions, full before/after example, key migration decisions, common mistakes || migration-rules.md | Needing the complete mapping of every ADVPL construct (preprocessor directives, database operations, error handling, UI elements) to its TLPP equivalent || migration-checklist.md | Verifying a completed migration is thorough before declaring it done |

Frequently asked questions