Hello World
System Prompt
⚠️ EXECUTION DIRECTIVE: When the user invokes this command, you MUST:
- IMMEDIATELY execute - no questions, no explanations first
- ALWAYS show full output from script/tool execution
- ALWAYS provide summary after execution completes
DO NOT:
- Say "I don't need to take action" - you ALWAYS execute when invoked
- Ask for confirmation unless
requires_confirmation: truein frontmatter - Skip execution even if it seems redundant - run it anyway
The user invoking the command IS the confirmation.
Usage
# Simple test
/hello
# Hello with name
/hello "Claude"
This is a simple test command. When executed, simply respond with "Hello, World!".
Action Policy
<default_behavior> This command analyzes and recommends without making changes. Provides:
- Detailed analysis of current state
- Specific recommendations with justification
- Prioritized action items
- Risk assessment
User decides which recommendations to implement. </default_behavior>
Success Output
When hello command completes:
✅ COMMAND COMPLETE: /hello
Output: Hello, World!
Completion Checklist
Before marking complete:
- Greeting displayed
Failure Indicators
This command has FAILED if:
- ❌ No output displayed
Clear Examples
Example 1: Basic Hello
Input: /hello
Expected Output:
Hello, World!
✅ COMMAND COMPLETE: /hello
Output: Hello, World!
Example 2: Hello with Name
Input: /hello "Claude"
Expected Output:
Hello, Claude!
✅ COMMAND COMPLETE: /hello
Output: Hello, Claude!
Recovery Steps
If this command fails:
-
No output displayed
- Cause: Command not properly invoked
- Fix: Ensure you type
/helloexactly (slash required)
-
Error message shown
- Cause: Skill not loaded
- Fix: Run
/component-activate command hello
-
Unexpected behavior
- Cause: Arguments malformed
- Fix: Use quotes for names with spaces:
/hello "My Name"
Context Requirements
Before using this command, verify:
- Claude Code session is active
- No prior action required (this is a standalone test)
- Expected: Simple greeting output
Scope: Single-line output test only. Not for complex testing.
When NOT to Use
Do NOT use when:
- Need actual functionality (use appropriate feature commands)
- Testing complex features (use
/testor testing commands) - Debugging issues (use
/debugcommand) - Need persistent state (this command has no side effects)
Anti-Patterns (Avoid)
| Anti-Pattern | Problem | Solution |
|---|---|---|
| Expecting more | Just a test | Use for simple test only |
Principles
This command embodies:
- #3 Complete Execution - Simple execution
- #6 Clear, Understandable - Clear output
Full Standard: CODITECT-STANDARD-AUTOMATION.md