Plutonium Development - Getting Started

VerifiedSafe

Essential guide to start with Plutonium. Covers core rules, key generators, and resource architecture for efficient Plutonium application development.

Sby Skills Guide Bot
DevelopmentBeginner
306/2/2026
Claude Code
#plutonium#generators#resource-architecture#development-guide

Recommended for

Our review

This guide provides a high-level introduction to Plutonium development, covering core rules, key generators, and resource architecture.

Strengths

  • Clear presentation of core rules to avoid common pitfalls.
  • Comprehensive list of generators with concrete examples.
  • Structured explanation of resource layers (model, definition, policy, controller).
  • Quick reference to other specialized skills.

Limitations

  • Does not replace detailed skills for each concept.
  • Assumes prior knowledge of Ruby on Rails.
  • Does not cover advanced or complex configurations.
When to use it

Use as a first step before diving into Plutonium application development.

When not to use it

Do not use if you are already experienced with Plutonium and need detailed instructions on a specific aspect.

Security analysis

Safe
Quality score85/100

The skill provides high-level guidance for a Rails framework, with no destructive or exfiltrating commands. The generators shown are standard Rails generators and pose no security risk.

No concerns found

Examples

Getting started with Plutonium
I'm starting a new Plutonium application. What are the core rules and key generators I need to know?
Understanding resource architecture
Explain the different layers of a Plutonium resource (model, definition, policy, controller) and when to customize each.
List of Plutonium generators
Show me the main generators in Plutonium with examples of how to use them to create resources, packages, and portals.

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

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 |

Related skills