ci4-advanced

Configure runtime namespaces and integrate external modules into CodeIgniter 4 applications.

21|7|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/enlivenapp/Codeigniter4-App-and-API-Skills-for-Claude-Code --skill ci4-advanced
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: ci4-advanced
Source: https://github.com/enlivenapp/Codeigniter4-App-and-API-Skills-for-Claude-Code/tree/main/ci4-advanced
Command: npx skills add https://github.com/enlivenapp/Codeigniter4-App-and-API-Skills-for-Claude-Code --skill ci4-advanced

SYSTEM DOCUMENTATION & REQUIREMENTS

๐Ÿ’ก This Skill includes references (resource) components.

What problem does it solve?

Standard CodeIgniter 4 documentation does not cover patterns for building extensible plugin systems, addon architectures, or workflows that require code to live outside the default app/ directory. This Skill fills that gap with proven, production-ready techniques for integrating external code with CI4's core subsystems.

Core Features & Use Cases

  • Runtime Namespace Registration: Dynamically register external namespaces at boot time so CI4 can resolve controllers, models, and other classes from non-standard paths.
  • External Subsystem Integration: Run migrations, seeders, Spark commands, View Cells, and filters from code outside the app/ directory.
  • Extensible Configuration: Use the Registrar pattern and module auto-discovery to let addons ship their own config, routes, services, and filters without modifying core app files.
  • Use Case: Build a modular CI4 application where third-party addons live in a /plugins directory, each with their own migrations, CLI commands, and route definitions that load automatically when the addon is activated.

Quick Start

Use the ci4-advanced skill to configure runtime namespace registration for your CodeIgniter 4 plugin system so external addon controllers, migrations, and Spark commands are automatically discoverable without modifying core app files.

Frequently Asked Questions about ci4-advanced

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I load CodeIgniter 4 controllers and models from outside the app directory?โ–ผ

To load CodeIgniter 4 controllers and models from outside the app directory, you must implement runtime namespace registration. This dynamically registers external namespaces at boot time so CI4 can resolve classes from non-standard paths.

What is the best way to build a modular plugin system in CodeIgniter 4?โ–ผ

The best way to build a modular CodeIgniter 4 plugin system is using an addon architecture with Registrar-based config extension. This lets third-party addons in directories like /plugins ship their own routes and configs without modifying core app files.

How do I run CI4 migrations and Spark commands from external namespaces?โ–ผ

To run CI4 migrations and Spark commands from external namespaces, you integrate external subsystems by configuring the migration runner and command dispatcher to recognize dynamically registered runtime namespaces outside the standard app/ directory.

Can I dynamically inject routes for external addons in CodeIgniter 4?โ–ผ

Yes, you can dynamically inject routes for external addons in CodeIgniter 4. By leveraging module auto-discovery and dynamic route injection, addons load their route definitions automatically upon activation without altering core application files.

Why are my external Spark commands not discovered in CI4?โ–ผ

External Spark commands are not discovered in CI4 due to CLI command discovery failures and autoload caching issues common in external namespace integration. Properly registering namespaces at runtime resolves these subsystem execution pitfalls.