Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Setup production-grade .claude/ AI collaboration layer for projects. Use when an agent starts using Claude Code for development, enters a new project directo...
Setup production-grade .claude/ AI collaboration layer for projects. Use when an agent starts using Claude Code for development, enters a new project directo...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Setup production-grade `.claude/` AI collaboration layer for projects.
This skill ensures projects have a proper `.claude/` configuration before agents start development work with Claude Code. It acts as a supervisor to maintain and enforce project standards.
.claude/ must be created in the target project directory, NOT in your workspace root. Example: โ Wrong: /home/user/workspace-xiaolong/.claude/ (workspace root) โ Correct: /home/user/eave-web/.claude/ (actual project being developed) Always identify which project you're working on first, then check/create .claude/ in that directory.
Starting a new development task with Claude Code Entering a new project directory User mentions "Claude Code", ".claude", "AI collaboration layer", or "project standards"
Always check if `.claude/` directory already exists in the target project directory: ```bash ls -la .claude/ 2>/dev/null ```
If the project doesn't have `.claude/` directory, create it first before development: ```bash node ~/.openclaw/skills/claude-code-setup/index.js ```
If `.claude/` already exists: โ DO NOT overwrite existing files โ DO NOT recreate the structure โ Let Claude Code naturally maintain and update during development
Your role is supervisor, not executor: Ensure Claude Code follows rules in `.claude/` During development, let Claude Code update configs based on actual code Periodically review if `.claude/` content matches the project reality
CLAUDE.md is core โ Highest priority project instructions Modular โ Separate rules/skills/context Clear directives โ Use MUST/ALWAYS/NEVER Project context โ Must include project overview and tech stack Don't reinvent โ Reuse and maintain existing configs
``` .claude/ โโโ CLAUDE.md # โญ Project-level global instructions (most important) โโโ rules/ # Team rule library โ โโโ frontend.md โ โโโ typescript.md โ โโโ commit.md โโโ context/ # Project context knowledge โ โโโ project.md โ โโโ stack.md โโโ skills/ # Project-private skills โ โโโ generate-crud.md โโโ prompts/ # Reusable prompt templates โโโ review.md ```
โ Writing as requirements doc or README โ Vague rules ("try to", "should") โ Only CLAUDE.md without modularity โ Missing project context โ Overwriting existing configs โ Redundant recreation
When using Claude Code: Before starting: Ensure `.claude/` exists During development: Let Claude Code reference rules in `.claude/` After completion: Update `.claude/` with any new standards learned
See `index.js` for template definitions.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.