Claude Code Configuration & Workflows

CCAR-F · 40 questions

• A new hire on the city apps team misses coding standards that lived only in a senior's user-level CLAUDE.md. What went wrong?
• A permits monorepo needs package-specific standards without duplicating a giant root file. What CLAUDE.md technique helps?
• A transit repo's CLAUDE.md became an unmaintainable monolith covering testing, APIs, and deploy. What should the team do?
• County IT wants every teammate to receive the same Claude coding conventions automatically. Where should shared conventions live?
• A library team's Claude sessions behave inconsistently across days. How can they verify which memory files loaded?
• A school-district SIS app folder needs module-local Claude notes that should not flood the whole monorepo. What scoping fits?
• A water utility engineer has personal editor preferences and the team has mandatory coding standards. How should they be separated?
• A city team wants every clone to get the same /review checklist for pull requests. Where should the command live?
• A verbose codebase-map skill floods the main municipal chat with analysis noise. How should the skill be configured?
• A destructive-migration skill for a civic database must allow file writes but block shell execution. What frontmatter helps?
• A city deploy skill needs the service name, but engineers often invoke it with no arguments. What frontmatter helps?
• A county engineer wants a personal brainstorming skill that teammates should never inherit. Where should it live?
• A housing authority needs on-demand release notes and always-on coding standards. How should those be split?
• An engineer keeps a personal /scratch helper that must not ship in the city repo. What scope is appropriate?
• Terraform conventions for the water utility should load only when editing Terraform files. What configuration fits?
• Test conventions for a parks monorepo must apply to test files scattered across many directories. What path rule helps?
• Why prefer path-scoped .claude/rules/ over always-on subdirectory CLAUDE.md files for niche GIS conventions?
• The permits API package needs conventions that should apply when working under src/api. What should the team create?
• A civic monorepo's test conventions cut across many packages. Why choose path-specific rules over many subdirectory CLAUDE.md files?
• Projection rules for a GIS package should activate only while editing matching geo modules. What does that illustrate?
• A 45-file library migration on the city platform has unclear sequencing risks. What Claude Code mode should come first?
• A one-line null-check bug in a single municipal fee calculator is already well understood. Which approach fits?
• Discovery across a noisy legacy clerk codebase floods the main chat. How can Claude Code isolate that pass?
• A transit microservice split has several valid architecture options still under debate. What should the team start with?
• After the team agrees on a planned SIS migration sequence, what is the sensible next Claude Code step?
• A clear stack-trace hotfix points to one emergency-dispatch file with an obvious fix path. What should the engineer do?
• A multi-integration permits rewrite could waste weeks if the wrong approach is coded first. How does plan mode help?
• A civic data-migration transform keeps drifting until engineers attach two or three concrete input/output pairs. What lesson applies?
• A utility CSV normalizer should improve through failing cases rather than guesswork. What iterative pattern fits?
• Before building a cache for parcel lookups, the team wants Claude to surface invalidation tradeoffs. What pattern helps?
• Date-and-timezone bugs interact in a clerk scheduler, while lint nits are independent. How should issues be batched?
• Null parcel IDs keep escaping a assessor helper despite vague "handle edges" guidance. What should engineers supply?
• A prose-only brief for a housing ETL transform keeps flipping output formats. What is the most effective fix?
• A civic ETL team wants Claude to implement a mapper with strong behavioral coverage. What should they prepare first?
• City CI must run Claude Code without hanging on interactive prompts. Which flag pattern fits?
• City DevOps wants PR review automation to emit machine-parseable inline comments. Which Claude Code CI pattern fits?
• CI-generated tests for the permitting service keep missing fixture conventions. What should the team put in project CLAUDE.md?
• After Claude Code generates a parks-fee patch in CI, how should automated review be run?
• A housing-portal PR keeps getting the same Claude Code review comments on every re-run. What should re-reviews do?
• CI asks Claude Code to generate tests for a transit fare module that already has a suite. What context should be supplied?