Claude Command Workflows – Projects, Artifacts, and Claude Code Direction
Lesson 1: Command Thinking in Claude – Prompts, Buttons, and Slash Commands
Lesson Objectives
By the end of this lesson, students should be able to:
- Distinguish natural-language requests, interface features (buttons and menus), and slash commands.
- Use command-style phrasing to make requests predictable.
- Write a fallback request when a command is not available.
Lesson Content
People say "command" for three different things in Claude:
- Natural-language requests: "Summarize this in five bullets." This is a prompt. It works everywhere.
- Interface features: buttons and menus such as attaching files, choosing a Project, turning on web search, or opening an Artifact. Availability depends on your plan and device.
- Slash commands: typed controls, mostly in Claude Code, such as
/compact,/clear,/memory, or/init. They control the session rather than ask for content. The exact list depends on the product and version; type/to see what is available.
Command-style phrasing makes natural-language requests predictable: start with a verb, name the input, the output format, and a limit. "Extract all deadlines from this email as a bullet list with dates." "Review this draft for unsupported claims only; do not rewrite."
When a feature or command is missing, write a fallback request that describes what it would have done.
Enroll to continue this lesson.
The preview above shows the lesson objectives and opening lesson content. Enroll to view the full lesson, complete the practice work, and take the lesson quiz.