admin-customize-core
/admin-customize-core
Use when a core screen or behaviour (Users, Levels, Beranda, Log Aktivitas, auth pages) must look or behave differently in this project without editing vendor.
- Author
- yuanmaharsyah ↗
- Repository
- admin-boilerplate ↗
- Licence
- MIT
- Last repository change
- 08.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 08.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when a core screen or behaviour (Users, Levels, Beranda, Log Aktivitas, auth pages) must look or behave differently in this project without editing vendor.
Original author description
Use when a core screen or behaviour (Users, Levels, Beranda, Log Aktivitas, auth pages) must look or behave differently in this project without editing vendor.
How it works
SKILL.md has no level-two headings · 13 lines, 160 words
SKILL.md preview
---
name: admin-customize-core
description: "Use when a core screen or behaviour (Users, Levels, Beranda, Log Aktivitas, auth pages) must look or behave differently in this project without editing vendor."
---
# Customize a core screen in this project
Never edit `vendor/yuanmaharsyah/admin-core`. In order of preference:
- **UI only:** add `'Users::Index' => 'App::Users/Index'` to `admin-core.pages.overrides` in `config/admin-core.php` (if the project has none yet: `php artisan vendor:publish --tag=admin-core-config`) and create `resources/js/pages/Users/Index.tsx` (copy it from `vendor/yuanmaharsyah/admin-core/modules/Users/resources/js/pages/Index.tsx`, then edit; the case must match exactly).
- **Extra user fields:** a project migration for the columns (index the ones you filter on); a class implementing `Yuan\AdminCore\Users\UserFormExtension` (`fields()`: `ExtraFieldData` of type `text`, `number` or `select`; `rules($user)`: rules per field name); set `admin-core.users.form_extension` to it. The Users forms, validation (`extra.{name}`), the detail page and `$fillable` pick them up. Personal data (NIP, NIK…) also goes into `admin-core.audit.masked_fields`. Example: `tests/Fixtures/EmployeeFields.php`.
- **Extra user behaviour:** `App\Models\User` extends the core User (`admin-core.models.user`); add relations or `applyVisibility()` there.
- **Side effects:** listen to the core events in `Yuan\AdminCore\Events` (`UserCreated`, `UserLevelChanged`, `UserDeactivated`, `LevelPermissionsUpdated`, `ExportCompleted`).
- **Anything else:** stop and ask the owner; a change to the core belongs in the package.
Then `composer check`.
Versions
The database has no other skills named admin-customize-core.
Database snapshot: 13.11.2026 · package version aae36d04baf4 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 96admin-dashboard-widget
Use when adding a card, KPI, chart or table to Beranda (the dashboard) for a module. - 100admin
Add or change a screen in this play's admin panel — users, analytics, funnel, retention, grants, payments, support. Use for "add an admin page for X", "I need to see Y in the admin", "let me grant premium from the dashboard", "show me which users did Z", or when an operator… - 100orchardcore-templates
Skill for customizing templates in Orchard Core via the admin UI. Covers shape template overrides, content type templates, content part templates, content field templates, differentiated display types, Liquid template syntax, admin template editing, the Templates and… - 100new-page
Use when building a brand-new admin panel page or screen from scratch in ANY web framework. Enforces design quality gates. Do NOT use for modifying existing pages — use ui-change instead. - 96admin-deploy
Use when deploying this admin project to a server or updating a server to a new commit. - 100admin-customize
Customize the admin UI with swappable pages and layout slots. Use when replacing built-in pages (dashboard, list, edit, view), injecting content into layout slots (header, footer, sidebar, before/after), or registering per-collection overrides.