Community resource: verified AI skill for EasyAdmin 5

[jupaygon]

Hi Javier,

I've created a verified API reference for EasyAdmin 5, optimized for AI coding agents (Claude Code, Cursor, etc.): jupaygon/ai-skills

The problem it solves: AI agents generate code using the EA4 API (linkToCrud, addPanel, displayAsLink...) because their training data doesn't include the EA5 changes. The skill gives them the correct information before generating code.

What it covers: EA4→EA5 breaking changes, full dashboard API, menus, CRUD controllers, all 30 field types, actions, filters, events, security, pretty URLs, and design customization. ~930 verified lines checked against the bundle's source code.

Verification process: multiple cross-review rounds between humans and different AI agents, checking every signature and every parameter against the 5.x branch source code.

It's open source (MIT), a single Markdown file with no dependencies. Sharing it in case you find it useful or want to reference it from the official documentation.

Best regards,
Juanjo Payá

[raye-deng]

Juanjo, this is exactly the problem we've been running into with AI-generated code.

We built Open Code Review partly because we kept seeing projects suffer from exactly this issue — AI agents generating code using APIs that either don't exist or have been deprecated in newer versions. The tricky part is that these issues often pass all traditional quality gates:

• TypeScript compilation succeeds (because the types look correct)
• Unit tests pass (because the deprecated import paths aren't exercised)
• Static analysis tools like SonarQube don't catch version-specific API usage

In our experience, these "silent API failures" are more common than you'd think. We've seen cases where:

1. AI suggests @symfony/ux-turbo which doesn't exist (only @symfony/ux-turbo-bridge)
2. AI recommends outdated field types that were removed between Symfony 4 and 5
3. AI imports components that were deprecated but not removed until the major version after

Your approach of creating a verified API reference is spot-on. We've found that the most effective solution is a combination of:

1. Registry validation (checking packages actually exist on npm)
2. Version-specific API usage detection
3. Breaking change awareness between major versions

Happy to share more details about what's been working for us if that'd be useful.