From tnf
Set up or update .NET Framework build and run configuration in .claude/settings.local.json. Use when installing the tnf plugin for the first time or when adjusting MSBuild path, IIS Express path, or csproj settings.
npx claudepluginhub bryant-tang/turbo-plugins-claude --plugin tnfThis skill uses the workspace's default tool permissions.
Configure `.claude/settings.local.json` with the environment variables required by the `build-project` and `run-project` commands so they can run in the current workspace.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Share bugs, ideas, or general feedback.
Configure .claude/settings.local.json with the environment variables required by the build-project and run-project commands so they can run in the current workspace.
| Area | Env Vars | Companion File | Required For |
|---|---|---|---|
| Build | BUILD_PROJECT_PATH, BUILD_MSBUILD_PATH | — | build-project command |
| Build frontend | BUILD_FRONTEND_DIR_PATH, BUILD_NODE_VERSION, BUILD_FRONTEND_INSTALL_COMMAND, BUILD_FRONTEND_BUILD_COMMAND | — | build-project (optional) |
| Run | RUN_IIS_EXPRESS_PATH, RUN_IIS_APPLICATIONHOST_CONFIG_PATH | — | run-project command |
.claude/settings.local.json if it exists and extract the current env block. Note which keys already have real values versus placeholder values.AskUserQuestion tool to ask the user about each env var. Ask one question per variable — do not batch all variables into a single summary table and ask for bulk confirmation. For each variable:
ABSOLUTE, RELATIVE, YOUR, or obvious template text), ask the user for the real value via AskUserQuestion.AskUserQuestion whether to keep or replace it. If the user chooses to keep it, skip to the next variable.env block back to .claude/settings.local.json, merging into any existing content so settings outside the env block are preserved..claude/settings.local.json already exists, merge into the env block only. Do not overwrite or remove any keys that are not part of this plugin's configuration..claude/settings.json also exists with an env block, keep this plugin's local values in settings.local.json so they stay out of version control.all, configure every area in the table above.BUILD_PROJECT_PATH is a relative path from the workspace root to the .csproj file.BUILD_MSBUILD_PATH and RUN_IIS_EXPRESS_PATH are absolute paths to executable files on the machine.RUN_IIS_APPLICATIONHOST_CONFIG_PATH, ask the user which applicationhost.config they want to use before prompting for a path:
.vs\{SolutionName}\config\applicationhost.config inside the workspace. This file is generated per-solution and keeps site bindings in version control proximity.%USERPROFILE%\Documents\IISExpress\config\applicationhost.config. This is the global fallback used when no project-level config is present.BUILD_* and RUN_* keys listed in the table above.&&.BUILD_PROJECT_PATH, BUILD_MSBUILD_PATH, BUILD_FRONTEND_DIR_PATH, RUN_IIS_EXPRESS_PATH, RUN_IIS_APPLICATIONHOST_CONFIG_PATH) accept any path format the user provides — Windows absolute with backslash (C:\...) or forward slash (C:/...), Unix absolute (/path/...), Git Bash drive format (/c/...), or relative with or without ./ prefix. Write the value as-is to settings.local.json; the underlying scripts (both bash and PowerShell) normalize all these formats automatically..\ prefix (Windows-style dot-backslash relative, e.g. .\src\Web.csproj). The bash script's path resolver does not strip .\. Prefer relative/path or ./relative/path format for relative paths..claude/settings.local.json exists and the env block contains all configured BUILD_* and RUN_* keys with real, non-placeholder values..claude/settings.local.json.