Claude Code admin-interface-component-audit for Blade reuse

Inventory existing components, partials, visual tokens, and Alpine stores before building or refactoring an admin interface.

中文

Install in Claude Code

Open the Laravel Flow Admin source in Claude Code with the target page and existing Blade and Alpine code.

Review `.claude/skills/admin-interface-component-audit/SKILL.md` and its requirements at the pinned GitHub commit.
Create `.claude/skills/admin-interface-component-audit/` in your project and save the reviewed file as `.claude/skills/admin-interface-component-audit/SKILL.md`.
Start Claude Code from that project's root, then select `/admin-interface-component-audit` in the slash menu.

Example task

Admin page admin-18 needs to show archived orders. The existing {component: 'ArchiveBadge', token: 'muted'} already represents the state, while the page lacks the new list.

What to check

The audit table records {component: 'ArchiveBadge', decision: 'REUSE'}, its existing template path, and the reason it fits. The new list keeps the muted visual token.

Original SKILL.md on GitHub · Updated 2026-11-14

Frequently asked question

When should I create a global component?

First check whether existing pieces can be reused or extended. Create a domain or global component according to its scope when reuse would hurt clarity or correctness.