Назад към всички

plutonium

// High-level guide for working with Plutonium applications - read this first

$ git log --oneline --stat
stars:56
forks:11
updated:March 2, 2026
SKILL.mdreadonly
SKILL.md Frontmatter
nameplutonium
descriptionHigh-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

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:

LayerPurposeCustomize when...
ModelData, validations, associationsAdding business logic
DefinitionUI - fields, actions, filtersChanging how things look/behave
PolicyAuthorization - who can do whatRestricting access
ControllerRequest handlingRarely - use hooks if needed

Skill Reference

TopicSkill
Creating resourcesplutonium-create-resource
Connecting to portalsplutonium-connect-resource
Field configurationplutonium-definition-fields
Actions & interactionsplutonium-definition-actions
Search, filters, scopesplutonium-definition-query
Authorizationplutonium-policy
Custom viewsplutonium-views
Custom formsplutonium-forms
Nested resourcesplutonium-nested-resources
Packages & portalsplutonium-package, plutonium-portal
Authenticationplutonium-rodauth