chore(boost): align guidelines and skill format

Author: realpascalbotjet

resources/boost/guidelines/core.blade.php

@@ -1,14 +1,8 @@
-{{--
-  Laravel Boost guidelines (repository core)
+{{-- Laravel Eloquent Scope as Select Guidelines for AI Code Assistants --}}
+{{-- Source: https://github.com/protonemedia/laravel-eloquent-scope-as-select --}}
+{{-- License: MIT | (c) ProtoneMedia --}}
 
-  This file intentionally stays small: it links this repository to its package-specific Boost skill.
---}}
+## Laravel Eloquent Scope as Select
 
-<section>
-    <h2>Repository development skill</h2>
-
-    <p>
-        When working on this repository, activate the <code>laravel-eloquent-scope-as-select-development</code> skill.
-        It contains package-specific conventions, testing notes, and common pitfalls.
-    </p>
-</section>
+- Expose Eloquent scopes as selectable query constraints.
+- Always activate the `laravel-eloquent-scope-as-select-development` skill when making package-specific changes.

resources/boost/skills/laravel-eloquent-scope-as-select-development/SKILL.md

@@ -1,24 +1,26 @@
-# laravel-eloquent-scope-as-select-development
+---
+name: laravel-eloquent-scope-as-select-development
+description: Development guidance for `protonemedia/laravel-eloquent-scope-as-select` (Expose Eloquent scopes as selectable query constraints.).
+license: MIT
+metadata:
+  author: ProtoneMedia
+  source: https://github.com/protonemedia/laravel-eloquent-scope-as-select
+---
 
-## When to activate
-- You are modifying code in **laravel-eloquent-scope-as-select**.
-- You are reviewing/triaging issues or PRs for **laravel-eloquent-scope-as-select**.
-- You are preparing a release (version bump, tag, changelog).
+# Laravel Eloquent Scope as Select Development
 
-## Aim
-Ship safe improvements while preserving the documented public API and keeping the test suite green.
+## Overview
+Use this skill when changing package code, docs, tests, or release tooling for `protonemedia/laravel-eloquent-scope-as-select`.
 
-## Do
-- Keep PRs small and focused.
-- Treat documented behavior (README) as the supported contract.
-- Add or update tests when behavior changes.
-- Prefer Laravel conventions (container bindings, facades, config publishing, events).
+## When to Activate
+- You are modifying code in this repository.
+- You are reviewing/triaging issues or PRs for this package.
+- You are preparing a release (version bump, tag, changelog).
 
-## Don’t
-- Introduce breaking changes without clearly documenting them.
-- Add new runtime dependencies without strong justification.
-- Bake in app-specific assumptions; keep the package reusable.
+## Workflow
+1. Skim the README / docs to confirm the public contract.
+2. Read  for common patterns and pitfalls.
+3. Keep changes small, add/update tests when behavior changes, and avoid breaking API changes.
 
-## Quick workflow
-- Install dependencies: `composer install`
-- Run tests: `composer test` (or the repository’s configured test command)
+## References
+- 

resources/boost/skills/laravel-eloquent-scope-as-select-development/references/laravel-eloquent-scope-as-select-guide.md

@@ -1,19 +1,15 @@
-# laravel-eloquent-scope-as-select development guide
+# Laravel Eloquent Scope as Select Reference
 
-For full documentation, see the README: https://github.com/protonemedia/laravel-eloquent-scope-as-select#readme
+Complete reference for `protonemedia/laravel-eloquent-scope-as-select`. Full documentation: https://github.com/protonemedia/laravel-eloquent-scope-as-select#readme
 
-## At a glance
-Allows re-using Eloquent query scopes/constraints by adding them as a **subquery/select**.
+## Start Here
+- README / docs: https://github.com/protonemedia/laravel-eloquent-scope-as-select#readme
 
-## Local setup
-- Install dependencies: `composer install`
-- Keep the dev loop package-focused (avoid adding app-only scaffolding).
+## Notes for AI Assistants
+- Treat the README as the source of truth for the supported public API.
+- Keep changes backward-compatible unless the change is explicitly a breaking change.
 
 ## Testing
-- Run: `composer test` (preferred) or the repository’s configured test runner.
-- Add regression tests for bug fixes.
+- Run the repository test command (see README / composer scripts).
 
-## Notes & conventions
-- Subquery correctness is essential (bindings, aliases, SQL portability).
-- Add tests for complex scopes (whereHas, joins, bindings).
-- Prefer database-agnostic SQL when possible.
+For detailed usage examples and the full API surface, refer to the README.