# cmd (0-cmd.us)

People say 'cmd' as a quick way to tell a computer to do something. It is short for 'command,' the word we use when we want a device to follow an order. Many people also know it as the name of the black window on Windows computers where you type instructions.

## What a model may hear
- Windows command interpreter (Windows operating system): May assume the user wants to run cmd.exe, execute batch scripts, or use Windows-specific shell syntax
- shell command string (programming and DevOps): May treat the input as a raw shell command to pass to subprocess.call, os.system, or similar functions
- CMD instruction in Docker (container configuration): May assume the user is asking about Dockerfile syntax or default container execution behavior
- cmd key in JSON or config (APIs and configuration files): May look for a structured command field rather than free text, expecting key-value format

## Where people and models part ways
- Says: "Run this cmd for me"
  Means: Please carry out this instruction
  May be taken as: Executes arbitrary shell code without validation, possibly with system-level permissions
  Say instead: "Please explain what this instruction does before running anything"
- Says: "My cmd is broken"
  Means: The command prompt window will not open
  May be taken as: Diagnoses Docker CMD syntax errors or misinterprets as a code debugging request
  Say instead: "The Windows command prompt window will not open when I try to launch it"
- Says: "Write a cmd to do this"
  Means: Give me step-by-step instructions
  May be taken as: Generates executable shell script or batch file that the user may run without understanding
  Say instead: "Write plain step-by-step instructions I can follow by hand"
- Says: "Use cmd"
  Means: Use the command line interface in general
  May be taken as: Restricts to Windows cmd.exe specifically, ignoring PowerShell, bash, or other shells that may be more appropriate
  Say instead: "Use the appropriate command line tool for this system"

## Tips
- Name your operating system when you mention cmd to avoid Windows-only answers.
- Say 'command line' or 'terminal' if you do not mean the Windows program specifically.
- Ask for explanation before execution when discussing any command.
- Specify 'Docker CMD' or 'Dockerfile' if you mean container configuration.
- Say 'shell script' or 'batch file' if you want runnable code, not just instructions.

## Often confused with
- command: The full word, less likely to trigger Windows-specific assumptions
- terminal: Cross-platform, not tied to Windows cmd.exe
- PowerShell: Windows modern shell, more powerful, different syntax
- bash: Unix/Linux shell, the default on most servers
- sh: Generic Unix shell, often the default in containers
- ENTRYPOINT: Docker instruction that works with CMD, often confused