Design and implementation guide for the Phoenix CLI (`px`). Covers the noun-verb command structure, dual-audience design (humans and coding agents), Commander.js patterns, configuration resolution, output formats, exit codes, and conventions for adding or modifying commands. Triggers when working on phoenix-cli commands — adding new commands, modifying existing ones, refactoring command structure, or reviewing CLI code. Also triggers on mentions of `px` commands, CLI design, or adding a new resource to the CLI.
89
96%
Does it follow best practices?
Impact
100%
1.47xAverage score across 2 eval scenarios
High
Do not use without reviewing
New resource command implementation
Noun-verb command structure
100%
100%
Singular resource name
100%
100%
Formatter file created
50%
100%
writeOutput/writeError used
0%
100%
No console.log
100%
100%
resolveConfig used
100%
100%
Shared options types reused
28%
100%
ExitCode named constants
42%
100%
Global options on verb
28%
100%
Help examples present
0%
100%
TSDoc on options fields
0%
100%
create returns resource data
100%
100%
camelCase filenames
60%
100%
PascalCase interfaces
100%
100%
Agent-friendly dataset delete command handler
--no-input flag registered
50%
100%
--no-input suppresses confirmation
100%
100%
Missing resource exits SUCCESS
100%
100%
StructuredError on --format raw/json
40%
100%
ExitCode named constants used
100%
100%
Deleted resource returned on stdout
100%
100%
Progress to stderr via writeProgress
37%
100%
Actionable error message with syntax
62%
100%
No console.log usage
100%
100%
DESIGN.md covers non-interactive behavior
100%
100%
DESIGN.md covers missing dataset behavior
100%
100%
DESIGN.md covers structured error output
50%
100%
d9421a4
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.