Plutonium Development Guide

VerifiedSafe

This high-level guide provides the foundational rules and conventions for building Plutonium applications. It covers the four-layer resource architecture, essential code generators for resources and portals, and directs developers to more specialized skills for definition fields, policies, and authentication.

Sby Skills Guide Bot
DevelopmentIntermediate
6/2/2026
Claude Code
#plutonium#rails#generators#resources#guide

Recommended for

Automated summary

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

Strengths

  • Structured introduction to key Plutonium concepts
  • Quick reference to generators and resource architecture
  • Links to more specific skills

Limitations

  • Does not contain detailed implementation specifics
  • Assumes prior knowledge of Ruby on Rails
When to use it

When starting a new Plutonium project or needing an overview of the architecture.

When not to use it

If you need detailed instructions on a specific feature (e.g., field configuration) - refer to the dedicated skill instead.

Security analysis

Safe
Quality score90/100

The skill provides guidance for development with Plutonium, including standard Rails generator commands. There are no destructive, exfiltrating, or obfuscated actions. Commands are typical development tasks and do not involve risky patterns like piping to shell, deleting files, or disabling safety.

No concerns found

How this analysis is made

Examples

Get started with Plutonium
I'm starting a new Plutonium project. Give me an overview of the framework's architecture and the key generators I should use.
Resource creation guidance
Explain how to create a new resource in Plutonium, including the four layers (model, definition, policy, controller) and which generators to use.
Skill reference navigation
What are the available Plutonium skills? I need to understand how to configure fields for a definition.

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 |

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/plutonium-development-guide-mma3jqs0/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/plutonium-development-guide-mma3jqs0' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/plutonium-development-guide-mma3jqs0/download' --output '.skill-downloads/plutonium-development-guide-mma3jqs0/SKILL.md.part' && mv '.skill-downloads/plutonium-development-guide-mma3jqs0/SKILL.md.part' '.skill-downloads/plutonium-development-guide-mma3jqs0/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/plutonium-development-guide-mma3jqs0/SKILL.md' && test -s '.skill-downloads/plutonium-development-guide-mma3jqs0/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/plutonium' && cp -R '.skill-downloads/plutonium-development-guide-mma3jqs0' '.claude/skills/plutonium'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/plutonium-development-guide-mma3jqs0'

openskills read 'plutonium-development-guide-mma3jqs0'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/plutonium-development-guide-mma3jqs0/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills