Can I use positional arguments for my CLI commands?

The skill enforces option-style arguments (e.g., --flag) to improve clarity and consistency, though positional arguments are permitted specifically for subcommands.

What runtime does this skill prioritize for CLI development?

This skill mandates the use of Bun for high-performance execution, native TypeScript support, and optimized script running.

How does this skill handle code quality?

It enforces functional programming styles (preferring map/filter over push), prohibits dummy implementations (NO-OPs), and uses Biome and Knip to ensure code cleanliness and remove unused code.

Why does this skill require tsgo instead of tsc?

It specifies @typescript/native-preview (tsgo) v7+ for specialized type checking to maintain high-performance native-preview standards, specifically prohibiting standard tsc.

CLI Tech Stack & Development Standards

Name: CLI Tech Stack & Development Standards
Author: masseater

bymasseater

Developer Tools

Standardizes CLI tool development using Bun, TypeScript, and modern ecosystem tools for high-quality terminal utilities.

About

This skill provides a comprehensive blueprint and set of guardrails for building modern, high-performance Command Line Interface (CLI) tools. It enforces a specific, opinionated tech stack—including Bun, Citty, and Biome—while mandating strict TypeScript conventions such as the prohibition of 'any' and a preference for functional programming patterns. By providing clear rules for argument handling, error management, and script execution, it ensures that terminal applications are consistent, maintainable, and robust from the first line of code.

Key Features

Promotes clean code quality through functional style and fail-fast error patterns
Enforces a modern Bun and TypeScript-based CLI development stack
0 GitHub stars
Implements strict type safety rules including the prohibition of the 'any' keyword
Standardizes command parsing and argument handling using the Citty framework
Automates high-quality formatting and linting requirements using Biome and Knip

Use Cases

Bootstrapping a new high-performance internal developer utility with Bun
Migrating a legacy Node.js CLI to a modern, type-safe TypeScript environment
Enforcing consistent coding standards and CLI argument patterns across a team

About

Key Features

Promotes clean code quality through functional style and fail-fast error patterns
Enforces a modern Bun and TypeScript-based CLI development stack
0 GitHub stars
Implements strict type safety rules including the prohibition of the 'any' keyword
Standardizes command parsing and argument handling using the Citty framework
Automates high-quality formatting and linting requirements using Biome and Knip

Use Cases

Bootstrapping a new high-performance internal developer utility with Bun
Migrating a legacy Node.js CLI to a modern, type-safe TypeScript environment
Enforcing consistent coding standards and CLI argument patterns across a team