The all-caps `clod` file, created via the `init` command, stores project structure and user-defined rules. Unlike temporary in-chat instructions that get lost or degraded as the conversation continues, this file is referenced in every session, ensuring consistent behavior and enforcing project-wide guardrails.

By running development and knowledge tools like Claude Code on a home server and accessing them via a secure personal VPN like Tailscale, you can transform a mobile phone into a powerful terminal for deep work, including coding and research, from anywhere.

Instead of manually providing context in each prompt, use Claude Code's 'append system prompt' command. This preloads crucial information, like architectural diagrams, at the start of a session, leading to faster and more accurate AI responses without repeated file reads.

Claude Code's terminal-based interaction within a specific folder allows it to automatically read and reference local files. This makes "context engineering" drastically faster and more powerful than manually pasting information into a traditional chat interface, as the context is implicitly understood.

Instead of managing prompts in a separate library, save them as custom commands directly within your Claude Code project folder. This lets you trigger complex, multi-file prompts with a simple command (e.g., `/meeting_notes`), embedding powerful, recurring workflows directly into your development environment.

Use the Claude chat application for deep research on technical architecture and best practices *before* coding. It can research topics for over 10 minutes, providing a well-summarized plan that you can then feed into a dedicated coding tool like Cursor or Claude Code for implementation.

For recurring AI tasks, such as loading project-specific diagrams or switching models in Claude Code, create short shell aliases (e.g., 'cdi' for 'Claude diagram load'). This avoids retyping long commands and allows you to quickly switch contexts or modes.

The terminal-first interface of Claude Code wasn't a deliberate design choice. It emerged organically from prototyping an API client in the terminal, which unexpectedly revealed the power of giving an AI model direct access to the same tools (like bash) that a developer uses.

Instead of jumping between apps, top PMs use a central tool like Claude Desktop or Cursor as a 'home base.' They connect it to other services (Jira, GitHub, Sanity) via MCPs, allowing them to perform tasks and retrieve information without breaking their flow state.