Skip to content
Back to skills

Gestor Module Integration

ASecurity

Use when creating, fixing, reviewing, or refactoring gestor modules in Conn2Flow private projects. Especially when there is risk of forgetting modulo-id, JSON, the *_start() function, final autorun, switch($_GESTOR["opcao"]), switch($_GESTOR["ajax-opcao"]), resources, hooks, API, or widget integration.

  • 4 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
developmentgophprefactoringapidatabase

Works with

  • api

Security analysis

A100/100

Scanned November 7, 2026

npx -y skills add otavioserra/conn2flow-ai-workspace --skill gestor-module-integration --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Gestor Module Integration?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Gestor Module Integration
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/otavioserra-gestor-module-integration/badge)](https://www.skillsdirectory.com/skills/otavioserra-gestor-module-integration)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: gestor-module-integration
description: Use when creating, fixing, reviewing, or refactoring gestor modules in Conn2Flow private projects. Especially when there is risk of forgetting modulo-id, JSON, the *_start() function, final autorun, switch($_GESTOR["opcao"]), switch($_GESTOR["ajax-opcao"]), resources, hooks, API, or widget integration.
user-invocable: false
---

# Gestor module integration

Use this skill when the task is not only an isolated business rule, but a structural adjustment in a gestor module.

## When to use

- create a new module in `gestor/modulos/`
- fix a module that responds only partially at runtime
- refactor a module with risk of breaking bootstrap, interface, or AJAX
- review a module diff that looks functional in the file, but incomplete inside gestor

## Procedure

1. Reread one simple module and one richer module as references before the first edit.
2. Confirm the module's structural contract: bootstrap, JSON, resources, pages, variables, hook, API, widget, and the `*_start()` function when applicable.
3. If the task touches a hook, API, or widget, include those layers in the reading and diff instead of concluding from the main PHP file alone.
4. After the first substantive edit, validate in the smallest scope capable of falsifying the integration.
5. If structural doubt remains, reread the Conn2Flow core flow that includes the module and closes interface or AJAX before expanding the diff.

## Common snippet mistakes

- do not use `$_REQUEST[$post_nome]` without `isset()` or `empty()`
- confirm that the database call is the correct function (`banco_select`, `banco_update`, etc.)
- confirm PHP strings with `;` and templates with correct tags
- for AJAX, confirm sending `ajaxOpcao` and handling it in `$_GESTOR['ajax-opcao']`
- when using model helpers, verify consistency of `modelo_var_troca`, `modelo_var_troca_tudo`, `modelo_tag_val`, `modelo_tag_troca_val`, `modelo_var_in`, and `modelo_tag_del`

## What this skill prevents

- a module with business functions but no `*_start()`
- a normal branch without `interface_iniciar()` and `interface_finalizar()`
- an AJAX branch without `interface_ajax_iniciar()` and `interface_ajax_finalizar()`
- JSON, pages, or variables inconsistent with the PHP and HTML
- forgotten hooks, API, or widget pieces when the module depends on them

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.