@stellisoft/stellify-mcp 0.1.36 → 0.1.37

package/dist/index.js

@@ -600,16 +600,24 @@ Use the returned UUID with html_to_elements (page parameter) or get_route for fu
 **For elements inside @foreach loops (SSR/Blade):**
 Use these attributes to reference the loop variable (defaults to \`$item\`):
 - \`textField\`: Field name for text content → outputs \`{{ $item->fieldName }}\`
-- \`hrefField\`: Field name for href → outputs \`href="{{ $item->fieldName }}"\`
+- \`hrefField\`: Field name for href → outputs \`href="{{ $item->fieldName }}"\` (field value ONLY, no prefix)
 - \`srcField\`: Field name for src → outputs \`src="{{ $item->fieldName }}"\`
 
+**For hrefs with path prefixes (IMPORTANT):**
+\`hrefField\` outputs ONLY the field value. There is NO \`hrefPrefix\` attribute.
+For links like \`/post/slug-here\`, you MUST use \`hrefExpression\`:
+- \`hrefExpression: "/post/{{ $item->slug }}"\` → outputs \`href="/post/{{ $item->slug }}"\`
+- \`hrefExpression: "/category/{{ $item->slug }}"\` → outputs \`href="/category/{{ $item->slug }}"\`
+
 **For complex Blade expressions in attributes:**
-Use expression attributes when you need more than simple field access (e.g., route helpers, method calls):
+Use expression attributes when you need more than simple field access:
 - \`hrefExpression\`: Blade expression for href → outputs \`href="..."\` with the expression
 - \`srcExpression\`: Blade expression for src → outputs \`src="..."\` with the expression
 - \`altExpression\`: Blade expression for alt → outputs \`alt="..."\` with the expression
 
-Example: \`hrefExpression: "{{ route('posts.show', $item->slug) }}"\`
+Examples:
+- Path prefix: \`hrefExpression: "/post/{{ $item->slug }}"\`
+- Route helper: \`hrefExpression: "{{ route('posts.show', $item->slug) }}"\`
 
 **For Blade text content:**
 Use the \`statements\` array with statement UUIDs containing Blade code. The statement's \`code\` property will be output directly for Blade to evaluate.`,
@@ -739,10 +747,14 @@ For SSR/Blade pages, do NOT pass raw Blade expressions in text or attributes. Th
 1. **For static HTML:** Pass clean HTML without Blade syntax, then use \`update_element\` to add dynamic behavior
 2. **For loop content:** After creating elements, use \`update_element\` with:
    - \`textField\`, \`hrefField\`, \`srcField\` for simple field access (outputs \`{{ $item->field }}\`)
-   - \`hrefExpression\`, \`srcExpression\`, \`altExpression\` for complex expressions
+   - \`hrefExpression\`, \`srcExpression\`, \`altExpression\` for paths with prefixes or complex expressions
    - \`statements\` array with statement UUIDs for text content with Blade code
 3. **For conditionals:** Use \`s-directive\` elements as siblings (see update_element docs)
 
+**IMPORTANT - Links with path prefixes:**
+\`hrefField\` outputs ONLY the field value with no prefix. There is NO \`hrefPrefix\` attribute.
+For links like \`/post/my-slug\`, use \`hrefExpression: "/post/{{ $item->slug }}"\` instead.
+
 **Loop variable:** Inside \`@foreach\` loops created with \`s-directive\`, the default loop variable is \`$item\`. Use \`textField: "title"\` to output \`{{ $item->title }}\`.
 
 Prefer SVG icons over emoji (encoding issues).`,
@@ -1497,7 +1509,7 @@ const SERVER_INSTRUCTIONS = `Stellify is a coding platform where code is stored
 // Create MCP server
 const server = new Server({
     name: 'stellify-mcp',
-    version: '0.1.36',
+    version: '0.1.37',
 }, {
     capabilities: {
         tools: {},

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@stellisoft/stellify-mcp",
-  "version": "0.1.36",
+  "version": "0.1.37",
   "mcpName": "io.github.MattStellisoft/stellify-mcp",
   "description": "MCP server for Stellify - AI-native code generation platform",
   "main": "dist/index.js",

package/server.json

@@ -6,12 +6,12 @@
     "url": "https://github.com/Stellify-Software-Ltd/stellify-mcp",
     "source": "github"
   },
-  "version": "0.1.36",
+  "version": "0.1.37",
   "packages": [
     {
       "registryType": "npm",
       "identifier": "@stellisoft/stellify-mcp",
-      "version": "0.1.36",
+      "version": "0.1.37",
       "transport": {
         "type": "stdio"
       },

package/skills/wordpress-import.md

@@ -72,6 +72,17 @@ Execute the plan using Stellify MCP tools in this order. This order matters —
 
 Use the `create_resources` tool with `api: false` to generate models and controllers together. The `api: false` flag ensures controller methods return data arrays (for Blade views) rather than JSON responses.
 
+**Route Model Binding with Slugs:** WordPress URLs use slugs (e.g., `/post/my-article-title`). After creating each model with a `slug` field, add a `getRouteKeyName()` method so Laravel's route model binding works correctly:
+
+```php
+public function getRouteKeyName(): string
+{
+    return 'slug';
+}
+```
+
+Add this method to **Post**, **Category**, **Tag**, and any custom post type models that use slugs in their URLs. Without this, routes like `/post/{post}` will try to look up by ID instead of slug, causing 404 errors.
+
 **If Mode A (connect to existing WordPress database):**
 
 Create resources that map to the existing WordPress tables. No migrations. Set the model's table and primary key to match WordPress.
@@ -81,7 +92,13 @@ Create resources that map to the existing WordPress tables. No migrations. Set t
 class Post extends Model {
     protected $table = 'wp_posts';
     protected $primaryKey = 'ID';
-    
+
+    // Enable slug-based route model binding (WordPress uses post_name for slugs)
+    public function getRouteKeyName(): string
+    {
+        return 'post_name';
+    }
+
     // Scope to only published posts (not revisions, drafts, etc.)
     public function scopePublished($query) {
         return $query->where('post_status', 'publish')
@@ -110,6 +127,15 @@ In Blade templates, use WordPress column names:
 
 Create new resources with clean Laravel migrations for each model identified in Step 4. Use clean column names (`title`, `slug`, `content`, `excerpt`, `status`, `published_at`, etc.). After the import is complete, suggest a data migration SQL query or artisan command that maps data from the WordPress tables to the new schema.
 
+For each model with a `slug` field, add `getRouteKeyName()`:
+
+```php
+public function getRouteKeyName(): string
+{
+    return 'slug';
+}
+```
+
 ### 5b. Refine Controller Methods
 
 `create_resources` (Step 5a) scaffolds controllers automatically. Review and refine the generated methods to ensure they query the right data. Controller methods in Stellify return data arrays — Stellify automatically merges these into the Blade view context. For example: