FastAdmin Addon Creator

Problem

FastAdmin addon development can get bogged down in directory layout, addon identifiers, admin controllers, SQL scripts, and packaging rules. Copying examples by hand can miss info.ini, install.sql, config.php, or leave debug files, extra modules, and risky scripts in the final package.

How It Works

The skill centers on scaffolding a plugin from the command line, then checking that the identifier uses lowercase letters and at least three characters. It explains the core files under addons/{plugin}/, including info.ini, {Plugin}.php, and config.php with supported config types. It also covers front-end controller URLs, admin controller locations, and install.sql conventions such as __PREFIX__ replacement, lowercase tables and fields, InnoDB, utf8mb4, related fields ending in _id, Unix timestamp fields as bigint(16) ending in time, and id as the primary key. Packaging guidance includes the output path, cleanup of .addonrc, .DS_Store, and .git, and restrictions on application, public, and assets.

Boundaries And Notes

This is useful for creating a new FastAdmin addon and producing a package that follows its expected structure. If the project already has custom deployment, multi-module architecture, or nonstandard database conventions, the output needs to be adjusted before use. The material does not define business APIs, permission models, or UI component details, so implementers should still refer to the official FastAdmin documentation.