Files
my-vault/.claude/commands/create-command.md
T
windyboy be56d86e84 refactor(vault): Phase 5 — single agent contract
- Rewrite AGENTS.md as single operations manual (PARA, permission table,
  frontmatter conventions, safety rules, code style)
- Root CLAUDE.md = one-line pointer to AGENTS.md
- Delete 13 stub CLAUDE.md files across vault directories
- Delete .claude/project-instructions.md + .claude/memory/instructions/
  (content merged into AGENTS.md)
- .claude/settings.json: deny plugin data.json + 04_Archive + git push;
  ask on .obsidian/** edits; remove SessionStart hook (claudesidian welcome)
- Delete 3 upstream commands (init-bootstrap, install-claudesidian, upgrade)
- Add risk/writes metadata to 14 remaining commands
- Rewrite README.md (remove all claudesidian content)
- package.json: name → my-vault, remove check-updates/firecrawl scripts
2026-09-26 11:41:32 +08:00

1.4 KiB

risk: low writes: .claude/commands/


allowed-tools: Write, Read, Bash(ls:, mkdir:), Edit description: Create a new Claude Code slash command argument-hint: [command details or description]

Create New Slash Command

I'll help you create a new Claude Code slash command.

Your Input

Command Details: $ARGUMENTS

Process

  1. Understand Requirements

    • What should the command do?
    • What tools does it need?
    • What output should it produce?
  2. Design Structure

    • Command name (kebab-case)
    • Required tools
    • Input arguments
    • Output format
  3. Create Command File

    • Location: .claude/commands/[command-name].md
    • Include proper frontmatter
    • Clear instructions
    • Example usage

Command Template

---
allowed-tools: [List tools needed: Read, Write, Edit, Bash, etc.]
description: [One-line description]
argument-hint: [What user should provide]
---

# Command Name

Brief description of what this command does.

## Task

[Clear description of the task]

## Process

1. [Step 1]
2. [Step 2]
3. [Step 3]

## Output

[Expected output format]

## Example Usage

\`\`\` claude run [command-name] [arguments] \`\`\`

Best Practices

  • Keep commands focused on one task
  • Use clear, descriptive names
  • Include example usage
  • Document required arguments
  • Specify output format
  • List needed tools in frontmatter

Let me help you create your command!