codeigniter-architecture-patterns
Enforces separation of concerns and consistent project patterns in CodeIgniter.
Install
mkdir -p .claude/skills/codeigniter-architecture-patterns && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15897" && unzip -o skill.zip -d .claude/skills/codeigniter-architecture-patterns && rm skill.zipInstalls to .claude/skills/codeigniter-architecture-patterns
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when: designing or refactoring feature architecture in CodeIgniter for maintainability, separation of concerns, and module consistency.Key capabilities
- →Follow predictable feature layout
- →Separate read models, write workflows, and cross-cutting concerns
- →Centralize shared behavior in base services/helpers
- →Prefer explicit dependency boundaries
- →Ensure new code matches folder and naming conventions
How it works
The skill guides the design and refactoring of CodeIgniter feature architecture by promoting consistent patterns, separation of concerns, and centralized shared behavior.
Inputs & outputs
When to use codeigniter-architecture-patterns
- →Design feature architecture
- →Refactor CodeIgniter modules
- →Ensure consistent naming conventions
- →Separate business logic from controllers
About this skill
CodeIgniter Architecture Patterns
Goal
Keep the codebase maintainable with consistent project patterns.
Do
- Follow a predictable feature layout across controllers, models, views, language files, and tests.
- Separate read models, write workflows, and cross-cutting concerns such as authorization and logging.
- Centralize shared behavior in base services/helpers instead of duplicating per module.
- Prefer explicit dependency boundaries over hidden global state.
Checks
- Feature logic can be traced without jumping across unrelated layers.
- New code matches folder and naming conventions used by existing modules.
- Refactors preserve public routes and response formats unless explicitly changed.
When not to use it
- →When the task is not about designing or refactoring feature architecture in CodeIgniter
Limitations
- →Applies specifically to CodeIgniter architecture
- →Requires refactors to preserve public routes and response formats unless explicitly changed
How it compares
This skill enforces specific architectural patterns for CodeIgniter, ensuring maintainability and consistency across modules, unlike ad-hoc development.
Compared to similar skills
codeigniter-architecture-patterns side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| codeigniter-architecture-patterns (this skill) | 0 | 3mo | No flags | Intermediate |
| laravel-architecture | 7 | 1mo | No flags | Intermediate |
| laravel-patterns | 0 | 4mo | Review | Advanced |
| laravel-event-driven-architecture | 0 | 1mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
laravel-architecture
HoangNguyen0403
Core architectural standards for scalable Laravel applications.
laravel-patterns
helmordev
Laravel architecture patterns, routing/controllers, Eloquent ORM, service layers, queues, events, caching, and API resources for production apps.
laravel-event-driven-architecture
noemdb
Best practices for Laravel events and listeners including event discovery, queued listeners, subscribers, and model events for decoupled architecture.
php-best-practices
HoangNguyen0403
PHP best practices, PSR standards, and code quality guidelines.
laravel-pdf
spatie
Generate PDFs from Blade views or HTML using spatie/laravel-pdf. Covers creating, formatting, saving, downloading, and testing PDFs with the Browsershot, Cloudflare, or DOMPDF driver.
php-guidelines-from-spatie
freekmurze
Describes PHP and Laravel guidelines provided by Spatie. These rules result in more maintainable, and readable code.