// 315 tips tagged "productivity"
The /security-review command scans your uncommitted changes for injection vectors, auth gaps, hardcoded secrets, and other common vulnerabilities.
The /btw command lets you ask quick side questions that are answered immediately but never added to the conversation history.
The language setting makes Claude respond in your preferred language by default, across every session and project.
The attribution setting lets you customize or completely remove Claude's Co-Authored-By trailer from git commits and pull requests.
The companyAnnouncements setting surfaces team messages to every developer at startup, directly in their Claude Code session.
The --name flag sets a human-readable session name at launch, making it easy to resume specific threads later.
The --continue flag loads your most recent conversation instantly, no session ID required.
Writing AGENTS.md as plain text in CLAUDE.md has no effect — use @AGENTS.md to actually load the file into context.
Set CLAUDE_CODE_NEW_INIT in settings.json to make /init interview you for targeted improvements instead of overwriting your existing CLAUDE.md.
Before asking Claude to scaffold a new feature, point it at your existing code first — it will match your naming, structure, error handling, and test patterns exactly rather than defaulting to framework boilerplate.
Ask Claude to write property-based tests for your functions using fast-check — it identifies the mathematical invariants in your code and generates tests that cover inputs you'd never enumerate by hand.
Give Claude your OpenAPI spec and ask for a handcrafted typed API client — clean method names, custom error handling, and TanStack Query hooks, without the ugly auto-gen output.