From dev-standards
This skill should be used when the user asks to "update project", "refresh project settings", "re-detect languages", "update CLAUDE.md", "refresh hooks", or "reconfigure dev standards". Provides guidance for re-running detection, updating project configuration, and refreshing hooks.
How this skill is triggered — by the user, by Claude, or both
Slash command
/dev-standards:update-projectThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Re-detect the project's tech stack, compare it against current configuration, and update rules, CLAUDE.md, and hooks to reflect the current state of the project.
Re-detect the project's tech stack, compare it against current configuration, and update rules, CLAUDE.md, and hooks to reflect the current state of the project.
Run the same detection logic as the setup-project command. Scan for:
package.json, tsconfig.json, *.csproj, *.sln, go.mod, Cargo.toml, pyproject.toml, setup.py, requirements.txtnext.config.*, angular.json, vite.config.*, nuxt.config.*, svelte.config.*, astro.config.*, remix.config.*, serverless.yml, cdk.json, Dockerfile, docker-compose*.ymljest.config.*, vitest.config.*, pytest.ini, playwright.config.*, cypress.config.*, *_test.go.eslintrc*, eslint.config.*, .prettierrc*, biome.json, ruff.toml, .golangci.ymlprisma/, **/migrations/, drizzle.config.*, alembic/, Entity Framework references.claude/mcp.json or project-level MCP configurationCollect all findings into a detection summary.
Read the existing .claude/rules/ directory and .claude/CLAUDE.md.
Build a comparison report:
Changes since last setup:
New detections (no matching rule):
+ Python detected (pyproject.toml found) -- no .claude/rules/python.md
+ Playwright detected -- testing.md does not reference it
Removed (rule exists but tech no longer detected):
- .claude/rules/go.md exists but no go.mod found
Unchanged:
= TypeScript, Next.js, Vitest (all rules up to date)
Present this report to the user.
Present the available update operations and ask the user which to perform. Allow selecting multiple:
Wait for the user's answer before proceeding.
For each newly detected language or framework that lacks a corresponding rule:
${CLAUDE_PLUGIN_ROOT}/assets/templates/rules/.claude/rules/ with the generated-by comment header.claude/rules/testing.md to reference themAfter adding rules, show a summary of files created.
For each rule file whose corresponding technology is no longer detected:
After removing rules, show a summary of files deleted.
Read the current .claude/CLAUDE.md file. Present its contents section by section and ask the user which parts to update:
Show the current project description. Ask if it needs updating. If yes, ask for the new description and replace it.
Show the current technology list. Update it based on the latest detection results. Ask the user to confirm the updated list.
Show the current domain concepts. Ask if new concepts should be added or existing ones removed.
Show the current team conventions. Ask if conventions have changed or new ones should be added.
Write the updated .claude/CLAUDE.md file.
Read the current MCP configuration (.claude/mcp.json if it exists).
List all currently configured MCP servers with their commands and descriptions.
If the user wants to add a server, ask for:
npx, uvx, a local binary path)["-y", "@package/name@latest", "mcp"])Add the server to the MCP configuration file.
If the user wants to remove a server, show the list and ask which to remove. Confirm before deleting.
Read the current hook configuration from the dev-standards plugin.
Compare the installed hooks against the plugin's current hook definitions. If the plugin has been updated since setup, show the differences and offer to update.
If the user confirms, rewrite the hook configuration to match the latest plugin version.
Present a final summary of all changes made:
Project update complete:
Rules added: [list or "none"]
Rules removed: [list or "none"]
CLAUDE.md: [updated sections or "no changes"]
MCP servers: [changes or "no changes"]
Hooks: [refreshed or "no changes"]
npx claudepluginhub standardbeagle/standardbeagle-tools --plugin dev-standardsSyncs HCF project config with latest plugin defaults: adds missing CLAUDE.md/.claude files, appends .gitignore entries, flags pipeline differences. Use after HCF plugin updates.
Initializes project configuration by auto-detecting framework, replacing CLAUDE.md placeholders, and installing rules, hooks, and scripts.
Bootstraps .claude/ dotclaude config from template if missing, then customizes all files to match project's tech stack, conventions, and patterns. Interactive via user confirmations.