plutonium 0.34.1 → 0.35.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 928572413dcc6ef2e0d2e7ad258ccd1728d1d6ace9ae921abe6ae9eba89733f3
-  data.tar.gz: f94b0167a48c070d0425d5d1f42364d03786a83834b1071f791b70dfb72db421
+  metadata.gz: 81218e96d42c461a2bc5b61da7e338683b372547745ebbc177fe53ee2b5fa800
+  data.tar.gz: 960e4e769e69d71e7e081f873d1b1bfe0f4c1aaae1b155c453e83446abbe0f8d
 SHA512:
-  metadata.gz: be38ab566496a59200dbb0dfe728ae85dc7c3d9fdbfb031b7501e9ac96b4fe69139618c7077fb7ea363aafa59388aee89681903d9c4223611044c59101ab17b6
-  data.tar.gz: a1d51393fe914ddecb1b339c36a0a2d4fd8f69cc995291e4d383fdeeae815419ce1f564854e3b4aace31d119ca1eddaa687ed7d87fce7e30b1fa8db07f98ae4d
+  metadata.gz: 3ce18e3627917b3dbb7564352101bb0bd55e6a78c0bcd7fdad75e923620830f407597fc4d140659207f3346e789a74ec5d035d176520b496c6d7c4e0efa421d9
+  data.tar.gz: 5215e2e874ebdfb05bbdd997f75f68178ae7e73f81abcd47e0f0d2be771d4f2a37762fbaaec522811341bd9b4a6aafbe61e2b8a5e189b0cd68745694915cc97a

data/.claude/skills/plutonium/skill.md

@@ -0,0 +1,53 @@
+---
+name: plutonium
+description: High-level guide for working with Plutonium applications - read this first
+---
+
+# Plutonium Development Guide
+
+Read this first when working on a Plutonium application.
+
+## Core Rules
+
+1. **Always use generators** - Never manually create resources, packages, or portals
+2. **Check relevant skills first** - Each concept has a dedicated skill with details
+3. **Definitions over controllers** - UI customization belongs in definitions, not controllers
+4. **Policies for authorization** - All permission logic goes in policies
+
+## Key Generators
+
+```bash
+rails g pu:res:scaffold Post title:string --dest=main_app    # Create resource
+rails g pu:res:conn Post --dest=admin_portal                 # Connect to portal
+rails g pu:pkg:package blogging                              # Create feature package
+rails g pu:pkg:portal admin_portal                           # Create portal
+```
+
+Always specify `--dest` to avoid interactive prompts.
+
+## Resource Architecture
+
+A resource has four layers:
+
+| Layer | Purpose | Customize when... |
+|-------|---------|-------------------|
+| Model | Data, validations, associations | Adding business logic |
+| Definition | UI - fields, actions, filters | Changing how things look/behave |
+| Policy | Authorization - who can do what | Restricting access |
+| Controller | Request handling | Rarely - use hooks if needed |
+
+## Skill Reference
+
+| Topic | Skill |
+|-------|-------|
+| Creating resources | `plutonium-create-resource` |
+| Connecting to portals | `plutonium-connect-resource` |
+| Field configuration | `plutonium-definition-fields` |
+| Actions & interactions | `plutonium-definition-actions` |
+| Search, filters, scopes | `plutonium-definition-query` |
+| Authorization | `plutonium-policy` |
+| Custom views | `plutonium-views` |
+| Custom forms | `plutonium-forms` |
+| Nested resources | `plutonium-nested-resources` |
+| Packages & portals | `plutonium-package`, `plutonium-portal` |
+| Authentication | `plutonium-rodauth` |

data/.claude/skills/{assets → plutonium-assets}/SKILL.md

@@ -1,12 +1,14 @@
 ---
-name: assets
-description: Plutonium assets and theming - TailwindCSS configuration, custom styling, and component themes
+name: plutonium-assets
+description: Plutonium asset setup - TailwindCSS configuration, Stimulus controllers, and Phlexi component themes
 ---
 
-# Plutonium Assets & Theming
+# Plutonium Assets & Setup
 
 Plutonium uses TailwindCSS 4 for styling with a customizable theme system for components.
 
+> **Note:** For CSS design tokens (`--pu-*` variables) and component classes (`.pu-btn`, `.pu-input`, etc.), see the `plutonium-theming` skill.
+
 ## Asset Configuration
 
 Configure assets in the initializer:
@@ -154,9 +156,11 @@ Plutonium includes a color mode selector component that handles this automatical
 - International telephone input styles
 - Flatpickr (date picker) styles
 
-## Component Themes
+## Component Themes (Phlexi)
+
+Plutonium components use a theme system based on Phlexi for customizing Form, Display, and Table components. Each component type has a theme class with named style tokens.
 
-Plutonium components use a theme system based on Phlexi. Each component type has a theme class with named style tokens.
+> **Note:** This is different from the CSS design token system (`.pu-*` classes). For pre-built component classes, see `plutonium-theming`.
 
 ### Form Theme
 
@@ -411,6 +415,7 @@ theme: {
 
 ## Related Skills
 
-- `views` - Layout customization
-- `forms` - Form theming
-- `installation` - Initial setup
+- `plutonium-theming` - CSS design tokens and component classes (`.pu-*`)
+- `plutonium-views` - Layout customization
+- `plutonium-forms` - Form theming
+- `plutonium-installation` - Initial setup

data/.claude/skills/{connect-resource → plutonium-connect-resource}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: connect-resource
+name: plutonium-connect-resource
 description: Connect existing resources to portals for web access
 ---
 

data/.claude/skills/{controller → plutonium-controller}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: controller
+name: plutonium-controller
 description: Plutonium resource controllers - CRUD actions, customization, and integration
 ---
 
@@ -269,16 +269,30 @@ end
 
 ## Portal-Specific Controllers
 
-Each portal can have its own controller override:
+Each portal can have its own controller override. Portal controllers inherit from the feature package's controller:
 
 ```ruby
 # packages/admin_portal/app/controllers/admin_portal/posts_controller.rb
-module AdminPortal
-  class PostsController < ResourceController
-    private
+class AdminPortal::PostsController < ::PostsController
+  include AdminPortal::Concerns::Controller
+
+  private
+
+  def preferred_action_after_submit
+    "index"  # Admin prefers list view
+  end
+end
+```
+
+Controllers are auto-created if not defined. When accessing a portal resource, Plutonium dynamically creates the controller by inheriting from the feature package's controller.
 
-    def preferred_action_after_submit
-      "index"  # Admin prefers list view
+For non-resource portal pages (dashboard, settings), inherit from `PlutoniumController`:
+
+```ruby
+module AdminPortal
+  class DashboardController < PlutoniumController
+    def index
+      # Dashboard home
     end
   end
 end
@@ -294,9 +308,9 @@ end
 
 ## Related Skills
 
-- `resource` - How controllers fit in the resource architecture
-- `policy` - Authorization (used by controllers)
-- `definition-actions` - Interactive actions (preferred over custom controller actions)
-- `views` - Custom page, form, display, and table classes
-- `nested-resources` - Parent/child routes and scoping
-- `model` - Resource models
+- `plutonium-resource` - How controllers fit in the resource architecture
+- `plutonium-policy` - Authorization (used by controllers)
+- `plutonium-definition-actions` - Interactive actions (preferred over custom controller actions)
+- `plutonium-views` - Custom page, form, display, and table classes
+- `plutonium-nested-resources` - Parent/child routes and scoping
+- `plutonium-model` - Resource models

data/.claude/skills/{create-resource → plutonium-create-resource}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: create-resource
+name: plutonium-create-resource
 description: Generate Plutonium resources with models, migrations, controllers, policies, and definitions
 ---
 

data/.claude/skills/{definition → plutonium-definition}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: definition
+name: plutonium-definition
 description: Overview of Plutonium resource definitions - structure, inheritance, and best practices
 ---
 
@@ -21,7 +21,7 @@ Resource definitions configure **HOW** resources are rendered and interacted wit
 ```ruby
 class PostDefinition < Plutonium::Resource::Definition
   # Fields, inputs, displays, columns (see definition-fields skill)
-  field :content, as: :rich_text
+  field :content, as: :markdown
   input :title, hint: "Be descriptive"
   display :content, as: :markdown
   column :title, align: :center
@@ -52,7 +52,7 @@ end
 # app/definitions/post_definition.rb (resource-specific - created by scaffold)
 class PostDefinition < ResourceDefinition
   scope :published
-  input :content, as: :rich_text
+  input :content, as: :markdown
 end
 ```
 
@@ -79,7 +79,7 @@ This lets you:
 
 | Layer | Purpose | Example |
 |-------|---------|---------|
-| **Definition** | HOW fields render | `input :content, as: :rich_text` |
+| **Definition** | HOW fields render | `input :content, as: :markdown` |
 | **Policy** | WHAT is visible/editable | `permitted_attributes_for_read` |
 | **Interaction** | Business logic | `resource.update!(state: :archived)` |
 
@@ -99,7 +99,7 @@ Plutonium automatically detects from your model:
 ```ruby
 class PostDefinition < ResourceDefinition
   # 1. Override auto-detected type
-  field :content, as: :rich_text      # text -> rich_text
+  field :content, as: :markdown      # text -> rich_text
   input :published_at, as: :date      # datetime -> date only
 
   # 2. Add custom options
@@ -125,7 +125,7 @@ class PostDefinition < ResourceDefinition
   # No field declarations needed - all auto-detected!
 
   # Only customize what you need:
-  input :content, as: :rich_text
+  input :content, as: :markdown
   display :content, as: :markdown
 
   scope :published
@@ -212,7 +212,7 @@ end
 
 ## Related Skills
 
-- `definition-fields` - Fields, inputs, displays, columns
-- `definition-actions` - Actions and interactions
-- `definition-query` - Search, filters, scopes, sorting
-- `views` - Custom page, form, display, and table classes
+- `plutonium-definition-fields` - Fields, inputs, displays, columns
+- `plutonium-definition-actions` - Actions and interactions
+- `plutonium-definition-query` - Search, filters, scopes, sorting
+- `plutonium-views` - Custom page, form, display, and table classes

data/.claude/skills/{definition-actions → plutonium-definition-actions}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: definition-actions
+name: plutonium-definition-actions
 description: Add custom actions and interactions to Plutonium resources
 ---
 
@@ -145,7 +145,12 @@ end
 
 ### Bulk Action (Multiple Records)
 
+Bulk actions operate on multiple selected records at once. When a definition has bulk actions, the resource table automatically shows:
+- **Selection checkboxes** in each row
+- **Bulk actions toolbar** that appears when records are selected
+
 ```ruby
+# 1. Create the interaction (note: plural `resources` attribute)
 class BulkArchiveInteraction < Plutonium::Resource::Interaction
   presents label: "Archive Selected", icon: Phlex::TablerIcons::Archive
 
@@ -162,8 +167,26 @@ class BulkArchiveInteraction < Plutonium::Resource::Interaction
     failed("Bulk archive failed: #{error.message}")
   end
 end
+
+# 2. Register the action in the definition
+class PostDefinition < ResourceDefinition
+  action :bulk_archive, interaction: BulkArchiveInteraction
+  # bulk_action: true is automatically inferred from `resources` attribute
+end
+
+# 3. Add policy method
+class PostPolicy < ResourcePolicy
+  def bulk_archive?
+    create?  # Or whatever permission level is appropriate
+  end
+end
 ```
 
+**Authorization for bulk actions:**
+- Policy method (e.g., `bulk_archive?`) is checked **per record** - the backend fails the entire request if any selected record is not authorized
+- Records are fetched via `current_authorized_scope` - only records the user can access are included
+- The UI only shows action buttons that **all** selected records support (intersection of allowed actions)
+
 ### Resource Action (No Record)
 
 ```ruby
@@ -188,12 +211,12 @@ end
 
 ```ruby
 def execute
-  # Success with message
+  # Success with message (redirects to resource automatically)
   succeed(resource).with_message("Done!")
 
-  # Success with redirect
+  # Success with custom redirect (only if different from default)
   succeed(resource)
-    .with_redirect_response(resource_url_for(resource))
+    .with_redirect_response(custom_dashboard_path)
     .with_message("Redirecting...")
 
   # Failure with field errors
@@ -207,6 +230,8 @@ def execute
 end
 ```
 
+**Note:** Redirect is automatic on success. Only use `with_redirect_response` for a different destination.
+
 ## Interaction Context
 
 Inside an interaction:
@@ -379,8 +404,8 @@ end
 
 ## Related Skills
 
-- `definition` - Overview and structure
-- `definition-fields` - Fields, inputs, displays
-- `definition-query` - Search, filters, scopes
-- `interaction` - Writing interaction classes
-- `policy` - Controlling action access
+- `plutonium-definition` - Overview and structure
+- `plutonium-definition-fields` - Fields, inputs, displays
+- `plutonium-definition-query` - Search, filters, scopes
+- `plutonium-interaction` - Writing interaction classes
+- `plutonium-policy` - Controlling action access

data/.claude/skills/{definition-fields → plutonium-definition-fields}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: definition-fields
+name: plutonium-definition-fields
 description: Configure how resource fields are rendered in forms, show pages, and tables
 ---
 
@@ -21,7 +21,7 @@ Configure how fields are rendered using `field`, `input`, `display`, and `column
 ```ruby
 class PostDefinition < ResourceDefinition
   # field - changes type everywhere
-  field :content, as: :rich_text
+  field :content, as: :markdown
 
   # input - form-specific
   input :title,
@@ -48,7 +48,7 @@ end
 | Category | Types |
 |----------|-------|
 | **Text** | `:string`, `:text`, `:email`, `:url`, `:tel`, `:password` |
-| **Rich Text** | `:rich_text`, `:markdown` |
+| **Rich Text** | `:markdown` (EasyMDE editor) |
 | **Numeric** | `:number`, `:integer`, `:decimal`, `:range` |
 | **Boolean** | `:boolean` |
 | **Date/Time** | `:date`, `:time`, `:datetime` |
@@ -311,7 +311,9 @@ input :color_picker, as: ColorPickerComponent
 display :chart, as: ChartComponent
 ```
 
-## Column Alignment
+## Column Options
+
+### Alignment
 
 ```ruby
 column :title, align: :start    # Left (default)
@@ -319,6 +321,32 @@ column :status, align: :center  # Center
 column :amount, align: :end     # Right
 ```
 
+### Custom Column Rendering
+
+Use a block to customize how a column value is displayed. The block receives the raw record:
+
+```ruby
+column :price do |record|
+  "$#{"%.2f" % record.price}" if record.price
+end
+
+column :status do |record|
+  case record.status
+  when 'active' then "✓ Active"
+  when 'pending' then "⏳ Pending"
+  else record.status.humanize
+  end
+end
+
+column :description do |record|
+  record.description&.truncate(50)
+end
+
+column :author do |record|
+  record.author&.name || "Unknown"
+end
+```
+
 ## Nested Inputs
 
 Render inline forms for associated records. Requires `accepts_nested_attributes_for` on the model.
@@ -425,7 +453,7 @@ input :documents, as: :uppy,
 ### Rich Text Content
 
 ```ruby
-field :content, as: :rich_text    # Form: rich editor
+field :content, as: :markdown    # Form: rich editor
 display :content, as: :markdown   # Show: rendered markdown
 ```
 
@@ -467,8 +495,8 @@ Inside `condition` procs and `input` blocks:
 
 ## Related Skills
 
-- `definition` - Overview and structure
-- `definition-actions` - Actions and interactions
-- `definition-query` - Search, filters, scopes
-- `forms` - Custom form templates and field builders
-- `views` - Custom page and display templates
+- `plutonium-definition` - Overview and structure
+- `plutonium-definition-actions` - Actions and interactions
+- `plutonium-definition-query` - Search, filters, scopes
+- `plutonium-forms` - Custom form templates and field builders
+- `plutonium-views` - Custom page and display templates