This is what I'm currently working on. The idea is to link up connecters to it such as hubspot, M365 and any other relevant support systems/ shared knowledge bases. I've currently got it as human in the loop so it has to be fed support requests and it never directly responds to customers. It's also building up a knowledge base of SOP's and responses as it goes. support-agent/ ├── CLAUDE.md ├── triage/ │ └── CONTEXT.md ← Dynamic: ticket analysis ├── drafting/ │ ├── CONTEXT.md ← Dynamic: response composition │ ├── templates/ │ │ ├── response-template.md │ │ └── escalation-template.md │ └── archive/ ← Approved responses (grows from use) ├── sops/ │ ├── CONTEXT.md ← Static: SOP library │ ├── _template/ │ │ └── sop-template.md │ └── [your-categories]/ │ └── issue-description_sop.md └── knowledge-base/ ├── CONTEXT.md ← Static: reference library ├── product/ ├── policies/ └── faqs/ I'm still working through the CLAUDE.md and CONTEXT.md to get them to where I'm happy with them. Let me know what you think and if anything could be done different or added to it.

Made it to Level 2!! I'm working on some ideas and folder structures that I'd like to share. Are we allowed to share github repo's here? Not sure of the rules, couldn't see any posting guidelines.

This is my first major win applying what @Jake Van Clief ef teaches. Since subscribing to Claude Code on March 19th, I’ve been able to show so much progress that my company has now upgraded me to the Max 5x subscription. Looking forward to pushing the boundaries of what’s possible and continuing to improve our processes! As a Finance Manager responsible for month-end closing, I wanted to see what Claude Code could actually achieve—and it delivered! Even without Azure or backend access to our ERP system (D365 F&O), I didn't let that stop me from being "efficiently lazy." Claude Code showed me how to use the Playwright MCP to control Chrome and handle the heavy lifting for me. The script now automatically downloads the monthly trial balance, populates an Excel template, identifies discrepancies via color-coding, and even takes screenshots to document numbers from various reports. I’m already tackling my next big automation project—a task that is notoriously tedious when done manually. Stay tuned for that post, as well as more month-end automation updates in the near future! I had Claude code describe the workflow: Common Reconciliation — Monthly Close Automation with Claude Code + Playwright MCP Every month-end I run a single slash command (/mec-common) and pass it a month number. Claude then drives the entire reconciliation process end-to-end, touching both a live D365 ERP system and a multi-sheet Excel workbook — no manual steps. The workflow in three phases: Phase 1 — Trial Balance Claude navigates to the D365 Trial Balance page, clears any stale filters, sets the correct date range, triggers a recalculation, and downloads the export. The Excel file is placed in the right folder, and the data is pasted (values only) into the reconciliation workbook's Trial bal D365 sheet. A full workbook recalculation is then forced before anything is read. Phase 2 — Revaluation Check Claude loops through ~50 reconciliation sheets. On each sheet it finds the last row where column C says "Revaluation" (there are two — the second one holds the actual diff) and reads the value in column G. If the diff is outside ±1, the sheet tab is colored red. One sheet (150070) is always flagged red and requires manual review regardless.

Completed a HABIT Tracking app. “Set your daily HABITS you want to improve on and let the 8th wonder of the world, COMPOUND INTEREST , prosper you in achieving goals and creating new BETTER habits. OPTION MENU Displays your analytics from results of a week, month, quarter, etc. Steps: 1. told Claude chat what I wanted. I said it needs to be a free setup, no subscriptions or fees to start and it recommended I use GitHub, vercel and Supabase. This is to store the data it records when users check off tasks for their daily habits and tracks results. I wanted Oauth so people can login with email. Daily quotes revolving in the ui to keep up motivation. 2.told Claude chat to make me a plan to effectively build this organized and as a pro engineer. 3. Converted the chat into a short Claude Md file and a context file. 4.told it to give me a pro CS Eng folder structure and save it to my docs. 5. Pushed it to git hub and I told it to build. All from VScode we went to work…. And had more than 50% worth of tokens left, as I even used it for other ideas while it was building out task app. This was amazing. Thank you @Jake Van Clief !!! Looking forward to more content of yours. Now time to work on the UI.

You just saw how context changes per task. Vote below, then tell us in the comments: what two areas of your work did you set up, and did Claude behave differently in each one?