PHPackages karim-ashraf/lara-architect-ui - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. karim-ashraf/lara-architect-ui ActiveLibrary karim-ashraf/lara-architect-ui ============================== Developer workspace for understanding Laravel architecture through Lara Architect memory. v0.1.0(today)01↑2900%MITTypeScriptPHP ^8.2 Since Jul 23Pushed todayCompare [ Source](https://github.com/gubakareem/lara-architect-ui)[ Packagist](https://packagist.org/packages/karim-ashraf/lara-architect-ui)[ Docs](https://github.com/gubakareem/lara-architect-ui)[ RSS](/packages/karim-ashraf-lara-architect-ui/feed)WikiDiscussions main Synced today READMEChangelogDependencies (7)Versions (2)Used By (0) Lara Architect UI ================= [](#lara-architect-ui) **Developer workspace** for understanding Laravel architecture through Lara Architect memory. Prerequisite (required) ----------------------- [](#prerequisite-required) You **must** install the core package first: ``` composer require karim-ashraf/lara-architect ``` `lara-architect-ui` only works with [`karim-ashraf/lara-architect`](https://github.com/gubakareem/lara-architect) **^1.5**. Without core there is no architecture memory, no snapshots, and nothing for the Workspace to show. ``` 1. Install lara-architect ← required first 2. Install lara-architect-ui ← this package 3. Build & publish UI assets ``` Product brand: *Lara Architect — Architecture Memory and Improvement Platform for Laravel* Composer: `karim-ashraf/lara-architect-ui` What this package is -------------------- [](#what-this-package-is) `lara-architect-ui` does **not** analyze code. It visualizes architectural knowledge produced by `lara-architect`. ``` Core discovers. UI explains. Developers decide. ``` ``` karim-ashraf/lara-architect | | ArchitectureContextEnvelope · snapshots · reports | ↓ karim-ashraf/lara-architect-ui | ├── Workspace UI ├── Context visualization ├── Future Debugbar adapter ├── Future VS Code adapter └── Future GitHub adapter ``` **Dependency direction is one-way:** UI → core. Core must never depend on UI. OwnsDoes not ownRendering · interaction · developer experienceAnalyzer · memory truth · events · contracts> **Milestone:** A developer can understand one architectural issue in under 30 seconds. Acceptance (Phase 1) -------------------- [](#acceptance-phase-1) - Open context (`/architect/workspace?context=ProductController`) - See health - See issues - Understand why (select issue → explanation) - See possible action - Copy context - Preview Fix — decision screen consuming `FixProposal` only (Apply later) Requirements ------------ [](#requirements) RequirementDetail**Core (required first)**`karim-ashraf/lara-architect` **^1.5** — install before this packagePHP^8.2Laravel11 / 12 / 13Node.js**18+** with npm (build Workspace assets once)Install ------- [](#install) ### 1. Core first [](#1-core-first) ``` composer require karim-ashraf/lara-architect php artisan vendor:publish --tag=lara-architect-config ``` ### 2. Then Workspace UI [](#2-then-workspace-ui) ``` composer require karim-ashraf/lara-architect-ui ``` Until Packagist lists this package, add a VCS repository in your app `composer.json`: ``` "repositories": [ { "type": "vcs", "url": "https://github.com/gubakareem/lara-architect-ui" } ] ``` ``` composer require karim-ashraf/lara-architect-ui:^0.1 ``` ### 3. Build and publish assets [](#3-build-and-publish-assets) ``` cd vendor/karim-ashraf/lara-architect-ui npm install && npm run build php artisan vendor:publish --tag=lara-architect-ui-assets ``` ### Local path develop (optional) [](#local-path-develop-optional) Both packages as siblings: ``` // Laravel app composer.json "repositories": [ { "type": "path", "url": "../lara-architect" }, { "type": "path", "url": "../lara-architect-ui" } ] ``` ``` composer require karim-ashraf/lara-architect:@dev composer require karim-ashraf/lara-architect-ui:@dev ``` ### Update [](#update) ``` composer update karim-ashraf/lara-architect karim-ashraf/lara-architect-ui --prefer-dist cd vendor/karim-ashraf/lara-architect-ui && npm install && npm run build php artisan vendor:publish --tag=lara-architect-ui-assets --force ``` If update fails with `would clobber existing tag`: ``` composer clear-cache # PowerShell Remove-Item -Recurse -Force vendor\karim-ashraf\lara-architect, vendor\karim-ashraf\lara-architect-ui -ErrorAction SilentlyContinue # bash: rm -rf vendor/karim-ashraf/lara-architect vendor/karim-ashraf/lara-architect-ui composer update karim-ashraf/lara-architect karim-ashraf/lara-architect-ui --prefer-dist ``` Open: ``` /architect/workspace?context=ProductController&context_type=file ``` JSON (same snapshot adapters use): ``` /architect/workspace?context=ProductController&format=json ``` Architecture ------------ [](#architecture) ``` UI (React) ↓ consumes (never owns analysis) WorkspaceSnapshot · GovernanceSnapshot · Learning / Collaboration reports FixProposal · ControlledChangeResult ↓ from lara-architect (core) ``` Domain language only: `WorkspaceShell`, `IssueList`, `IssueDetails`, `ActionPanel`, `FixPreviewShell` — not Dashboard / Widget. Phase 2 Preview: React never generates code. Metric = Proposal Understanding Rate (what / why / risk / verification in ~30s). Dev --- [](#dev) ``` npm install npm run dev # Vite on :5177 ``` With `npm run dev`, the Blade view loads the Vite client when assets are unpublished. Phase 1.5 --------- [](#phase-15) Workspace Intelligence — breadcrumb, priority issues, impact dimensions, related context, neighborhood map. Phase 2 — Fix Preview --------------------- [](#phase-2--fix-preview) Decision screen (not a diff editor): ``` GET /architect/workspace/propose?issue_id=…&context=ProductController ``` Returns `FixProposal` JSON (`summary`, `change_set`, `architecture_impact`, `status: viewed`). ### Phase 2.1 — Change Understanding ✅ [](#phase-21--change-understanding-) Milestone: know what changes, where, and how architecture improves — before mutation. ``` preview/ ├── FixPreviewShell.tsx ├── ChangeNavigator.tsx ├── FileChangeList.tsx ├── DiffViewer.tsx ← comprehension only (not git) ├── ArchitectureImpact.tsx ├── VerificationDetails.tsx ├── StartImprovementButton.tsx ← no ApplyButton.tsx └── SessionComplete.tsx ``` ### Phase 3 — Controlled Change ✅ [](#phase-3--controlled-change-) Not “Apply Fix”. Architectural event: ``` Preview → Accept → Prepare → Apply → Verify (gate) → Session ``` - Safe proposals: **Start Improvement** - Assisted/Design: **Apply Later** records `ProposalReviewed` only (no mutation) - Session recorded only after verification passes (`storage/architect/sessions/`) - `ChangeExecution.events` is append-only (Replay-ready) ``` POST /architect/workspace/review POST /architect/workspace/improve POST /architect/workspace/confidence ``` ### Phase 3.1 — Improvement Confidence ✅ [](#phase-31--improvement-confidence-) After Session: “Did this improvement help?” → Yes / Not really. Feeds Improvement Success Rate (`storage/architect/metrics/improvement_success.json`). ### Phase 4 — Architecture Memory ✅ [](#phase-4--architecture-memory-) ``` GET /architect/workspace/history?context=ProductController ``` History panel: recent improvements + chronological Replay. Event stream under `storage/architect/events/`. Baseline under `storage/architect/baseline.json`. ### Phase 4.1 — Architecture Story ✅ [](#phase-41--architecture-story-) History explains itself: Problem → Decision → Change → Proof → Result (+ period trend). Events carry correlation IDs for Replay chains. Still postponed: AI · VS Code · GitHub · dashboards. ### Health Score 37 — LowBetter than 81% of packages Maintenance100 Actively maintained with recent releases Popularity2 Limited adoption so far Community6 Small or concentrated contributor base Maturity35 Early-stage or recently created project Bus Factor1 Top contributor holds 100% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Unknown Total 1 Last Release 0d ago ### Community Maintainers ![](https://avatars.githubusercontent.com/u/107818019?v=4)[gubakareem](/maintainers/gubakareem)[@gubakareem](https://github.com/gubakareem) --- Top Contributors [![gubakareem](https://avatars.githubusercontent.com/u/107818019?v=4)](https://github.com/gubakareem "gubakareem (6 commits)") --- Tags laravelarchitectureworkspacelara-architect ### Code Quality TestsPHPUnit ### Embed Badge ![Health badge](/badges/karim-ashraf-lara-architect-ui/health.svg) ``` [![Health](https://phpackages.com/badges/karim-ashraf-lara-architect-ui/health.svg)](https://phpackages.com/packages/karim-ashraf-lara-architect-ui) ``` ### Alternatives [psalm/plugin-laravel Psalm plugin for Laravel 3345.3M347](/packages/psalm-plugin-laravel)[laravel/cashier Laravel Cashier provides an expressive, fluent interface to Stripe's subscription billing services. 2.5k30.2M151](/packages/laravel-cashier)[laravel/pulse Laravel Pulse is a real-time application performance monitoring tool and dashboard for your Laravel application. 1.7k15.1M136](/packages/laravel-pulse)[roots/acorn Framework for Roots WordPress projects built with Laravel components. 9762.4M133](/packages/roots-acorn)[laravel/mcp Rapidly build MCP servers for your Laravel applications. 77922.3M185](/packages/laravel-mcp)[api-platform/laravel API Platform support for Laravel 58174.6k17](/packages/api-platform-laravel) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)