Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
laravel-themer-development
laravel-themer-development
alizharb/laravel-themer
claude-code
package
theme
laravel
Themer

Build and maintain Laravel Themer themes using native Laravel, Livewire, Vite, diagnostics, previewing, and design-token workflows.

Install
php artisan boost:add-skill alizharb/laravel-themer

Save this content to: .claude/skills/laravel-themer-development/SKILL.md

# Laravel Themer Development

Use this skill when working in an application that uses `alizharb/laravel-themer`.

## Workflow

1. Inspect themes with `php artisan theme:list`, `php artisan theme:status`, and `php artisan theme:debug {theme} --json`.
2. Generate new themes with `php artisan theme:make`.
3. Put theme views in `resources/views`, Livewire classes in `app/Livewire`, and assets in `resources/assets`.
4. Use `theme.json` for metadata, inheritance, required modules, conflicts, provided capabilities, screenshots, hooks, and design tokens.
5. Use `theme_token()` and `@themeTokens` for reusable brand values.
6. Use `php artisan theme:preview {theme}` to QA inactive themes.
7. Run `php artisan theme:doctor`, `php artisan theme:check`, and `php artisan theme:refresh` after structural changes.

## Guardrails

- Do not bypass theme inheritance by hard-coding absolute theme paths in views.
- Do not globally activate a theme just to inspect it; use preview URLs.
- Do not duplicate parent theme views unless the child theme intentionally overrides them.
- Keep theme manifests valid and machine-readable.

Laravel Themer Development

Use this skill when working in an application that uses alizharb/laravel-themer.

Workflow

  1. Inspect themes with php artisan theme:list, php artisan theme:status, and php artisan theme:debug {theme} --json.
  2. Generate new themes with php artisan theme:make.
  3. Put theme views in resources/views, Livewire classes in app/Livewire, and assets in resources/assets.
  4. Use theme.json for metadata, inheritance, required modules, conflicts, provided capabilities, screenshots, hooks, and design tokens.
  5. Use theme_token() and @themeTokens for reusable brand values.
  6. Use php artisan theme:preview {theme} to QA inactive themes.
  7. Run php artisan theme:doctor, php artisan theme:check, and php artisan theme:refresh after structural changes.

Guardrails

  • Do not bypass theme inheritance by hard-coding absolute theme paths in views.
  • Do not globally activate a theme just to inspect it; use preview URLs.
  • Do not duplicate parent theme views unless the child theme intentionally overrides them.
  • Keep theme manifests valid and machine-readable.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
mehedimi/laravel-amp-mail
happones/laravel-vue-i18n-generator
jwerd/inertia-table
siberfx/flysystem-wasabi
hollyit/token-replace
ippanelcom/laravel-sdk
adachsoft/changelog-linter
adachsoft/collection
payerurl/telegrambot-crypto-payment-instant-payout
dskripchenko/laravel-hybrid-search
riorizkyrainey/lara-ced
mehedimi/static-vel
zharp/zharp
nonsapiens/bigquery-model-sync
lgu-bayambang-ict-office/lgu-laravel-development-standards
andydefer/laravel-support
se7enxweb/flysystem
lampwick/laravel
jeslage/statamic-emojis
micahdshackelford/rmap-laravel