jeongheonk/c-sharp-custom-marketplace

Overview

This skill initializes or updates C#/.NET projects for use with Claude Code by creating a CLAUDE.md and installing context hooks (Bash or PowerShell). It supports three subcommands: init (full setup), migrate (add context sections to an existing CLAUDE.md), and hooks (install/update hook scripts). Use it when starting new projects, migrating existing documentation, or refreshing hook installations.

How this skill works

The skill parses command arguments to determine subcommand and target directory. For init/migrate it detects .sln/.csproj files, extracts TargetFramework, OutputType, UseWPF, and package references, and infers project type and solution layout. It installs appropriate hook scripts based on OS detection (bash on Linux/macOS/WSL/Git Bash, PowerShell on native Windows), updates .claude/settings.local.json with hook commands, and creates or edits CLAUDE.md from a template with conditional sections.

When to use it

• Creating a new C#/.NET project prepared for Claude Code integration (init).
• Migrating an existing repository to include Context Management and quick references (migrate).
• Installing or updating only the hook scripts without touching CLAUDE.md (hooks).
• When moving a project to a new machine or switching environments (refresh hooks).
• Before onboarding contributors who need standardized CLAUDE.md and hooks.

Best practices

• Run the skill from the repository root or pass the explicit project path to avoid wrong detection.
• Confirm overwrite when CLAUDE.md exists; prefer migrate if you want to preserve content.
• Keep scripts/hooks/ committed to share hooks across the team and add .claude/context to .gitignore.
• Verify bash scripts have execute permission on Linux/macOS after setup.
• Back up settings.local.json if parsing fails; the skill will create a safe new file if needed.

Example use cases

• Initialize a new WPF application repo with CLAUDE.md tailored to WPF patterns and install hooks.
• Migrate a legacy solution: add Context Management and Quick Reference sections without deleting existing docs.
• Install hooks on a Windows developer machine using PowerShell to enable session-start and pre-compact hooks.
• Set up a CI worker or container with the bash hook runner for session automation.
• Update hooks across a mono-repo after adding new hook scripts or changing runners.