What problem does it solve?
Contributors to the Phoenix CLI (px) need consistent conventions for adding or modifying commands so the tool works equally well for humans in a terminal and coding agents executing commands programmatically.
Core Features & Use Cases
- Command Structure Standards: Enforces the noun-verb pattern (
px project list), standard verbs, singular resource names, and backward-compatible migration from flat commands.
- Dual-Audience Output Rules: Defines
--format modes (pretty, json, raw), semantic exit codes, structured errors, non-interactive --no-input behavior, and idempotent mutating commands that return resources on stdout.
- Implementation Conventions: Covers Commander.js patterns, options interfaces, configuration resolution priority, I/O helpers, vitest testing with MSW mock servers, and a checklist for adding new resource commands.
- Use Case: When adding a new
px dataset get command, follow the checklist to create the command module, formatter, options interface, tests, help examples, and README updates.
Quick Start
Ask the AI to add a new noun-verb command to the Phoenix CLI following the phoenix-cli-development conventions, including formatter, tests, and help examples.