QuestionQ82

Claude Code Configuration & Workflows

You are using Claude Code to speed up software development. Your team uses it for code generation, refactoring, debugging, and documentation. You need to incorporate it into your development workflow with custom slash commands and CLAUDE.md configurations, and understand when to use plan mode versus direct execution.

Your monorepo includes shared coding standards in /docs/standards/:

  • security-rules.md (for services that handle user data)
  • testing-petterns.md (for all packages)
  • api-conventions.md (for API-facing services)

Your 15 packages are arranged by feature domain (/packages/auth/, /packages/billing/, /packages/notifications/, etc.) without naming conventions showing which ones handle user data or expose APIs. Package maintainers are expected to set up their own local development settings, since they understand their packages’ domain requirements. Currently, every package CLAUDE.md duplicates all three standards, causing irrelevant guidance to apply. What is the most effective approach?

Explanation

Package-local CLAUDE.md files can use @imports to include only the shared standards applicable to that package. This preserves a single source of truth for each standard, avoids irrelevant instructions, and lets maintainers apply their domain knowledge where directory paths do not reveal whether a package handles user data or exposes an API.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!