update-claude-md-after-install

Replace generic CLAUDE.md examples with real project patterns from repository analysis.

2|5|Updated Nov 23, 2025
One-click install
npx skills add https://github.com/ulpi-io/togglebox --skill update-claude-md-after-install
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-claude-md-after-install
Source: https://github.com/ulpi-io/togglebox/tree/main/.claude/skills/update-claude-md-after-install
Command: npx skills add https://github.com/ulpi-io/togglebox --skill update-claude-md-after-install

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After installing framework agents, CLAUDE.md and its imported files contain generic placeholder examples. This skill guides you to systematically discover the actual project patterns and update these files with real, project-specific information.

Core Features & Use Cases

  • Discovery of actual patterns: Identify real commands, architecture decisions, and team conventions used in the project, replacing generic examples.
  • Documentation synchronization: Update CLAUDE.md and referenced guides (architecture, conventions, development guides) to reflect current project patterns.
  • Artifact generation: Create and import a development guide and updated references to enable a 10/10 documentation score.

Quick Start

Run the update-claude-md-after-install skill to analyze the repository and refresh CLAUDE.md documentation with project-specific details.

Frequently Asked Questions about update-claude-md-after-install

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update CLAUDE.md with real project patterns after installing framework agents?

To update CLAUDE.md, analyze your repository to identify actual commands, routes, and team conventions, then replace generic placeholder examples with project-specific information across CLAUDE.md, architecture.md, and conventions.md.

What's the best way to synchronize documentation with actual project conventions?

Synchronizing documentation requires discovering real architecture decisions from your repository and applying those updates across development guides and CLAUDE.md imports to reflect current team conventions and commands accurately.

Why does my CLAUDE.md still contain generic placeholder examples after setup?

CLAUDE.md contains generic placeholders because framework agents install default templates; you must systematically discover and replace these examples with real project patterns by analyzing the repository and imported references.

Can I generate concrete development guides from existing repository patterns?

Yes, you can generate concrete development-guide.md templates and file references by analyzing the repository to extract actual project patterns, achieving a 10/10 documentation quality score through updated CLAUDE.md imports.

Does updating markdown documentation require imported references and architecture files?

Updating markdown documentation requires analyzing imported references and architecture.md files to ensure CLAUDE.md updates reflect actual project patterns, team conventions, and real commands used in the repository.

When do I need to replace generic examples in CLAUDE.md and development guides?

You need to replace generic examples in CLAUDE.md and development guides when your documentation quality score requires project-specific accuracy, ensuring architecture.md and conventions.md reflect actual commands and routes.