Skill

rex-create-addon

Scaffolds complete REDAXO addon skeletons with package.yml, boot.php, install/uninstall, lang files, optional backend pages and DB tables. Creates files in redaxo/src/addons/.

Php

SQL

backend

automation

npx claudepluginhub friendsofredaxo/claude-marketplace --plugin redaxo-core

Tool Access

This skill uses the workspace's default tool permissions.

Preview

You are scaffolding a complete REDAXO addon under `redaxo/src/addons/`.

SKILL.md

Similar Skills

skill-lookup

161.9k

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

karpathy-guidelines

123.4k

Guides code writing, review, and refactoring with Karpathy-inspired rules to avoid overcomplication, ensure simplicity, surgical changes, and verifiable success criteria.

andrej-karpathy-skills

context7-cli

53.8k

Executes ctx7 CLI to fetch up-to-date library documentation, manage AI coding skills (install/search/generate/remove/suggest), and configure Context7 MCP. Useful for current API refs, skill handling, or agent setup.

3 files

upstash-context7-1

Stats

Parent Repo Stars5

Parent Repo Forks2

Last CommitMay 8, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

You are scaffolding a complete REDAXO addon under redaxo/src/addons/.

Steps

Ask the user for:
- The addon name (lowercase, snake_case, e.g. team_directory)
- A short description
- Whether it needs a database table (and if yes, which columns)
- Whether it needs a backend page (and which subpages, e.g. list, settings)
- The minimum REDAXO version (default ^5.18) and PHP version (default >=8.1)
Verify the path. Find the REDAXO root by looking for a redaxo/src/addons/ folder upwards from the current working directory. If not found, tell the user this command must run inside a REDAXO project.
Create the directory layout at redaxo/src/addons/<name>/:

package.yml
boot.php
install.php
uninstall.php
lang/de_de.lang
lang/en_gb.lang
lib/.gitkeep
fragments/.gitkeep
assets/.gitkeep

If backend pages were requested, also create pages/<subpage>.php for each.

Generate package.yml from the user's answers. Include a page: block with perm: <name>[] if backend pages are present.
Generate install.php with rex_sql_table::ensure(...) calls for each requested column. Use rex::getTable('<name>_<entity>') for table names and never hardcode the rex_ prefix.
Generate uninstall.php that drops the addon's tables and removes its config namespace via rex_config::removeNamespace('<name>').
Generate boot.php with:
- A backend asset hook scaffold (commented out unless the user wants assets)
- An empty space for rex_extension::register(...) calls
- A backend-only guard pattern showing how to require admin/specific permissions
Generate lang/de_de.lang and lang/en_gb.lang with at minimum a <name>_title key matching the addon's display title.
For each backend page, generate a starter pages/<subpage>.php that uses rex_fragment with core/page/section.php to render a titled section, plus a placeholder content area.
Do not add the addon to redaxo/data/core/config.yml – installation happens through the REDAXO backend (System → Addons → install). Tell the user to install via the backend after the files are in place.
After generating, summarize what was created and the next steps:
- Open the REDAXO backend
- Go to System → Addons
- Click Install on the new addon, then Activate
- Optionally grant the new permission(s) to user roles

Keep the generated code clean and commented in English. Use rex_i18n::msg('<name>_<key>') for any user-facing strings, even in the scaffolded backend pages.