Agency Repo Structure & Claude Optimization

Atlas Development Log — Agency Repo Structure & Claude Optimization

Overview

Analyzed the agency monorepo structure with focus on optimizing for Claude Code's .claude folders and CLAUDE.md files. Created a /daily-notes slash command for automated end-of-session documentation that integrates with the blog's dev logs system.

1. Objectives

• Analyze current repo structure for Claude configuration gaps
• Compare implementation against proposed structure in Agency Repo.md
• Create automated daily notes generation command

Success looks like: Clear recommendations for CLAUDE.md placement and a working /daily-notes command that generates properly formatted dev logs.

2. Key Developments

Technical Progress:

• Explored entire monorepo using Task agent (comprehensive structure analysis)
• Identified .claude folder locations across all products
• Found only 2 CLAUDE.md files exist (one empty) despite multiple products
• Created /daily-notes slash command for session documentation

System / Agent Improvements:

• Mapped 10-agent taxonomy from Agency Repo.md to current 4-role Agent OS
• Identified path for migrating core/standards/ to .claude/skills/

Integrations Added:

• /daily-notes command integrates with dev_logs collection for Daily Notes section

3. Design Decisions

Root-Level CLAUDE.md Recommendation

• Decision: Recommended creating a root CLAUDE.md with agency-wide context
• Rationale: Currently missing, would provide consistent context for all products
• Alternative considered: Relying solely on global ~/.claude/CLAUDE.md
• Trade-off: Additional file to maintain, but provides repo-specific context

Standards-to-Skills Migration Path

• Decision: Recommended moving core/standards/ content into .claude/skills/
• Rationale: Makes standards automatically available as Claude skills
• Alternative considered: Keeping standards separate and referencing via links
• Trade-off: Duplication of content structure, but better Claude integration

Daily Notes Command Location

• Decision: Placed command in root .claude/commands/ folder
• Rationale: Agency-wide utility, not product-specific
• Alternative considered: Placing in each product's .claude/commands/
• Trade-off: Single location means it works everywhere in the monorepo

4. Challenges & Solutions

daily-notes.njk Template Reference

• Problem: Initial reference to @daily-notes.njk file that didn't exist
• Root cause: Template was conceptual, not yet created
• Solution: Used existing dev_logs posts as reference for correct frontmatter format

Correct Collection Placement

• Problem: Initially saved to posts/ instead of dev_logs/
• Root cause: Didn't check eleventy config for collection definitions
• Solution: Read .eleventy.js to confirm dailyNotes collection pulls from dev_logs/

5. Code Changes

6. Next Steps

• Create root-level CLAUDE.md with agency structure documentation
• Add CLAUDE.md to youtube_scout product
• Add CLAUDE.md to local_business_scout/v2 product
• Consider migrating core/standards/ to .claude/skills/
• Populate the 10 agents from Agency Repo.md into .claude/agents/

7. Session Notes

• The monorepo is well-structured with clear separation of concerns
• Agent OS template is mandatory for new projects (good governance)
• The 3-Layer Context Architecture from AGENCY_AGENT_FRAMEWORK.md is solid
• Gap between proposed structure (Agency Repo.md) and implementation suggests aspirational architecture not yet fully realized
• Daily notes serve dual purpose: personal documentation and public blog content demonstrating work