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

documentation-project-expert

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

Updated Jan 6, 2026
Search Tags:#architecture#documentation#orm#conventions#delphi#freepascal#analise
One-click install
npx skills add https://github.com/cslsoftwares/ParamentersORM --skill documentation-project-expert
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: documentation-project-expert
Source: https://github.com/cslsoftwares/ParamentersORM/tree/main/.cursor/skills/documentation-project-expert_V1.0.0
Command: npx skills add https://github.com/cslsoftwares/ParamentersORM --skill documentation-project-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides the authoritative single source of truth for the project’s v2.0 ORM conventions in Delphi/Free Pascal, ensuring consistent architecture, naming, and organizational rules across modules.

Core Features & Use Cases

  • Centralized conventions: defines mandatory naming (I* / T*) and the ORM module hierarchy (Connection, PoolConnections, Database, Exceptions, Parameters, Loggers) to unify all contributions.
  • Multi-engine alignment: guides conventions across FireDAC, UniDAC, Zeos, and SQLdb to support multi-engine integrations.
  • Documentation-driven governance: anchors standards in Analise and related planning/docs to drive implementation and code reviews.
  • Use Case: when adding or refactoring ORM components, consult this standard to ensure consistent naming, encapsulation, and module boundaries.

Quick Start

Review Analise guidelines and apply the v2.0 ORM conventions to any new Delphi/Free Pascal ORM module.

Frequently Asked Questions about documentation-project-expert

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

FAQPage Schema
How do I standardize ORM naming conventions across Delphi and Free Pascal projects?▼

To standardize ORM naming conventions in Delphi and Free Pascal, enforce mandatory I* and T* interface and class prefixes, ensuring unified module architecture across all project contributions.

What is the required module hierarchy for a Delphi Free Pascal ORM architecture?▼

The required ORM module hierarchy includes Connection, PoolConnections, Database, Exceptions, Parameters, and Loggers modules, establishing a single source of truth for architectural boundaries.

Can I use these ORM conventions with FireDAC, UniDAC, Zeos, and SQLdb simultaneously?▼

Yes, the ORM conventions explicitly support multi-engine alignment across FireDAC, UniDAC, Zeos, and SQLdb, guiding consistent integration and encapsulation rules for each database engine.

How to align ORM code reviews with project documentation in Free Pascal?▼

Align ORM code reviews with documentation by anchoring standards in Analise and related planning docs, driving implementation validation and ensuring naming patterns match v2.0 conventions.

When should I consult the single source of truth for Delphi ORM refactoring?▼

Consult the single source of truth whenever adding or refactoring Delphi or Free Pascal ORM components, ensuring consistent encapsulation, naming, and module boundaries during v2.0 upgrades.

Related Skills

Explore More Content & Communication Skills→
cslsoftwarescslsoftwares

documentation-class-analysis-generator

Generate structured Markdown documentation for classes and interfaces from source code.

Community
Advanced
cslsoftwarescslsoftwares

developer-delphi-programming-oop-naming

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

Community
Intermediate
cslsoftwarescslsoftwares

developer-delphi-programming-conditional-defines

Configure Delphi and Free Pascal conditional compilation directives for engines and modules.

Community
Advanced
gridacogridaco
2.6k

naming

Identify naming drift and propose strict names for code modules and packages.

Official
Intermediate