From tdp
Set up or update plugin configuration in .claude/settings.local.json and create required companion files. Use when installing the plugin for the first time or when adding or adjusting environment variables and config files for db-management, memory, markitdown, or testing-and-proof skills.
npx claudepluginhub bryant-tang/turbo-plugins-claude --plugin tdpThis skill uses the workspace's default tool permissions.
Configure `.claude/settings.local.json` and companion files so this plugin's skills and commands can run in the current workspace.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
Configure .claude/settings.local.json and companion files so this plugin's skills and commands can run in the current workspace.
| Area | Env Vars | Companion File | Required For |
|---|---|---|---|
| Test stash | TEST_LOCAL_STASH_SHA | — | testing-and-proof (optional) |
| DB | DBHUB_TOML_FILE_PATH | .claude/dbhub.local.tomlsql files/local-db/sql files/test-db/sql files/main-db/sql files/archives/local-db/sql files/archives/test-db/sql files/archives/main-db/ | db-management |
| Memory | MEMORY_SERVER_JSONL_FILE_PATH | .claude/memory-server.local.jsonl | memory |
| MarkItDown | MARKITDOWN_WORKDIR_PATH | workdir directory | markitdown |
| Specs | — | specs/bugfix/specs/feature/specs/archives/bugfix/specs/archives/feature/ | start-dev, write-plan, finish-dev |
.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.DBHUB_TOML_FILE_PATH — if the file does not exist, copy the template from ${CLAUDE_PLUGIN_ROOT}/default-files/.claude/dbhub.example.local.toml to the configured path, then tell the user to edit the connection strings inside it.MEMORY_SERVER_JSONL_FILE_PATH — if the file does not exist, create an empty file at that path.MARKITDOWN_WORKDIR_PATH — if the directory does not exist, create it..claude/frontend-standard.local.md — if the file does not exist in the workspace root, copy the template from ${CLAUDE_PLUGIN_ROOT}/default-files/.claude/frontend-standard.example.local.md.sql files/ directory structure — if the DB area was configured in this run, create each of sql files/local-db/, sql files/test-db/, sql files/main-db/, sql files/archives/local-db/, sql files/archives/test-db/, and sql files/archives/main-db/ that does not already exist. Create each directory as a separate step; do not chain with &&.specs/ directory structure — regardless of which areas were configured, create specs/bugfix/, specs/feature/, specs/archives/bugfix/, and specs/archives/feature/ if they do not already exist. Create each directory as a separate step; do not chain with &&..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.DBHUB_TOML_FILE_PATH and MEMORY_SERVER_JSONL_FILE_PATH are absolute paths to files that the Docker containers can read via volume mount.MARKITDOWN_WORKDIR_PATH is an absolute path to a directory that the Docker container mounts as /workdir.sql files/local-db/, sql files/test-db/, sql files/main-db/, sql files/archives/local-db/, sql files/archives/test-db/, and sql files/archives/main-db/ are only created when the DB area is configured in the current run. If the DB area is skipped, do not touch sql files/.specs/bugfix/, specs/feature/, specs/archives/bugfix/, and specs/archives/feature/ are always created regardless of which areas the user chose to configure. If any of these directories already exist, skip them silently..claude/settings.local.json. The DBHub TOML file holds the actual database credentials; only the path to that file goes in the env block.&&.DBHUB_TOML_FILE_PATH, MEMORY_SERVER_JSONL_FILE_PATH, and MARKITDOWN_WORKDIR_PATH are passed directly to Docker volume mounts without any path normalization. Provide an absolute path appropriate for the host OS: Windows absolute with backslash (C:\...) or forward slash (C:/...), or Unix/macOS absolute (/path/...). Write the value as-is./c/Users/...), convert it to Windows format (C:/Users/...) before writing to settings.local.json, since that format is not reliably supported by Docker Desktop on Windows..claude/settings.local.json exists and the env block contains all configured keys with real, non-placeholder values.sql files/local-db/, sql files/test-db/, sql files/main-db/, sql files/archives/local-db/, sql files/archives/test-db/, and sql files/archives/main-db/ all exist.specs/bugfix/, specs/feature/, specs/archives/bugfix/, and specs/archives/feature/ all exist..claude/settings.local.json.