add-org-feature

Scaffolds org-scoped Phoenix app features with schema, LiveView pages and routes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/johngrandson/orkestry --skill add-org-feature
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-org-feature
Source: https://github.com/johngrandson/orkestry/tree/main/.claude/skills/add-org-feature
Command: npx skills add https://github.com/johngrandson/orkestry --skill add-org-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scaffolds a new org-scoped feature for a multi-tenant Phoenix app, creating schema with org_id, a context module, a migration, org-scoped LiveView pages, routes, and GDPR updates.

Core Features & Use Cases

  • Org-scoped resource scaffolding, including schema, migration, context, routes, and LiveViews
  • Enforces org scoping in queries and provides GDPR integration for resources with user data
  • Use Case: Add a new resource to an organization and expose it via org-scoped routes with admin controls

Quick Start

Follow the described steps to scaffold a new org-scoped feature in your multi-tenant Phoenix app.

Frequently Asked Questions about add-org-feature

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

FAQPage Schema
How do I add an org-scoped feature to a multi-tenant Phoenix app?

To add an org-scoped feature in a multi-tenant Phoenix app, you scaffold a schema with org_id, a context module, a migration, org-scoped LiveView pages, routes, and GDPR updates to enforce org-wide CRUD workflows and access control.

What is org scoping in Elixir and when do I need it for CRUD workflows?

Org scoping in Elixir restricts database queries and resources to a specific organization using an org_id. You need it when building multi-tenant Phoenix applications that require org-wide CRUD workflows, admin controls, and isolated data access.

How do I scaffold a new resource with org_id and GDPR handling in Ecto?

Scaffolding a new resource with org_id and GDPR handling in Ecto involves creating a migration and schema with org_id, a context module for scoped queries, and integrating GDPR updates for resources containing user data.

Can I use this scaffolding approach with any Elixir Phoenix project?

This scaffolding approach requires an Elixir Phoenix project using PetalPro patterns. Your project must have properly configured migrations and org routes to support the generated org-scoped LiveViews and admin access controls.

Does adding an org feature automatically include GDPR data handling for users?

Adding an org feature includes GDPR integration for resources with user data. The scaffolding process updates GDPR handling alongside creating the org-scoped schema, context, and LiveViews to ensure compliance across the new organization resource.

How do LiveView routes handle org admin access control in Phoenix?

LiveView routes handle org admin access control in Phoenix by applying on_mount hooks when required. This enforces admin permissions within the org-scoped routes, securing the generated CRUD workflows for the specific organization.