Skip to content
Back to search

delphi-dev

MarketplaceWorks with Claude CodeGitHub

Delphi development expert plugin for Claude Code — automatically applies Delphi Style Guide, Clean Code and SOLID patterns

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/adrianosantostreina--delphi-dev/badge.svg)](/listings/adrianosantostreina--delphi-dev)

HTML

<a href="/listings/adrianosantostreina--delphi-dev"><img src="/api/listings/adrianosantostreina--delphi-dev/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

npx delphi-dev

This single command: - Installs the Claude Code plugin - Downloads the RAG knowledge base - Installs the VS Code extension (if VS Code is detected) - Removes any stale automation hooks left by older versions

**Requirements:** Node.js 18+, Claude Code CLI, git

> **Automation hooks are disabled since v2.2.2.** They depended on native modules > that broke clean installs on Windows. The knowledge base still ships and the > skills, commands and agents all work — what is currently off is the automatic > per-prompt knowledge injection and session capture. They return with the local > MCP server. **Do not register them by hand:** on v3.0.0 and earlier the capture > path writes session noise into the index tagged as authoritative.

> **Nothing to do about the knowledge base right now.** The curated corpus ships as > `rag.db` on each release and `npx delphi-dev` downloads it for you. It is currently > **read by nothing**, because the only consumer is the per-prompt injection hook, which > is off — so an install without it behaves identically. When the local MCP server lands, > `npx delphi-dev update` will bring both the corpus and the code that reads it.

Update

npx delphi-dev update

Verify installation

npx delphi-dev verify

Clean reinstall (upgrading from v1.x)

If you already had an old version (v1.x) installed and want to move to the new version from scratch, **first remove the old installation inside Claude Code**, then reinstall.

**1. Remove the old version** — commands run inside Claude Code:

/plugin list                            # see what is installed
/plugin uninstall delphi-dev@delphi-dev # uninstall the plugin
/plugin marketplace remove delphi-dev   # remove the old marketplace

> Removing the marketplace also uninstalls plugins that came from it. Short forms `/plugin market` and `rm` are accepted.

**2. (Optional) clear the plugin cache** if anything gets stuck:

rm -rf ~/.claude/plugins/cache

**3. Clean install** — in the terminal:

npx delphi-dev

**4. Reload** — restart Claude Code or run `/reload-plugins` to load the new version.

Local install (development / testing)

To test from a local checkout of the repository — useful when developing the plugin itself:

/plugin marketplace add <checkout-path>
/plugin install delphi-dev@delphi-dev

Changes to `.md` / `.json` files only take effect after reinstalling. To repeat the test cycle from a clean state, uninstall and re-add:

/plugin uninstall delphi-dev@delphi-dev
/plugin marketplace remove delphi-dev
/plugin marketplace add <checkout-path>
/plugin install delphi-dev@delphi-dev

---

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 41 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "name": "delphi-dev",
  3. "owner": {
  4. "name": "Adriano Santos",
  5. "email": "adrianosantospro@gmail.com"
  6. },
  7. "metadata": {
  8. "description": "Delphi development expert for Claude Code — applies Delphi Style Guide, Clean Code, and SOLID patterns automatically."
  9. },
  10. "plugins": [
  11. {
  12. "name": "delphi-dev",
  13. "source": {
  14. "source": "url",
  15. "url": "https://github.com/adrianosantostreina/delphi-dev.git"
  16. },
  17. "description": "Delphi development expert for Claude Code. Automatically applies Delphi Style Guide, Clean Code principles, and SOLID patterns. Includes technical audit, code review, standardized code writing, project scaffolding, build validation, and RAG-powered knowledge base.",
  18. "version": "3.2.1",
  19. "author": {
  20. "name": "Adriano Santos",
  21. "email": "adrianosantospro@gmail.com"
  22. },
  23. "homepage": "https://github.com/adrianosantostreina/delphi-dev",
  24. "repository": "https://github.com/adrianosantostreina/delphi-dev",
  25. "license": "MIT",
  26. "keywords": [
  27. "delphi",
  28. "object-pascal",
  29. "clean-code",
  30. "style-guide",
  31. "code-review",
  32. "audit",
  33. "firemonkey",
  34. "vcl",
  35. "firedac",
  36. "rad-studio"
  37. ],
  38. "category": "development"
  39. }
  40. ]
  41. }
README.md · README · 293 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # delphi-dev — Claude Code Plugin
  2. > A Claude Code plugin that turns the assistant into a senior Delphi expert.
  3. > 🇧🇷 [Leia em Português](README.pt-BR.md)
  4. ---
  5. ## What is it
  6. **delphi-dev** activates automatically whenever Claude Code detects Delphi-related content — `.pas`, `.dpr`, `.dfm`, `.dpk`, `.dproj` files, or any mention of Object Pascal, FireMonkey, VCL, FireDAC, or RAD Studio. Once active, Claude applies the full Delphi Style Guide, Clean Code principles, and SOLID patterns without being asked.
  7. ---
  8. ## Features
  9. | Command | Description |
  10. |---|---|
  11. | **Auto Delphi Mode** | Opening any `.pas`, `.dpr` or `.dfm` file activates the full coding standards context automatically |
  12. | **`/audit`** | Generates a complete professional technical audit with per-dimension scoring and a prioritized modernization roadmap |
  13. | **`/review`** | Quick code review — detects violations and provides corrected examples |
  14. | **`/write`** | Writes new code with all standards applied from the start |
  15. | **`/new-project`** | Scaffolds a new project with standardized layered folder structure |
  16. | **`/spec`** | Analyzes the current project source code and auto-generates a complete `SPEC.md` |
  17. | **`/tdd`** | Generates a complete DUnitX unit test suite for the project |
  18. | **`/e2e`** | Runs end-to-end scenarios against a running Delphi desktop app — builds it, opens the `.exe`, drives the screens and reports a verdict per scenario |
  19. | **`/contribute-kb`** | Packages local learnings captured by the hooks and opens a PR to the community knowledge base *(needs hooks, currently disabled — see Installation)* |
  20. | **`/dashboard`** | Displays GitHub repository metrics — stars, forks, issues, PRs, commits, releases, contributors |
  21. | **`/about`** | Displays plugin info, version, and available commands |
  22. ---
  23. ## End-to-end testing with `/e2e` <sub>new in 3.2.0</sub>
  24. Think of it as **Playwright for Delphi desktop apps**. You describe test scenarios in plain
  25. language; the plugin builds the project, opens the `.exe`, drives the real screens, and returns
  26. a **verdict per scenario** — correlated with your app's log.
  27. ```
  28. /e2e login: blank password, wrong password, correct password
  29. ```
  30. Without arguments, `/e2e` derives an "opens without error" scenario for each screen of the
  31. main menu.
  32. ### Four verdicts, not two
  33. The distinction is what separates a useful report from noise:
  34. | Verdict | Meaning |
  35. |---|---|
  36. | ✅ PASS | Ran and matched the expectation |
  37. | ❌ FAIL | Ran and diverged — **the app is wrong** |
  38. | ⛔ BLOCKED | Couldn't run — **I don't know whether the app is wrong** |
  39. | ⏭️ SKIPPED | Writes data and wasn't authorized at the gate |
  40. A report that blames a bug where there was only state contamination is worse than no report.
  41. So when a scenario can't be returned to its starting point, it comes back **⛔ BLOCKED, never
  42. ❌ FAIL**.
  43. ### It never steals focus
  44. Clicks go through `PostMessage`, text through `WM_CHAR`, screenshots through `PrintWindow` —
  45. so the plugin **never grabs your keyboard and never moves your cursor**. Screenshots work even
  46. with the window fully covered, and `WM_CHAR` is immune to the dead-key problem of ABNT
  47. keyboards that breaks `SendKeys`.
  48. By default the app runs in the foreground so you can watch. Pass `--background` and it runs
  49. behind your other windows without interrupting you.
  50. ### It stops and asks before touching your data
  51. Before the first click, `/e2e` presents the scenarios it intends to run, **which ones write
  52. data and what they write**, and waits. It never writes on its own initiative — it explores,
  53. captures, and leaves through Cancel/Back.
  54. ### It reads your app's log
  55. Delivery is not effect: a message can reach the window and still do nothing if the control
  56. isn't in the expected state. That's why `/e2e` reads your log in parallel — it's the difference
  57. between ⛔ BLOCKED and ❌ FAIL. If your app has no log, the plugin **offers** (never imposes)
  58. either a minimal logging unit or a headless `--selftest` mode, and generates it following the
  59. plugin's own coding standards.
  60. > **Requirements:** Windows, and RAD Studio for the build step. FireMonkey is validated;
  61. > VCL is a declared fallback. Android is out of scope by design.
  62. ---
  63. ## Installation
  64. ```bash
  65. npx delphi-dev
  66. ```
  67. This single command:
  68. - Installs the Claude Code plugin
  69. - Downloads the RAG knowledge base
  70. - Installs the VS Code extension (if VS Code is detected)
  71. - Removes any stale automation hooks left by older versions
  72. **Requirements:** Node.js 18+, Claude Code CLI, git
  73. > **Automation hooks are disabled since v2.2.2.** They depended on native modules
  74. > that broke clean installs on Windows. The knowledge base still ships and the
  75. > skills, commands and agents all work — what is currently off is the automatic
  76. > per-prompt knowledge injection and session capture. They return with the local
  77. > MCP server. **Do not register them by hand:** on v3.0.0 and earlier the capture
  78. > path writes session noise into the index tagged as authoritative.
  79. > **Nothing to do about the knowledge base right now.** The curated corpus ships as
  80. > `rag.db` on each release and `npx delphi-dev` downloads it for you. It is currently
  81. > **read by nothing**, because the only consumer is the per-prompt injection hook, which
  82. > is off — so an install without it behaves identically. When the local MCP server lands,
  83. > `npx delphi-dev update` will bring both the corpus and the code that reads it.
  84. ### Update
  85. ```bash
  86. npx delphi-dev update
  87. ```
  88. ### Verify installation
  89. ```bash
  90. npx delphi-dev verify
  91. ```
  92. ### Clean reinstall (upgrading from v1.x)
  93. If you already had an old version (v1.x) installed and want to move to the new version from scratch, **first remove the old installation inside Claude Code**, then reinstall.
  94. **1. Remove the old version** — commands run inside Claude Code:
  95. ```text
  96. /plugin list # see what is installed
  97. /plugin uninstall delphi-dev@delphi-dev # uninstall the plugin
  98. /plugin marketplace remove delphi-dev # remove the old marketplace
  99. ```
  100. > Removing the marketplace also uninstalls plugins that came from it. Short forms `/plugin market` and `rm` are accepted.
  101. **2. (Optional) clear the plugin cache** if anything gets stuck:
  102. ```bash
  103. rm -rf ~/.claude/plugins/cache
  104. ```
  105. **3. Clean install** — in the terminal:
  106. ```bash
  107. npx delphi-dev
  108. ```
  109. **4. Reload** — restart Claude Code or run `/reload-plugins` to load the new version.
  110. #### Local install (development / testing)
  111. To test from a local checkout of the repository — useful when developing the plugin itself:
  112. ```text
  113. /plugin marketplace add <checkout-path>
  114. /plugin install delphi-dev@delphi-dev
  115. ```
  116. Changes to `.md` / `.json` files only take effect after reinstalling. To repeat the test cycle from a clean state, uninstall and re-add:
  117. ```text
  118. /plugin uninstall delphi-dev@delphi-dev
  119. /plugin marketplace remove delphi-dev
  120. /plugin marketplace add <checkout-path>
  121. /plugin install delphi-dev@delphi-dev
  122. ```
  123. ---
  124. ## Output Language
  125. **delphi-dev** supports both **pt-BR** (default) and **en-US** for everything it shows you — audit reports, SPEC documents, code reviews, prompts, and notifications.
  126. The plugin auto-detects the language of your **first message** in a session and responds in that language. You can switch any time with an explicit override:
  127. - `respond in English` / `in English please` / `switch to English` → en-US
  128. - `responda em português` / `em português por favor` → pt-BR
  129. What changes with the language selection:
  130. - **Report templates** — `/audit` loads `estrutura-laudo.en.md` for English, `estrutura-laudo.md` for Portuguese; `/spec` does the same with `spec-template[.en].md`.
  131. - **Severity / classification labels** — e.g. `🟢 GOOD / 🟡 FAIR / 🟠 CRITICAL / 🔴 NOT VIABLE` (en-US) vs. `🟢 BOM / 🟡 REGULAR / 🟠 CRÍTICO / 🔴 INVIÁVEL` (pt-BR).
  132. - **Notifications** — e.g. `✅ Tests created in TestePedidoService.pas — 7 test cases` vs. the pt-BR equivalent.
  133. - **All explanatory prose** in `/review`, `/write`, `/new-project`, `/tdd`, and `/about`.
  134. What does **not** change with language:
  135. - **Delphi identifiers in example code** (`FNome`, `ACliente`, `BuscarPorCodigo`) — these illustrate the naming convention itself.
  136. - **Code prefixes** (`F`, `A`, `L`, `C_`, `T`, `I`, `E`).
  137. - **Test method names** (`Test_<Method>_<Scenario>`).
  138. - **Requirement IDs in SPECs** (`RF-001`, `RNF-001`, `RN-001`, `UC-001`).
  139. ---
  140. ## Standards Applied Automatically
  141. ### Prefixes
  142. - `F` — fields (private attributes)
  143. - `A` — method parameters
  144. - `L` — local variables
  145. - `C_` — constants (+ UPPER_CASE body)
  146. - `T` — classes and types
  147. - `I` — interfaces
  148. - `E` — exceptions
  149. ### Formatting
  150. - ✅ 2-space indentation (no tabs)
  151. - ✅ 120-character line limit
  152. - ✅ `begin` and `else` on their own lines
  153. - ✅ One variable per line
  154. - ✅ One unit per line in `uses` clause (RTL → VCL/FMX → FireDAC → Third-party → Project)
  155. ### Prohibited Commands
  156. - ❌ `with` — causes ambiguity and debugging issues
  157. - ❌ `Break` / `Continue` — use loop conditions instead
  158. - ❌ `Real` — use `Double` or `Currency`
  159. - ⚠️ `Exit` — allowed only as guard clauses at the top of a method
  160. ### Safety Rules
  161. - ✅ One resource per `try..finally` block
  162. - ✅ No empty `except` blocks
  163. - ✅ SQL always parameterized (no string concatenation)
  164. - ✅ `const` never applied to interface parameters (ARC compatibility)
  165. - ✅ No global variables — use `class var` instead
  166. ### Component Prefixes (VCL / FMX)
  167. `btn`, `edt`, `lbl`, `mmo`, `cbx`, `grd`, `qry`, `cnn`, `dts`, `pnl`, `tmr`, and more — see [`skills/delphi-standards/references/component-prefixes.md`](skills/delphi-standards/references/component-prefixes.md)
  168. ---
  169. ## Included Skills
  170. | Skill | Activation |
  171. |---|---|
  172. | `delphi-standards` | Auto-activated on Delphi file/code detection |
  173. | `delphi-write` | Activated when writing new Delphi code |
  174. | `delphi-laudo` | Activated by the `/audit` command |
  175. | `delphi-spec` | Activated by the `/spec` command |
  176. | `delphi-tests` | Activated by the `/tdd` command or automatically after `delphi-write` |
  177. | `delphi-claudeignore` | Auto-activated on Delphi project detection to optimize token usage |
  178. | `delphi-encoding` | Auto-activated on encoding/BOM/mojibake issues in Delphi files |
  179. | `delphi-fmx` | Auto-activated for FireMonkey and Android/iOS mobile development |
  180. | `delphi-firedac` | Auto-activated for FireDAC data-access code |
  181. | `delphi-acbr` | Auto-activated for ACBr fiscal components (NFe/NFCe/boleto) |
  182. | `delphi-async` | Auto-activated for async/threading (TTask, TThread, Synchronize) |
  183. | `delphi-build` | Auto-activated for command-line build/compilation and build errors |
  184. | `delphi-spring4d` | Auto-activated for Spring4D DI container and collections |
  185. | `delphi-legacy` | Auto-activated for legacy code modernization/migration |
  186. | `delphi-e2e` | Activated by the `/e2e` command — Windows only |
  187. ---
  188. ## Included Agents
  189. | Agent | Purpose |
  190. |---|---|
  191. | `delphi-auditor` | Deep technical audit — 8 dimensions, scoring, 17-section report |
  192. | `delphi-writer` | Writes complete, production-ready Delphi code following all standards |
  193. | `delphi-spec-writer` | Generates the SPEC document from source code analysis |
  194. | `delphi-tester` | Creates DUnitX unit test suites for Delphi classes |
  195. ---
  196. ## Roadmap
  197. See [ROADMAP.md](ROADMAP.md) for what is planned and how to influence priorities. Phases under discussion include automatic encoding handling (UTF-8/BOM), mobile FMX scaffolding, Spring4D dependency injection, and a build/validation pipeline that lets Claude actually compile and verify the code it generates.
  198. ---
  199. ## Based on
  200. - *Delphi Coding Standards v4.0.1* — Adriano Santos
  201. - *Clean Code and Best Practices in Delphi* — Adriano Santos
  202. - *Clean Code* — Robert C. Martin
  203. - *Delphi Style Guide* — Embarcadero
  204. ---
  205. ## License
  206. MIT © 2026 Adriano Santos
  207. ---
  208. ## Privacy Policy
  209. [View Privacy Policy](privacy-policy.md)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.