跳到技能内容
词映 AI导航
发现工具选型指南Skills 技能AI 快讯AI图片AI视频AI文档AI办公AI助手AI搜索AI编程AI音频AI设计AI智能体模型与开发AI学习模型评测AI提示词内容检测AI金融AI 3D扫描与识别其他工具跨境电商 AI
词映 AI导航
工具库Skills 技能
我的收藏
词映 AI导航
发现工具选型指南Skills 技能AI 快讯AI图片AI视频AI文档AI办公AI助手AI搜索AI编程AI音频AI设计AI智能体模型与开发AI学习模型评测AI提示词内容检测AI金融AI 3D扫描与识别其他工具跨境电商 AI
Skills directory/kevin-n-01/oskado-web/component-modularity

Claude Code component-modularity for multi-section React forms

Split a page or dialog into an orchestrator and section components, distinguishing shared submission data from local interaction state.

中文

Install in Claude Code

Open a React project in Claude Code with the current page or form. Identify state needed by more than one section.

  1. Review `.claude/skills/component-modularity/SKILL.md` and its requirements at the pinned GitHub commit.
  2. Create `.claude/skills/component-modularity/` in your project and save the reviewed file as `.claude/skills/component-modularity/SKILL.md`.
  3. Start Claude Code from that project's root, then select `/component-modularity` in the slash menu.

Example task

Screen edit-24 has 3 sections: basics, contact details, and notes. Save needs data from all three sections, while collapse affects its own section only.

What to check

Produce {sectionFiles: 3, coordinatorFiles: 1}. The coordinator owns shared form data, and sections own collapse state and report updates through callbacks.

Original SKILL.md on GitHub · Updated 2026-11-14

Frequently asked question

When should state stay in a section component?

Keep local-only state in its section. A value needed for submission or across multiple sections belongs in the orchestrator.

Browse Claude Code skills in the Chinese directory
词映 AI 导航Skills 技能
工具分类全部工具已本地化技能选型指南AI 快讯