command-development

Create Claude Code slash commands with Markdown, YAML frontmatter, and agent prompts.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/NGTPTE/TuriX-MarketPlace --skill command-development-ngtpte
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: command-development
Source: https://github.com/NGTPTE/TuriX-MarketPlace/tree/main/plugins/plugin-dev/skills/command-development
Command: npx skills add https://github.com/NGTPTE/TuriX-MarketPlace --skill command-development-ngtpte

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It removes the guesswork from creating Claude Code slash commands by teaching how to structure command files, configure metadata, and write prompts that reliably instruct the agent.

Core Features & Use Cases

  • Command File Fundamentals: Learn how Markdown command files, locations, and namespacing work across project, personal, and plugin scopes.
  • Frontmatter and Arguments: Configure descriptions, tool access, model selection, and dynamic inputs with positional arguments or argument strings.
  • File, Bash, and Plugin Integration: Use file references, inline shell execution, plugin-root paths, and component-aware patterns for richer workflows.
  • Best Practices and Validation: Build safer, more maintainable commands with restrictive tools, clear error handling, testing strategies, and documentation patterns.
  • Use Case: A team can create a reusable review command that reads changed files, runs git-aware checks, and produces consistent feedback without rewriting the workflow each time.

Quick Start

Ask the AI to help you design a Claude Code slash command for a specific workflow, including the command prompt, frontmatter, arguments, and any plugin-specific files it should use.

Frequently Asked Questions about command-development

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

FAQPage Schema
How do I create Claude Code slash commands with custom arguments and YAML frontmatter?

To create Claude Code slash commands, you structure Markdown command files with correct YAML frontmatter to configure metadata, tool access, and model selection, while defining dynamic inputs using positional arguments or argument strings for reliable agent instruction.

What is the best way to structure a multi-step Claude Code command that runs bash execution?

The best way to structure multi-step Claude Code commands is using Markdown files that incorporate inline bash execution, file references, and agent-oriented prompt instructions, ensuring you apply restrictive tool patterns and clear validation for maintainable workflows.

Can I use file references and plugin-scoped resources when building slash commands?

Yes, you can use file references, inline shell execution, and plugin-root paths when building slash commands. The command structure supports component-aware patterns and plugin-scoped resources to enable richer, context-specific workflows within your project.

How does command namespacing work across project, personal, and plugin scopes in Claude Code?

Command namespacing in Claude Code works by organizing Markdown command files across project, personal, and plugin scopes, allowing teams and individuals to separate custom command workflows and access appropriate plugin-scoped resources based on the operational context.

Why are my Claude Code plugin commands failing to execute bash scripts correctly?

Claude Code plugin commands may fail due to incorrect Markdown structure, missing YAML frontmatter, or overly broad tool permissions. Ensure your commands include restrictive tool patterns, clear error handling, and proper validation to produce reliable execution.