skills.rest
cslsoftwares
cslsoftwaresCOMMUNITY
Explore all skills by this author →
GitHub

developer-delphi-programming-oop-naming

Enforce Delphi OOP naming conventions for modules, interfaces, and builders.

Updated Jan 6, 2026
Search Tags:#modules#oop#naming#builders#delphi
One-click install
npx skills add https://github.com/cslsoftwares/ParamentersORM --skill developer-delphi-programming-oop-naming
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: developer-delphi-programming-oop-naming
Source: https://github.com/cslsoftwares/ParamentersORM/tree/main/.cursor/skills/developer-delphi-programming-oop-naming_V1.0.0
Command: npx skills add https://github.com/cslsoftwares/ParamentersORM --skill developer-delphi-programming-oop-naming

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This policy standardizes Delphi OOP naming for modules, interfaces, and builders to improve readability and maintainability across backend and ORM code.

Core Features & Use Cases

  • Hierarchy rules: master module naming IModulo / TModulo and submodule naming IModuloSubclasse / TModuloSubclasse, plus fluent builder interfaces IOperacaoBuilder / TOperacaoBuilder.
  • Commons and Controllers conventions: ensure modules in Commons start with Commons., and Controllers use the Controller suffix (not EntryPoint) for all entry points.
  • Canonical file naming and factory patterns: aligns with the canonical MXX naming rules, explicit interface/class pairings, and standard Factory/Builder patterns.

Quick Start

Apply the two-level OOP naming convention across all Delphi modules and interfaces to standardize TModulo/IModulo and TModuloSubclasse patterns.

Frequently Asked Questions about developer-delphi-programming-oop-naming

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce Delphi OOP naming conventions for modules and interfaces?▼

To enforce Delphi OOP naming, apply a two-level hierarchy: name master modules IModulo / TModulo and submodules IModuloSubclasse / TModuloSubclasse, while using fluent builder interfaces like IOperacaoBuilder / TOperacaoBuilder for consistent class structures.

What is the correct Delphi naming convention for Controllers and Commons modules?▼

The correct Delphi naming convention requires Controllers to use the Controller suffix instead of EntryPoint, and modules in Commons must start with the Commons. prefix to maintain consistent project structure across backend and ORM code.

How do I structure fluent builder interfaces in Delphi backend projects?▼

To structure fluent builder interfaces in Delphi backend projects, use the IOperacaoBuilder / TOperacaoBuilder pattern, pairing explicit interfaces with standard Factory and Builder classes to align with canonical MXX file naming rules.

Can I use this naming convention for Delphi ORM modules?▼

Yes, you can use this naming convention for Delphi ORM modules, as it is specifically applied to backend Delphi projects and ORM modules to govern master/submodule naming and factory/builder patterns.

Why should I use the Controller suffix instead of EntryPoint for Delphi modules?▼

You should use the Controller suffix instead of EntryPoint because the Delphi OOP naming policy standardizes all entry points with the Controller suffix, ensuring readability and maintainability across backend code.

Related Skills

Explore More Software Engineering Skills→
cslsoftwarescslsoftwares

documentation-project-expert

Enforce Delphi/Free Pascal ORM naming and module conventions across FireDAC, UniDAC, Zeos, and SQLdb.

Community
Advanced
VoDaiLoczVoDaiLocz
24

lint-and-validate

Automate linting and static analysis of code in CI pipelines.

Community
Intermediate
cslsoftwarescslsoftwares

developer-delphi-architecture-and-design

Define modular architecture boundaries and interface contracts for Delphi/FPC projects.

Community
Advanced
yanhaoluo0yanhaoluo0
44

java-coding-standards

Enforce Alibaba Java coding standards across Java codebases.

Community
Advanced