Settings & Shortcuts Collection: Efficiency Techniques to Master

AI Navigate Original / 3/24/2026

💬 OpinionTools & Practical Usage
共有:

Key Points

  • With Claude, practical usefulness increases not only with model performance, but also by locking the output language, tone, and format
  • Remember the three most-used shortcuts—"new chat," "send," and "search"—to work more efficiently
  • Using conversation forks lets you compare and improve alternative ideas safely while preserving the original draft
  • When attaching files, specifying the set of "document role," "items to extract," and "output format" stabilizes accuracy
  • For external integrations like Zapier, using structured outputs such as Markdown and JSON makes automation easier

Introduction: Your perceived speed with Claude changes with "settings" and small tricks

Once you start using Claude every day, what matters more than the model’s performance itself isoperational speed andhow easily you can organize the conversation. Especially as of 2025, Claude is strong at reading long-form text, writing, and assisting with code, but if you use it carelessly, small losses add up—things like "previous instructions getting buried," "the conversation becoming too long," or "not getting the output format you want."

In this article, centered on convenient features that are surprisingly easy to overlook, we’ll compile practical efficiency techniques that work in day-to-day work—up toshortcuts, conversation forks, search, file attachments, locking the output language, leveraging Markdown, and external integrations like Zapier.

First, the settings to lock in: Reduce rework every time

Fix the output language and tone from the start

Claude does a good job picking up context, but as conversations grow longer, the output format can gradually drift. That’s why it’s effective to place astanding rule at the beginning of the chat.

In this conversation, please always follow the rules below.
- Answers must be in Japanese
- Use desu/masu style
- Organize in the order: headings → bullet points → conclusion
- Output in Markdown except for code
- If something is unclear, don’t guess—ask for confirmation

Even for a one-off request, simply placing these rules in the very first turn can significantly reduce the number of revision cycles afterward. If you use them often, it’s convenient to save them in a notes app or a text-expansion tool.

Lock in a “role” per project

Separating chats by purpose is also effective. For example, use them like this.

  • For writing text: prioritize readability and remove overly verbose phrasing
  • For research and organization: prioritize candidate sources, comparisons, and framing key points
  • For code assistance: make differences, error causes, and reproduction steps explicit

Rather than stuffing everything into one conversation, splitting by purpose helps stabilize Claude’s response quality.

Keyboard shortcuts: Faster just by reducing mouse movement

In Claude’s web app, there are differences depending on the environment, but using shortcuts can greatly improve your operation tempo. In particular, it’s worth learningnew chat, send, search, and moving between conversations. Confirm the exact shortcuts in the shortcut list inside the app.

Sign up to read the full article

Create a free account to access the full content of our original articles.