[andreia]

Summary

Adds project-local verification skill for Filament LMS package under .cursor/skills/verify-filament-lms/. The skill documents and automates end-to-end verification: launching a throwaway Laravel app, publishing/running migrations in sequence, seeding test data, running a Playwright drive script to login/navigate, capturing evidence screenshots, and cleaning up the environment. Verified that courses appear on the dashboard after proper migration sequence; documented step URL redirect loop as a gotcha.

Design decisions

Project-local skill in .cursor/skills/ rather than global

Why

Verification requirements are package-specific (migration order, model trait requirements, seed data structure). Keeping the skill in the repo ensures it stays synchronized with package changes and can be updated in pull requests alongside code. Global skills become stale when packages evolve.

Files

.cursor/skills/verify-filament-lms/SKILL.md
.cursor/skills/verify-filament-lms/PROOF.md
.cursor/skills/verify-filament-lms/drive-lms.cjs

Playwright drive script instead of Pest browser tests

Why

Pest browser tests run in the package test environment and test package behavior, but they don't prove the package works when installed in a real Laravel app. The drive script launches an external Laravel app with the package installed via composer, proving the published migrations run in order and the UI renders correctly for an actual consumer. This catches integration issues (missing migrations, trait dependencies, route registration) that unit tests miss.

Files

.cursor/skills/verify-filament-lms/drive-lms.cjs

Three-step migration sequence: certificate builder → media library → LMS

Why

lms_courses references certificate_templates.id (from certificate-builder package) and course cards render Spatie media components. Publishing LMS migrations first fails with "no such table: certificate_templates". Publishing without media library migrations causes 500 errors when rendering course cards. The skill documents this required order so future verifications don't hit the same dependency errors.

High impact

Installation instructions in README and developer onboarding assume migrations "just work" with php artisan vendor:publish. This three-step sequence is mandatory but undocumented in the package README, so new adopters and CI environments will hit cryptic SQL errors if they don't follow this exact order.

Files

.cursor/skills/verify-filament-lms/SKILL.md (Launch section)

Feature documentation with Gotchas section

Why

The verification uncovered a step URL redirect loop: navigating directly to /lms/courses/{course}/{lesson}/{step} redirects to itself infinitely. This is real package behavior (the route expects session context set by clicking through the dashboard), not a harness bug. Documenting it in features/course-viewer.md prevents future developers from assuming it's an environment issue or wasting time debugging middleware when users report "step URLs don't work when bookmarked."

Files

.cursor/skills/verify-filament-lms/features/course-viewer.md

UI

The drive script verifies courses appear on the dashboard after login:

Course visible: "Introduction to Filament LMS" card renders with correct course card component (requires media table from Spatie).

Step navigation: Clicking the course link results in ERR_TOO_MANY_REDIRECTS. The step URL (/lms/courses/intro-to-filament-lms/getting-started/welcome) redirects to itself infinitely (HTTP 302 → same URL). Documented in features/course-viewer.md Gotchas.

Testing

Setup:
Fresh Laravel 13 app in /tmp/lms-verify-app, file-backed SQLite at database/database.sqlite.

Run the verification:

cd /workspace/.cursor/skills/verify-filament-lms
node drive-lms.cjs

Expected output:

✓ Login page
✓ Login successful
✓ Dashboard screenshot
✓ Course visible on dashboard: YES (1 matches)
❌ Error navigating to step: ERR_TOO_MANY_REDIRECTS

Evidence: Screenshots captured in .cursor/skills/verify-filament-lms/evidence/ (git ignored).

Full proof: See .cursor/skills/verify-filament-lms/PROOF.md for complete setup, migration sequence, seed data, and redirect chain analysis.

Note: The step redirect loop is real package behavior, not a verification failure. Direct step URL navigation is blocked by the package's session context requirements.

  

---

Note

Low Risk
Documentation and developer-only scripts under .cursor/skills/; no changes to package runtime code, migrations, or application behavior.

^{Reviewed by Cursor Bugbot for commit 5887784. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Stale Bugbot comment from a previous run.

[cursor]

Doctor script exits on first check

High Severity

set -e combined with ((PASSED++)) and ((FAILED++)) aborts doctor.sh on the first increment. When the counter is 0, the arithmetic expression evaluates to 0, which bash treats as failure, so the health check never prints results or exits with a meaningful status.

Additional Locations (1)

• .cursor/skills/verify-filament-lms/doctor.sh#L15-L20

 

^{Reviewed by Cursor Bugbot for commit 49a089f. Configure here.}

[cursor]

Stale Bugbot comment from a previous run.

[cursor]

Stale Bugbot comment from a previous run.

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

There are 2 total unresolved issues (including 1 from previous review).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 3c4ae13. Configure here.}

[cursor]

Evidence gitignore sqlite path is wrong

Low Severity

The new sqlite ignore rule is a repo-root path inside the evidence directory’s own .gitignore, so it will not match *.sqlite files written next to the screenshots.

 

^{Reviewed by Cursor Bugbot for commit 3c4ae13. Configure here.}