service-claude-md

Generates and updates per-service CLAUDE.md files from architecture documentation templates.

8|4|Updated Jul 1, 2026
One-click install
npx skills add https://github.com/YuShenLiu06/PCHSystem --skill service-claude-md-yushenliu06
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: service-claude-md
Source: https://github.com/YuShenLiu06/PCHSystem/tree/main/.claude/skills/service-claude-md
Command: npx skills add https://github.com/YuShenLiu06/PCHSystem --skill service-claude-md-yushenliu06

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintaining consistent, up-to-date CLAUDE.md memory files across multiple microservice directories is error-prone when done by hand. This Skill standardizes the generation and incremental updating of distributed CLAUDE.md files for each PCHSystem sub-service, ensuring they stay aligned with the root specification and architecture docs. ## Core Features & Use Cases - Template-Based Generation: Reads the service's architecture document and data model, then fills a six-section template covering service positioning, responsibility boundaries, service-specific red lines (RS-x), key entities, and documentation index. - Incremental Updates: When a service's architecture changes, only affected sections are modified while human-added notes are preserved, with timestamps refreshed. - Cross-Tool Alias Management: Automatically ensures an AGENTS.md symlink to CLAUDE.md exists in each service directory. - Use Case: After adding a new scoring-service to the backend, invoke this Skill with the service name to produce a compliant Backend/scoring_service/CLAUDE.md that references the root red lines R-1~R-12 without duplicating them. ## Quick Start Ask the assistant to generate or update the CLAUDE.md for a specific service such as scoring-service using the service-claude-md skill.

Frequently Asked Questions about service-claude-md

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

FAQPage Schema
How do I generate a CLAUDE.md for a new microservice?

Invoke the skill with the service name, such as user-service or scoring-service. It reads the corresponding architecture document under Docs/architecture/services/, fills the standard template, and writes the CLAUDE.md to the service's default directory after confirming the path exists.

How are service CLAUDE.md files updated after architecture changes?

The skill performs incremental updates: it re-reads the changed architecture document, modifies only the affected sections, preserves manually added content, and refreshes the timestamp at the end of the file without reordering sections.

What is the difference between R-x and RS-x red lines?

R-1 through R-12 are global red lines defined in the root CLAUDE.md and apply project-wide. RS-x numbers mark constraints specific to one service; service files reference global rules instead of duplicating them.

Does the skill create the AGENTS.md file as well?

Yes. It ensures an AGENTS.md relative symlink pointing to CLAUDE.md exists in the same directory, creating it with ln -s if missing. AGENTS.md is never edited directly since CLAUDE.md is the authoritative source.

When should I not use this skill?

Do not use it to edit the root CLAUDE.md, which is maintained manually, or to write full API or module documentation. Those detailed documents belong in Docs/architecture/; this skill only produces service-level summaries and navigation.