plutonium-package

Organize Rails application code into modular feature and portal packages.

68|10|Updated Jan 10, 2024

Search Tags:#architecture #reusability #generator #package #modular #portal #rails-engine

Ready to run

npx skills add https://github.com/radioactive-labs/plutonium-core --skill plutonium-package

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plutonium-package
Source: https://github.com/radioactive-labs/plutonium-core/tree/main/.claude/skills/plutonium-package
Command: npx skills add https://github.com/radioactive-labs/plutonium-core --skill plutonium-package

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plutonium packages help Rails teams organize large codebases into reusable, engine-based components that separate business logic from web interfaces.

Core Features & Use Cases

Feature Packages: reusable domain logic (models, definitions, policies, interactions) that can be shared across portals.
Portal Packages: portal-specific web interfaces (controllers, views, routes) for admin/dashboard interfaces.
Engine-based architecture: auto-loaded engines and proper namespacing for clean separation and reuse.

Quick Start

Install and configure the packages in your Rails app, then scaffold feature and portal packages to begin organizing your code.

Frequently Asked Questions about plutonium-package

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I organize a large Rails app into modular packages?▼

To organize Rails apps into modular packages, you scaffold engine-based feature packages for reusable domain logic and portal packages for web interfaces, integrating them via config/packages.rb to auto-load package engines.

What is the difference between feature packages and portal packages in Rails?▼

Feature packages in Rails contain reusable domain logic like models and policies for sharing across portals, while portal packages hold portal-specific web interfaces such as controllers, views, and routes for admin or dashboard interfaces.

How do I scaffold reusable domain logic and web interfaces in Rails?▼

You scaffold reusable domain logic and web interfaces in Rails by using generator commands to create feature and portal packages, which structure code into auto-loaded engines with proper namespacing for clean separation.

Can I share business logic across multiple portals in a Rails application?▼

Yes, you can share business logic across multiple portals in a Rails application by extracting it into reusable feature packages that contain domain models, definitions, policies, and interactions separate from portal-specific web interfaces.

Does organizing Rails code into packages require engine-based architecture?▼

Organizing Rails code into modular packages uses an engine-based architecture to ensure proper namespacing and clean separation, auto-loading package engines through config/packages.rb for reusable components across multiple portals.

When should I not use a modular package architecture for my Rails app?▼

You should avoid a modular package architecture for Rails apps that do not require reusable domain logic or multiple web interfaces, as scaffolding engine-based feature and portal packages adds structural overhead better suited for larger codebases.