powerbuilder-dev

Full PowerBuilder project setup — installs toolkit, generates CLAUDE.md and .mcp.json. Zero manual steps.

Show current PowerBuilder project status — toolkit, MCP connection, project structure, PMIX info, and git status.

Run a full validation of the PowerBuilder project — compile, check conventions, detect dangerous patterns.

Use this agent when you need deep analysis of PowerBuilder objects — exploring inheritance chains, dependency graphs, call graphs, and architecture patterns. Use for questions like "what does w_xxx do?", "who calls function of_xxx?", "what inherits from uo_datawindow?", or "show me the full dependency tree of this object". This agent works autonomously and returns a structured analysis report.

Use this agent to review PowerBuilder code for bugs, bad practices, and potential issues. Use after modifying PB code, or when investigating a suspicious object. It checks for common PB pitfalls — missing SQLCA.SQLCode checks, null object references, missing Destroy statements, incorrect event firing order, DataWindow update issues, and PMIX convention violations.

Use this agent when you need to analyze the impact of modifying a PowerBuilder object, table, or function before making changes. It traces all dependencies, inheritance chains, and cross-references to identify what could break. Use for questions like "si je modifie w_response, quel impact?", "quels objets utilisent la table salhead?". This agent runs autonomously and returns a structured impact report.

Use this agent when you need to research a PMIX ERP question in depth — understanding business processes, finding which tables/windows/DataWindows are involved, or documenting how a feature works end-to-end. Use for questions like "comment fonctionne la facturation?", "quelles tables sont impliquees dans le flux de stock?". This agent searches the RAG knowledge base and cross-references with source code to provide complete answers.

Use when you need to understand existing PowerBuilder code — explore architecture, inheritance, dependencies, and data flow. For deep analysis with a full report, use the pb-analyst agent instead.

Use when creating new PowerBuilder objects (windows, user objects, DataWindows). Ensures proper inheritance and naming conventions.

Use when creating, modifying, or optimizing DataWindows — the central data presentation component in PowerBuilder. Activates for any request involving DW SQL, columns, layout, or properties.

Use when diagnosing bugs, errors, or unexpected behavior in PowerBuilder code. Provides a systematic debugging approach with structured output.

Use when modifying PowerBuilder source code (.srw, .srd, .sru, .srm files). Guides the complete workflow from reading to compilation. MUST be used for any PB code change.