skills.rest
agentxm
agentxmOFFICIAL
Explore all skills by this author →
Website𝕏@agentxm_aiGitHub

cli-conventions

Define standardized Effect-based CLI command structures with parsing and logic separation.

5|Updated Jan 29, 2026
Search Tags:#testing#architecture#cli#commands#flags#effect
One-click install
npx skills add https://github.com/agentxm/axm --skill cli-conventions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cli-conventions
Source: https://github.com/agentxm/axm/tree/main/.claude/skills/cli-conventions
Command: npx skills add https://github.com/agentxm/axm --skill cli-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes a standardized approach to designing CLI commands with Effect-based architectures, reducing inconsistencies and onboarding time across projects.

Core Features & Use Cases

  • Architecture guidance for separating CLI parsing (commands, flags) from business logic (handlers)
  • Patterns for arguments and flags (required/optional positionals, multi-value flags, defaults, aliases)
  • Reference implementation guidance and patterns to accelerate new command creation
  • Real-world use cases like creating a leaf command to install, list, or configure subcommands

Quick Start

Create a new CLI command by applying the leaf-command pattern and wiring arguments, flags, and a handler.

Frequently Asked Questions about cli-conventions

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

FAQPage Schema
How do I structure Effect CLI commands to separate argument parsing from business logic?▼

Effect CLI commands require separating parsing logic, such as arguments and flags, from handler logic to ensure predictable behavior and maintainable command architectures. This convention enforces that boundary strictly.

What is the best way to define optional flags and multi-value arguments in an Effect CLI?▼

Defining arguments and flags in an Effect CLI involves standardized patterns for required and optional positionals, multi-value flags, defaults, and aliases to ensure consistent command interfaces across the project.

How do I create a leaf command for an Effect-based CLI tool?▼

Creating a leaf command involves applying a standardized pattern that wires arguments, flags, and a handler together, providing reference implementation guidance to accelerate new command creation for tasks like install or list.

Does the Effect CLI library support testing scenarios for command flags and handlers?▼

Yes, Effect CLI conventions specify testing scenarios to verify predictable behavior for commands, ensuring that argument parsing and handler execution function correctly within the Effect ecosystem.

Why should I use standardized conventions for building Effect-based CLI commands?▼

Standardized conventions for Effect-based CLI commands reduce inconsistencies across projects and significantly lower onboarding time by providing a predictable structure for subcommands, error handling, and architecture.

Related Skills

Explore More Software Engineering Skills→
DevMHOneDevMHOne

cli-plugins-skills

Manage Omni Skills, plugins, and persistent memory from the CLI.

Community
Intermediate
mdelapenyamdelapenya
21

lpn CLI Tester

Automate testing of the lpn CLI tool for Liferay Portal Docker images.

Community
Advanced
timmo001timmo001
5

effect

Create, manage, and validate TypeScript services with Effect's typed functional approach.

Community
Advanced
constructive-ioconstructive-io

inquirerer-cli

Develop interactive command-line interfaces with inquirerer, appstash, and yanse.

Official
Intermediate