Lots of updates

.claude/commands/local-build-resume.md

@@ -0,0 +1,99 @@
+# /build-resume
+
+## Description
+
+Generate a tailored resume based on the provided job descriptoin and my existing background. Use the file with detailed in it's name as context for my experience. Optimize keywords and align experience with job requirements. Format the output for ATS (Applicat Tracking Systems) compatibility
+
+### Profile Summary
+
+- Seeking: Backend/Application/Security/Systems Programming roles (Jr-Mid level ONLY)
+- Level: Jr-Mid developer (level 1-2) - NO Senior/Sr/Staff/Founding titles
+- Requirements: Remote, no on-call, $130k+, low responsibility, no mentoring/management
+- Key Skills: Rust, Python, C, GoLang, MySQL, Docker, REST APIs, Security, CI/CD
+- Also open to: Other remote roles (non-dev) that pay well and are learnable short-term
+
+## Usage
+- Either paste the entire description OR link to the job description immediatly after the command
+
+## Workflow
+
+### Step 1: Analyze the Job Description
+- Extract the top 5-8 hard skills and soft skills required.
+- Identify the core problems the company is trying to solve with this role.
+- Note specific keywords, technologies, and metrics emphasized in the text.
+- Verify with user if anything undesirable flags with the description before continuing
+
+### Step 2: Create the directory structure
+- Create or use the directory with the company name
+- Create a subdirectory of the job title
+- Inside, put a markdown file of the job description
+- Put the resume with name paul-halvorsen-resume.md
+- Put the coverletter with name paul-halvorsen-cover-letter.md
+- Put the analysis in job-breakdown.md
+- When building with make, the pdfs of the resume and cover letter will be here as well
+
+### Step 3: Tailor the Resume Content
+- **Professional Summary:** Rewrite to directly address the company's mission and the role's primary objectives using the extracted keywords.
+- **Skills Section:** Reorder and prioritize skills to match the job description's hierarchy.
+- **Experience Bullets:**
+  - Rewrite bullet points to highlight achievements that mirror the job requirements.
+  - Use the "Action Verb + Task + Result (with Metrics)" formula.
+  - Ensure specific keywords from the JD appear naturally in the context of your past work.
+- **Gap Analysis:** If the user provided their current resume, identify missing skills or experiences and suggest how to frame existing experience to cover those gaps.
+- **Metadata Header:**
+    - Always include the following: Email, Phone, Git, Blog, LinkedIn
+        - Include the title of each value
+    - Include "Citizen of the United States"
+
+### Step 4: Formatting & Output
+- Generate the resume in **Markdown** format (for easy conversion to PDF/Word).
+- Ensure clean hierarchy (H1 for Name, H2 for Sections).
+- Keep it to a maximum of 2 pages (simulated by content density).
+- Include a "ATS Optimization Score" estimate at the top based on keyword matching.
+- Chronological work experience (details of older positions can be greatly reduced to save space)
+
+### Step 5: Cover Letter
+- Briefly draft a 3-paragraph cover letter hook that connects the user's specific value proposition to the company's stated needs.
+- If the position is below general experience level, note that in the cover letter and specify that the position is being looked at to provide greater field breadth
+- Be up front about gaps and provide reasons that previous experience will cover those gaps
+
+### Step 6: Build the pdfs
+- Use `jb2resume-modern` theme
+- Build Resume Command: `make resume-modern FILE_NAME=path/to/resume`
+- Build Cover Letter Command: `make resume-modern FILE_NAME=path/to/coverletter`
+
+## Constraints & Guidelines
+- **Tone:** Professional, confident, and concise.
+- **Truthfulness:** Do not invent experiences. If a skill is missing, suggest phrasing like "Familiar with..." or "Exposure to..." rather than claiming expertise.
+- **Metrics:** Prioritize quantifiable results (e.g., "Increased efficiency by 20%") over vague descriptions.
+- **Privacy:** Remind the user to replace placeholders like `[Phone Number]`, `[Email]`, and `[City, State]` with their actual data before sending.
+- **Hard Requirements:**
+    - Remote only
+    - No on-call rotations (flag before proceeding if description mentions on-call, pager duty, 24x7, "total ownership", "you own it in production", or similar)
+    - $100k+
+    - No management responsibilities
+- **Soft Requirements:**
+    - No mgmt/mentoring
+    - No mentoring responsibilities
+    - Jr or Mid level only (level 1-2) - no senior/sr/staff/principal/founding/lead titles
+    - $130k+
+- **Preferences**
+    - Low responsibility
+    - backend/application/security/systems programming focus
+    - Willing to take mid-level to learn new problem space or tech stack
+    - Willing to take lower salary to learn new problem space or tech stack
+- **On-call flag protocol**
+    - Before creating resume/cover letter materials, flag any job description language that implies on-call:
+        - Explicit: "on-call rotation", "pager duty", "24x7"
+        - Implicit: "total ownership", "you own systems in production", "production accountability", "incident response"
+    - Ask user whether to proceed before continuing.
+
+
+## Example Interaction
+**User:** `/build-resume` [Paste Job Description] OR [Paste link to Job Description]
+
+**AI Response:**
+1. **Analysis:** "I've analyzed the Senior Python Engineer role. Key focus areas are AWS Lambda, Django, and scaling microservices..."
+2. **Resume Draft:** Create the resume in 
+3. **Cover Letter Hook:** [Brief draft]
+4. **Next Steps:** "Review the 'Skills' section to ensure the AWS certifications are prominent. Would you like me to generate a specific cover letter?"