Kyle Trauberman

Windows · .NET · Aspire · Marten/Wolverine

Settings

I use ccstatusline for my status line in Claude Code.
The permission philosophy in settings.local.json is “verbose allow-list for read-only, hard deny on anything destructive”.
I have some global instructions configured in ~/.claude/claude.md:

# Azure DevOps MCP Server Defaults

When using any Azure DevOps MCP tools, always use the following default values unless the user explicitly specifies otherwise:

- **Organization:** `adesacentral`
- **Project:** `adesa`
- **Area Path:** `Adesa\Untitled`
- **Iteration Path:** `ADESA`
- **Parent Feature:** `155843` (set as parent on newly created work items)

# Essentials Plugin

- Whenever you are asked to use the Essentials plugin (any `essentials:*` skill or agent) for a PBI, also update that PBI in Azure DevOps to add the `RPIV` tag (preserving any existing tags).
- Whenever you are asked to use the Essentials plugin (any `essentials:*` skill or agent), AND the `/essentials:essentials-prime` skill has not already been executed in the current session, then execute the `/essentials:essentials-prime` skill to ensure you have proper context loaded.

Plugins

I use essentials pluging regularly. I always start a session by calling /essentials:essentials-prime, but if I forget, claude has instructions to do that automatically before calling any other essentials skill.

MCPs

Connected globally in ~/.claude.json:

Context7 — current library docs, so Claude doesn’t lean on stale training data when I’m in unfamiliar packages. Stdio: npx -y @upstash/context7-mcp.
Azure DevOps — the official @azure-devops/mcp server bound to org adesacentral, scoped via -d to the core, work, work-items, search, and pipelines domains. My global CLAUDE.md pins the defaults: project adesa, area path Adesa\Untitled, iteration ADESA, parent feature 155843 for any new work item.

Hooks & automation

I use Gitkraken as my git UI, and a recent update added integration with claude via hooks. In this way, GitKraken’s AI features ingest the full activity stream and can correlate it back to git state. Every single hook fires the same command:

"C:/Users/ktrauber/AppData/Local/GitKrakenCLI/gk.exe" ai hook run --host claude-code

Workflow

I run the four-phase essentials workflow — Research → Plan → Implement → Validate — for almost everything non-trivial. /essentials:essentials-workflow is the entry point: it auto-detects which phase I’m in from the artifacts already in ai_docs/ and tells me what to run next, so I don’t have to memorize the command sequence.

I use /essentials:essentials-code-review to review PRs. Combined with the gh cli, Claude can review a PR and provide meaningful feedback directly on the PR as a comment.