new-context

Generate Phoenix context modules with CRUD operations for Petal Pro projects.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool automates the creation of a consistent Phoenix context module scaffold for Petal Pro projects, ensuring standardized CRUD templates, section separators, and logging conventions across contexts.

Core Features & Use Cases

  • Generates a complete context skeleton at lib/petal_pro/{ContextName}.ex with CRUD operations, changesets, and documentation comments.
  • Enforces Petal Pro conventions for naming, structure, and private helper patterns to promote maintainable, testable code.
  • Use Case: Start a new business domain by generating a ready-to-extend context with a standard API surface and error-handling scaffolds.

Quick Start

Run the scaffold to generate a new Petal Pro Phoenix context module in lib/petal_pro for the specified context name.

Frequently Asked Questions about new-context

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

FAQPage Schema
How do I scaffold a new Phoenix context module for a Petal Pro project?

To scaffold a new Phoenix context module for Petal Pro, generate a file at lib/petal_pro/{ContextName}.ex. This creates a standard API surface with CRUD operations, validation changesets, and logging patterns for your business domain.

What is included in a generated Petal Pro Phoenix context skeleton?

A generated Petal Pro Phoenix context skeleton includes standard CRUD operations, validation changesets, documentation comments, private helper patterns, and section separators to enforce consistent code organization and maintainability across the project.

Can I use this context scaffolding to enforce consistent naming and structure in Elixir projects?

Yes, the context scaffolding enforces Petal Pro conventions for naming, structure, and private helper patterns. This ensures your Elixir code remains maintainable and testable when creating new business domains.

What's the best way to start a new business domain context in Phoenix Petal Pro?

The best way to start a new business domain is to run the scaffold to generate a ready-to-extend context. This provides a standard API surface and error-handling scaffolds at lib/petal_pro/{ContextName}.ex.

Why does my Phoenix context need private helper patterns and logging conventions?

Private helper patterns and logging conventions are needed to maintain consistent code organization and testability across multiple Phoenix contexts. The scaffold applies these standard patterns automatically to reduce manual setup errors.