Slash Commands: Built-Ins And Custom

End-of-lesson check

15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-claude-code-slash-commands-creators

1. What is the core idea behind "Slash Commands: Built-Ins And Custom"?

   1. Slash commands are the keyboard shortcuts of Claude Code. The built-ins handle plumbing; the custom ones are where teams encode their workflows.
   2. system prompt
   3. Hand-offs — you can stop and resume because the list is the state
   4. It plans, then executes — reading files, editing files, running commands

2. Which term best describes a foundational idea in "Slash Commands: Built-Ins And Custom"?

   1. /compact
   2. slash command
   3. custom command
   4. workflow

3. A learner studying Slash Commands: Built-Ins And Custom would need to understand which concept?

   1. slash command
   2. custom command
   3. /compact
   4. workflow

4. Which of these is directly relevant to Slash Commands: Built-Ins And Custom?

   1. slash command
   2. /compact
   3. workflow
   4. custom command

5. Which of the following is a key point about Slash Commands: Built-Ins And Custom?

   1. /review — runs a checklist for the current changes (lint, tests, conventions, security)
   2. /spike — generates a throwaway prototype script in a sandbox folder
   3. /changelog — drafts a CHANGELOG entry from the diff
   4. /perf — runs a perf harness on a function and reports the numbers

6. Which of these does NOT belong in a discussion of Slash Commands: Built-Ins And Custom?

   1. /changelog — drafts a CHANGELOG entry from the diff
   2. /review — runs a checklist for the current changes (lint, tests, conventions, security)
   3. system prompt
   4. /spike — generates a throwaway prototype script in a sandbox folder

7. Which statement is accurate regarding Slash Commands: Built-Ins And Custom?

   1. Write a prompt that describes the workflow precisely
   2. Save it as a custom slash command in `.claude/commands/`
   3. Pick a workflow you do every week (review, deploy, changelog)
   4. Run it three times; refine the prompt

8. Which of these does NOT belong in a discussion of Slash Commands: Built-Ins And Custom?

   1. system prompt
   2. Pick a workflow you do every week (review, deploy, changelog)
   3. Save it as a custom slash command in `.claude/commands/`
   4. Write a prompt that describes the workflow precisely

9. What is the key insight about "/compact is the daily move" in the context of Slash Commands: Built-Ins And Custom?

   1. On any session running more than 30 minutes, /compact roughly every 30-50k tokens of context.
   2. system prompt
   3. Hand-offs — you can stop and resume because the list is the state
   4. It plans, then executes — reading files, editing files, running commands

10. What is the key insight about "Don't make commands you don't use" in the context of Slash Commands: Built-Ins And Custom?

    1. system prompt
    2. Custom commands sprawl easily. A repo with 20 slash commands no one remembers is worse than one with 4 that everyone run…
    3. Hand-offs — you can stop and resume because the list is the state
    4. It plans, then executes — reading files, editing files, running commands

11. What is the key insight about "From the community" in the context of Slash Commands: Built-Ins And Custom?

    1. system prompt
    2. Hand-offs — you can stop and resume because the list is the state
    3. On r/ClaudeAI, power users repeat one rule of thumb for custom commands: anything you do more than once a day should bec…
    4. It plans, then executes — reading files, editing files, running commands

12. Which statement accurately describes an aspect of Slash Commands: Built-Ins And Custom?

    1. system prompt
    2. Hand-offs — you can stop and resume because the list is the state
    3. It plans, then executes — reading files, editing files, running commands
    4. Slash commands are special inputs starting with / that trigger meta-actions instead of going to the model.

13. What does working with Slash Commands: Built-Ins And Custom typically involve?

    1. Custom commands let your team encode 'the way we do X' as a runnable name. They live in your project (typically under a `.
    2. system prompt
    3. Hand-offs — you can stop and resume because the list is the state
    4. It plans, then executes — reading files, editing files, running commands

14. Which of the following is true about Slash Commands: Built-Ins And Custom?

    1. system prompt
    2. The big idea: slash commands turn 'how we work' into a one-keystroke entry point.
    3. Hand-offs — you can stop and resume because the list is the state
    4. It plans, then executes — reading files, editing files, running commands

15. Which best describes the scope of "Slash Commands: Built-Ins And Custom"?

    1. It is unrelated to tools workflows
    2. It applies only to the opposite beginner tier
    3. It focuses on Slash commands are the keyboard shortcuts of Claude Code. The built-ins handle plumbing; the custom
    4. It was deprecated in 2024 and no longer relevant