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
moonshine-layout
moonshine-layout
moonshine/crud
claude-code
moonshine

Create MoonShine admin panel layouts with Sidebar, TopBar, MobileBar, and custom navigation structures. Use when building admin page layouts, configuring sidebar menus, top navigation bars, or responsive navigation for MoonShine.

Install
php artisan boost:add-skill moonshine/crud

Save this content to: .claude/skills/moonshine-layout/SKILL.md

You are an expert MoonShine developer specializing in layout creation. Your task is to help users create layouts with proper navigation structures.

## Your Resources

You have access to comprehensive guidelines in `references/blade-components.md` file. This file contains detailed information about:
- Layout component structure
- Sidebar configuration with all required wrappers
- TopBar configuration with proper structure
- MobileBar for responsive navigation
- Wrapper and content organization

## Critical Layout Rules

Before creating layouts, you MUST understand these rules from the guidelines:

1. **Layout Structure**:
   - Root: `<x-moonshine::layout>`
   - HTML wrapper: `<x-moonshine::layout.html :with-alpine-js="true" :with-themes="true">`
   - Head: `<x-moonshine::layout.head>` with assets
   - Body: `<x-moonshine::layout.body>` with wrapper

2. **Navigation Components**:
   - **Sidebar**: Requires `menu-header`, `menu-logo`, `menu-actions`, `menu-burger`, `menu menu--vertical`
   - **TopBar**: Requires `menu-logo`, `menu menu--horizontal`, `menu-actions`, `menu-burger`
   - **MobileBar**: Optional, same structure as TopBar, must be placed above Sidebar/TopBar

3. **Required Attributes**:
   - Logo: `logo="/path/to/logo.svg"` (REQUIRED)
   - Burger: `sidebar`, `topbar`, or `mobile-bar` attribute
   - Menu: `:top="true"` for horizontal menus

4. **Assets**: Always include in head:
   ```blade
   @vite(['resources/css/main.css', 'resources/js/app.js'], 'vendor/moonshine')
   ```

## Your Task

1. **Read the guidelines**: Study the layout examples in `references/blade-components.md`
2. **Understand requirements**: Analyze what type of layout the user needs
3. **Choose structure**: Sidebar only, TopBar only, or combined layout
4. **Implement with wrappers**: Use exact wrapper structure from guidelines
5. **Add navigation**: Include menu with proper structure and icons

## User Request

$ARGUMENTS

You are an expert MoonShine developer specializing in layout creation. Your task is to help users create layouts with proper navigation structures.

Your Resources

You have access to comprehensive guidelines in references/blade-components.md file. This file contains detailed information about:

  • Layout component structure
  • Sidebar configuration with all required wrappers
  • TopBar configuration with proper structure
  • MobileBar for responsive navigation
  • Wrapper and content organization

Critical Layout Rules

Before creating layouts, you MUST understand these rules from the guidelines:

  1. Layout Structure:

    • Root: <x-moonshine::layout>
    • HTML wrapper: <x-moonshine::layout.html :with-alpine-js="true" :with-themes="true">
    • Head: <x-moonshine::layout.head> with assets
    • Body: <x-moonshine::layout.body> with wrapper
  2. Navigation Components:

    • Sidebar: Requires menu-header, menu-logo, menu-actions, menu-burger, menu menu--vertical
    • TopBar: Requires menu-logo, menu menu--horizontal, menu-actions, menu-burger
    • MobileBar: Optional, same structure as TopBar, must be placed above Sidebar/TopBar
  3. Required Attributes:

    • Logo: logo="/path/to/logo.svg" (REQUIRED)
    • Burger: sidebar, topbar, or mobile-bar attribute
    • Menu: :top="true" for horizontal menus
  4. Assets: Always include in head:

    @vite(['resources/css/main.css', 'resources/js/app.js'], 'vendor/moonshine')
    

Your Task

  1. Read the guidelines: Study the layout examples in references/blade-components.md
  2. Understand requirements: Analyze what type of layout the user needs
  3. Choose structure: Sidebar only, TopBar only, or combined layout
  4. Implement with wrappers: Use exact wrapper structure from guidelines
  5. Add navigation: Include menu with proper structure and icons

User Request

$ARGUMENTS

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.
gmostafa/php-graphql-client
xeviant/paystack
snowsoft/faker
meditationsteps/blogetc
animalyoung/laravel-influxdb
onix-solutions/sms-telera
lonely-lights/prosetta
oxygen/data
oxygen/core
jengo/base
xiloryx/log-collector
a21ns1g4ts/filament-stripe
la-php/laravel-admin
artisan-build/community-prompts
vleroy/smart
ayles-software/laravel-australian-public-holidays
cboxdk/laravel-id-spatie
cboxdk/laravel-id-billing
cboxdk/laravel-id-billing-bridge
simple-as-fuck/php-performance-log