Neura Kit Laravel Package

Product Decisions This Supports

• Build vs. buy for UI primitives. v3.0.0 ships ~12 net-new components (action button, split button, button group, expanding button group, confirm morph, number field, mention input, signature pad, time dial, date reel, activity rings, JSON viewer) on top of a mature primitives set. That is months of design-and-engineering work your team no longer has to scope, staff, or maintain — a strong default argument for buying/ adopting over building anything that isn't core differentiation.
• Scope decisions on interaction-heavy features. The new components map directly onto features teams routinely under-estimate: destructive-action safety (confirm-morph with confirm/pending/done/error/retry/undo and timeout windows), data entry (number-field, date-reel, mention-input), and compliance/legal (signature-pad with PNG export). PMs can now commit to these in a roadmap without a bespoke design-system ticket.
• Time-zone and scheduling product bets. time-dial (up to five cities, working-hours arc, fixed noon/6/18/midnight geometry) and date-reel are unusually specific primitives. If you're shipping anything in scheduling, global team coordination, or booking, this release materially changes the cost of that roadmap item.
• Data and analytics surface area. Three new chart types (donut, waffle, slope) plus activity-rings (with day scrubber) and json-viewer (searchable tree, 2000-match cap, paging, keyboard nav) mean dashboards, admin/debug panels, and internal tooling can be shipped without pulling in a heavyweight charting or tree-view dependency.
• Design-system consistency as a roadmap enabler. The appearance API (neuraKit({ appearance }) with neutral/muted/tint/vivid, and single-hue light/dark ramps with light/dark tuning) plus shared motion tokens (duration-fast 160ms → duration-spring 580ms, three easings) means theming and motion become configuration, not a per-feature design negotiation. This is the release's biggest strategic item — it turns the kit into a themable system rather than a component set.
• Accessibility as a release criterion, not a retrofit. prefersReducedMotion() is now honored in scripted motion (Web Animations API bypasses the global CSS rule), tooltips skip travel, and the time-dial focus-ring and readout-overlap bugs are fixed. PMs can hold accessibility acceptance criteria on animation and interaction work.
• Internationalization roadmap. EN/FR strings added for the JSON viewer and the new form/action controls. Useful signal if you have near-term French/Canadian or EU market plans; the pattern is there but coverage is partial.
• Procurement/licensing risk decision. Explicitly "MIT, with no license key." Removes a legal review and a recurring line item — a meaningful unblocker for regulated or budget-constrained orgs.

When to Consider This Package

Adopt when:

• You are on Laravel + Blade/Livewire + Alpine + Tailwind and want first-party-feeling UI rather than a React/Vue island. The installer already targets this stack: php artisan neura-kit:install patches vite.config.js/.mjs/.ts/.mts and adds the Tailwind @source line to resources/css/app.css.
• Your product is form- and workflow-heavy (admin panels, internal tools, CRMs, ops/booking interfaces) where confirm-morph, number/mention/date inputs, filters, kanban, flow, and rule builder pull disproportionate weight.
• You need theming across light and dark without a design-system team, and want a single hue to drive the surface ramp.
• You want to de-risk accessibility and motion with a library that ships tokens and a reduced-motion contract.
• You are comfortable with a 3.0 major — the installer changed behavior (it patches the Vite config and CSS, leaves app.js untouched) and the toast factory now registers via onAlpineInit. Budget a short upgrade spike if you are on 2.x.

Look elsewhere when:

• You are not on Laravel/Blade — this is a live template + Alpine package; a React/Vue/Svelte app gets nothing from it.
• You need enterprise-grade charts (large datasets, extensive axis/annotation control, server-side rendering of charts). The native canvas charts are intentionally narrow (slope is exactly two moments; waffle is a fixed 10×10 grid). Pair with a dedicated charting library for analytical depth.
• You require formal accessibility certification — reduced motion, keyboard nav, and focus fixes are present, but this release does not claim a WCAG audit, and a canvas signature pad and canvas charts carry inherent a11y limits.
• You need broad localization — EN/FR only, and only for a subset of components.
• You have a strict dependency-light policy or a design system you must conform to — the value proposition here is opinionated visual language, not headless primitives.
• You cannot absorb breaking-change churn — a 3.0 within this cadence implies ongoing majors; plan for maintenance windows.

How to Pitch It (Stakeholders)

For executives: Neura Kit 3.0.0 is an MIT-licensed, no-license-key Laravel UI package that gives us a large, coherent set of production-grade interface components — including several expensive ones (destructive-action confirm/undo flows, multi-timezone scheduling dials, signature capture, activity analytics, a searchable JSON inspector) — plus a theming and motion system that keeps light and dark consistent from a single color. The commercial case is straightforward: it converts a long list of "we'd need to design and build that" roadmap items into configuration work, with no per-seat or renewal cost and no procurement cycle. It also raises our baseline on accessibility and i18n without a dedicated workstream.

For engineering: This is a well-scoped major. The headline is the appearance API and shared motion tokens — theming and animation become declarative instead of bespoke CSS, and prefersReducedMotion() is correctly handled for scripted motion (the Web Animations API path that CSS can't reach). We pick up roughly a dozen new components with consistent size/variant/color/rounded packs, EN/FR strings, and a batch of real bug fixes (rule-builder drag reordering, calendar/date-picker selection desync, select's nested Livewire binding, waffle and slope chart rendering). Known upgrade work is small and enumerable: the installer now patches our Vite config and Tailwind @source instead of app.js, and the toast factory registers through onAlpineInit. Constraints to note: charts are deliberately narrow (fine for dashboards, not for analytics), and multi-select remains on neura::select rather than a separate component. Recommendation: pilot on one internal admin surface, then standardize.