LibxaFrame Skill
What an AI needs to know.
- Version
- 1.0.0
- Category
- Developer tools
- Requires
- An assistant that reads Agent Skills
cp -r libxa-skill ~/.claude/skills/libxaframe
An Agent Skill teaching an AI assistant to work with LibxaFrame.
Why it exists
LibxaFrame looks enough like Laravel that a model will confidently write Laravel and produce code that parses and then fails at runtime. The skill is mostly the differences.
Installing
# For one project
mkdir -p .claude/skills
cp -r libxa-skill .claude/skills/libxaframe
# For every project
cp -r libxa-skill ~/.claude/skills/libxaframe
Restart your assistant. It loads the skill when a project looks like LibxaFrame, or when you mention it by name.
What it covers
The layout, routing, controllers, the Blade dialect, Atlas, validation, the console, testing and deploying. Plus two reference files loaded only when a task needs them: every known difference from Laravel, and full server configuration for Apache, nginx, Caddy and shared hosting.
The differences it teaches
src/app/andsrc/public/, notapp/andpublic/php libxa, notphp artisanResponse::getStatus(), notgetStatusCode()@extendstakes exactly one argument; a second is a parse error{{ }}is inert inside a@phpblock- Routes match in registration order, with no specificity sorting
- A migration whose class name does not match its filename is skipped silently
- The home page loads and every other route 404s, but only once deployed
Every item caused a real bug while this ecosystem was being built. That is the test for whether something belongs in it: not that it is a difference, but that the difference has cost someone an afternoon.