skills.rest
OshanKHZ
OshanKHZCOMMUNITY
Explore all skills by this author →
GitHub

instructions-development

Create and synchronize CLAUDE.md files with codebase patterns.

5|2|Updated Dec 26, 2025
Search Tags:#workflow#documentation#split#organization#CLAUDE.md#instructions#modular
One-click install
npx skills add https://github.com/OshanKHZ/oshankhz-claude-code --skill instructions-development
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: instructions-development
Source: https://github.com/OshanKHZ/oshankhz-claude-code/tree/main/.claude/skills/instructions-development
Command: npx skills add https://github.com/OshanKHZ/oshankhz-claude-code --skill instructions-development

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and examples (resource) and scripts (resource) components.

What problem does it solve?

This skill enables automating and organizing the complete lifecycle of project instructions: from initial CLAUDE.md creation through synchronization with code patterns to modular organization of rules. It helps teams maintain consistent project documentation with predictable lifecycles.

Core Features & Use Cases

  • Initialize: Create an opinionated baseline CLAUDE.md for new projects.
  • Sync: Analyze codebase to detect patterns and update CLAUDE.md with discovered conventions.
  • Organize: Create or manage .claude/rules/ modular structure for scalable documentation.
  • Split: Break large CLAUDE.md into focused rule files to improve maintainability.
  • Guided workflow: Interactively guide users with questions (AskUserQuestion) to decide between simple and modular setups and to preview structure.

Quick Start

  1. Decide between Single-file CLAUDE.md or Modular CLAUDE.md structure and preview the outline.
  2. Generate a baseline CLAUDE.md with core standards, architecture rationale, and Git conventions.
  3. If modular, propose a .claude/rules/ structure and show a preview of file layout; otherwise keep a single-file approach.
  4. Obtain explicit user confirmation before writing files and outline next steps.