How siubie/kaido-kit works
Project type and purpose
• This is a full-stack Laravel 11.0 application with a FilamentPHP 3.2-based admin panel starter kit (“Kaido Kit”) intended to accelerate CRUD, API, auth, media, settings, and RBAC setup.
• The README confirms it’s a feature-rich admin interface that bundles Filament plugins (Shield, Socialite, Breezy, Impersonate, Media Library, Settings, API Service) plus export/import, two-factor auth, social login, and auto-generated API docs.
File structure
• Top-level:
• app/Filament → Filament Resources (Books, Users, Roles, Contacts), Pages, Exports/Imports, API handlers
• app/Http → HTTP Controllers (web & API), Form Requests, API Resources
• app/Models & app/Policies → Eloquent models and authorization policies
• app/Services & app/Settings → custom service classes (ApiService) and dynamic settings
• config/, database/, routes/, public/, resources/ → typical Laravel layout
• Tests → PHPUnit/Pest Feature and Unit tests
• docker-compose.yml, sail support, stubs, webpack (Vite) and Tailwind configs
README for additional insights
• States core plugins and patterns: RBAC via Shield, Social login, 2FA, user impersonation, API with Sanctum, media via Spatie, settings via Spatie.
• Quick-start and Docker/Sail instructions suggest standard LAMP/Sail deployment.
Elements
• Clear labels for each component (e.g., “Filament Resource: BookResource → CRUD pages and API handlers”)
• HTTP request flow (Browser → WebServer → Laravel Router → Controller/Filament Page → Model → DB)
• Data flows between Filament Resources and Import/Export services
• Calls from Controllers to Services (ApiService) and from Services to external APIs
• Purple clouds = external services (Google OAuth, Resend, Scramble)