Two doors, one system. After installing, you can start through the Studio door — open the Dev Studio, write the Mind in Plan mode, scaffold slices in Create, shape them in Design — or through the AI door — hand your AI assistant the shipped skill (npx skills add HereafterSol/laraslice) and brief it with the Mind; it drafts, scaffolds, and verifies by the same declarations. Both doors produce the same Mind · Body · Heart files, and teams mix them freely. From-zero and brief-first starts are first-class; porting an existing system is simply the third door (see the Replica Protocol). Full guide: the framework skill, §24.

1. Installation & Setup

composer require hereafter/laraslice
php artisan slice:install

slice:install publishes the landing page, runs all core database migrations, and seeds the default Super Admin user (admin@laraslice.com / password).

2. First, the Mind — the one first step

Every LaraSlice project, whichever door you use, starts the same way: write the Mind before the first slice. The Mind is the project's one-page intent — purpose, who uses it, the main journeys, and how success is measured. It takes minutes, a non-technical owner can read and sign it, and everything else (slices, flows, gates) is checked against it.

• In the Studio: open Plan mode and write it as plain-language cards.
• With an AI assistant: hand it the skill family and your brief; it drafts system.yaml for your sign-off (or run php artisan slice:plan:draft from a written brief). The family, arranged the way skills.sh indexes skills — one folder per skill, examples and references inside: laraslice (the core: trilogy, fields, standard UI, concepts), laraslice-start (this door), laraslice-port (moving an existing system), laraslice-operate (running it after launch: customize, optimize, improve, operate, upgrade). Install them all with npx skills add HereafterSol/laraslice.
• The full pre-build checklist — PRD, tech choices, app flow, design identity, schema, plan — is the pre-build dossier (framework skill, §28). New here? That section plus §24 are the whole on-ramp; the rest of the skill is reference you grow into.

3. Scaffold Vertical Slices & Domain Suites

Generate a single feature slice or an entire multi-slice domain suite with full CRUD, BlatUI views, and Flutter mobile clients:

# Scaffold a single slice
php artisan slice:make Invoice --flutter

# Scaffold an entire CRM Domain Suite (multi-slice Bounded Context)
php artisan slice:make Companies Contacts Deals --domain=CRM

# Scaffold an E-Commerce Suite with Flutter mobile clients
php artisan slice:make Products Orders Customers Categories --domain=E-Commerce --flutter

This instantly creates:

• app/Slices/{Domain}/{Slice}/ (Full vertical slices with DTO contracts, models, controllers, and BlatUI views)
• Unified REST APIs and BlatUI collapsible domain sidebar navigation
• flutter_app/lib/slices/{slice}/ (Optional native Flutter Dart models, API clients, and mobile screens)

4. Production Boot Optimization

In production environments, cache discovered slices just like route:cache:

php artisan slice:cache

To clear the cache during development:

php artisan slice:clear

5. The Dev Studio — six modes, one surface

The ONE Studio (http://localhost:8000/laraslice/wizard) is organized as destinations, not steps:

• Plan — the Mind made visible: purpose, actors, journeys, and operations as cards, editable in plain-language forms with diff-before-save; slice:plan:draft drafts a Mind + Bodies from discovery.
• Port — reverse-engineer a legacy system into slices (anatomy capture, twin-port namespacing, per-slice porting notes).
• Design — the declarative slice.yaml / Body designer with field widths and instant component preview.
• Create — scaffold slices and domain suites from presets, blueprints, or a brief.
• Manage — lifecycle: seed, toggle, wipe, destroy, repair — mirrored by the CLI.
• Operate — health checks, backups against the Mind's declared policy, the audit trail, an access review that flags risky grants, and one-click operator-manual generation.

6. Domain Lifecycle & Data Management CLI

Manage slice lifecycle, seeding, and teardown directly from the command line:

# List all slices with domain grouping
php artisan slice:list
php artisan slice:list --domain=CRM

# Seed realistic demo data into slice tables
php artisan slice:seed Contacts --count=20
php artisan slice:seed --domain=CRM --count=5

# Toggle slice/domain activation (hide/show in navigation)
php artisan slice:toggle Contacts --disable
php artisan slice:toggle --domain=CRM --enable

# Wipe (truncate) all records from slice tables
php artisan slice:wipe Tests --force
php artisan slice:wipe --domain=CRM --force

# Destroy a slice or domain (drop tables, clean migrations, delete files)
php artisan slice:destroy Tests --mode=comple

…