CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Repository Purpose

This is a personal career documentation repository for maintaining a "brag document" - a weekly/monthly record of professional accomplishments, projects, technical achievements, and career growth.

File Structure

BragDocument.md - Main document tracking career achievements organized chronologically (year → month → week)

Workflow: Weekly Brag Document Update

When the user requests a brag document update, follow this interview process:

1. Initial Questions

What projects or initiatives have you been working on this week?
For each project mentioned, ask follow-up questions:
- What is the purpose/context of this project?
- What technical work did you do?
- Were there any challenges or interesting problems you solved?
- What's the current status? (complete, deployed, in progress)

2. Impact & Results Questions

What was the impact or benefit of this work?
Any quantifiable outcomes? (metrics, workload reduction, efficiency gains)
Is it being used? By whom?

3. Skills & Learning Questions

Any new skills, tools, or technologies learned or deepened?
Any domain knowledge gained?

4. Collaboration Questions

Are you working solo or with a team?
Any mentoring, helping others, or leadership activities?

5. Recognition Questions

Any positive feedback, recognition, or praise received?
Feature requests or follow-up work generated by your accomplishments?

6. Other Work

Any other notable work? (bug fixes, code reviews, meetings, housekeeping, refactoring)
Roughly how much time spent on each area of work?

7. Document Update

Once you have enough information, update BragDocument.md under the current week's section with these categories:

Projects & Initiatives - High-level summary of what was worked on Technical Achievements - Specific technical problems solved, architecture decisions, implementation details Impact & Results - Business value, operational improvements, user benefits Skills Developed - New knowledge or deepened expertise Collaboration & Leadership - Team work, helping others, independent execution Recognition - Feedback, praise, or follow-up requests

Writing Style

Use bold for project/feature names
Include context (what/why) along with accomplishments
Focus on impact and outcomes, not just activities
Be specific about technologies, systems, and domains
Frame accomplishments positively and professionally
Quantify when possible (number of documents, days spent, users affected)

Adding New Time Periods

When starting a new week/month, add a new dated section at the top of the current month, or create a new month section if needed. Keep the template at the bottom of the document for reference.

2.8 KiB Raw Blame History