delphi-spec-kit

🚀 Delphi AI Spec-Kit

An opinionated ecosystem of rules, skills and steerings to elevate Delphi development to state-of-the-art with Artificial Intelligence.

Sponsorship

Delphi/Lazarus components <www.inovefast.com.br>

Integrations with payment platforms and services (Asaas, MercadoPago, Cielo, PagSeguro, D4sign, Webstore, MelhorEnvio, Groq)

i9DBTools <www.inovefast.com.br/i9dbTools/> Manage MySQL, PostgreSQL, Firebird and SQLite in one place, with AI to generate and explain SQL in natural language, optimize queries and create Brazilian fake data in seconds.

📋 Index

• What is this project?
• Why use?
• Supported AI-Tools
• Main Guidelines
• Supported Frameworks
• Kit Structure
• Quick Start
• Code Examples
• Contributions

💡 What is this project?

The Delphi AI Spec-Kit is not a code framework — it's a set of behavior guidelines for your favorite AI. It "teaches" the wizard to write Delphi code:

• ✅ Clean — no god classes, no business logic in OnClick
• ✅ Secure — zero memory leaks with try..finally and (ARC) interfaces
• ✅ Testable — TDD with DUnitX, Fakes via interface, without real bench in tests
• ✅ Architected — SOLID, DDD, Repository/Service Pattern and clean architecture

Say goodbye to AI that mixes database access with the presentation layer, forgets try..finally or ignores Dependency Injection.

🤔 Why use it?

🤖 Supported AI Tools

🌟 Key Guidelines Taught to AI

🧠 Memory Management Zero-Leak

The AI ​​enforces the pattern: every .Create without Owner requires try..finally on the immediately subsequent line. Also teaches the use of Interfaces (ARC) for native Garbage Collection — without Free manual.

//✅ Gold Standard — ALWAYS generated by AI with Spec-Kit
var LList: TStringList;
begin
  LList := TStringList.Create;
  try
    LList.Add('item');
  finally
    LList.Free;
  end;
end;

🧪 TDD with DUnitX

Red-Green-Refactor flow with Fakes isolated per interface. No coupling to the database in tests.

[Test]
procedure ProcessOrder_WithoutStock_RaisesException;
begin
  Assert.WillRaise(
    procedure begin FSut.Process(FEmptyOrder); end,
    EInvalidOrderException
  );
end;

🏛️ SOLID and DDD

• S — One class, one responsibility. TCustomerValidator does not save to the bank.
• O — Extension via interfaces, without modifying existing code.
• L — Inheritance only with a clear contract. Preferred interfaces.
• I — Small and specific interfaces. Avoid giant interfaces.
• D — Dependency injection in the constructor, never hardcoded concrete instances.

//✅ DIP in practice
constructor TOrderService.Create(
  ARepo: IOrderRepository;
  ANotifier: INotificationService);
begin
  FRepo := ARepo;
  FNotifier := ANotifier;
end;

📖 Clean Code — Pascal Guide

Consistent and mandatory nomenclatures:

🛠️ Supported Frameworks and Libraries

📂 Kit Structure