For AI agents

Prompts to start from

Each one links to /llms.txt, so it works in any agent that can fetch a URL; with the MCP server connected, the agent can also see what your app already has. Change the routes, fields and wording to fit your app.

Login page

Build a login page at /login with Bladewell components (https://www.bladewellui.com/llms.txt): email and password fields, a "Remember me" checkbox and a "Log in" button. When the email or password is wrong, show an error alert above the form and keep the email filled in. Validate in a Form Request, and install only the components you use with php artisan bladewell:add.

Built from Text input, Password, Checkbox, Button and Alert.

Sign-up page

Build a sign-up page at /register with Bladewell components (https://www.bladewellui.com/llms.txt): name, email, password and password confirmation, and a "Create account" button. The password field shows a live checklist of the rules (at least 12 characters, upper and lower case, a number), and the Form Request enforces the same ones with Password::min(12)->mixedCase()->numbers(). Show each field's error under it, and install only the components you use with php artisan bladewell:add.

Built from Text input, Password and Button.

Account settings

Build an account settings page at /settings with Bladewell components (https://www.bladewellui.com/llms.txt): tabs for Profile and Password, with the open tab kept in the URL. Profile has name and email fields and a Save button; Password has the current password, a new password with a live checklist of its rules, and a Save button. After saving, redirect back and show a success toast. Install only the components you use with php artisan bladewell:add.

Built from Tabs, Text input, Password, Button and Toast.

Starting a new app? The starter kit comes with the components installed and the MCP server set up, so you can give your agent a prompt straight away.

Connect the MCP server

In your own app, php artisan bladewell:mcp is an MCP server the agent can connect to. On top of the catalogue, it knows which components this app has, which installed files are out of date or edited, and it can install: a dry run first, which writes nothing until you agree, and never over files you edited.

claude mcp add bladewell -- php artisan bladewell:mcp

{
    "mcpServers": {
        "bladewell": {
            "type": "stdio",
            "command": "php",
            "args": [
                "${workspaceFolder}/artisan",
                "bladewell:mcp"
            ]
        }
    }
}

{
    "servers": {
        "bladewell": {
            "type": "stdio",
            "command": "php",
            "args": [
                "artisan",
                "bladewell:mcp"
            ],
            "cwd": "${workspaceFolder}"
        }
    }
}

codex mcp add bladewell -- php /path/to/your-app/artisan bladewell:mcp

gemini mcp add bladewell php /path/to/your-app/artisan bladewell:mcp

Claude Desktop, Windsurf, Zed, JetBrains and any other client: the command php, with the arguments /path/to/your-app/artisan bladewell:mcp. The full path to artisan is what makes it work where a client may not start the server in your app's folder. If a desktop app can't find php, give it the full path too (which php).

What agents can read

The same catalogue as this site, in a form agents can read. Each component's entry has its install command, props, working examples and full source, and for an app built with Livewire, a Livewire example.

/llms.txt

An index of every component, for agents that follow the llms.txt convention.

/r/index.json

Every component, with a link to its full entry.

/r/datepicker.json

One component's full entry: install command, props, examples and source.

php artisan bladewell:list --json

The same catalogue offline, from the installed package.

php artisan bladewell:mcp

An MCP server in your app: the catalogue, what this app has installed and edited, and installing with a dry run first.