claude-optimised
Guide for writing and optimizing CLAUDE.md files for maximum Claude Code performance. Use when creating new CLAUDE.md, reviewing existing ones, or when user asks about CLAUDE.md best practices. Covers structure, content, pruning, and common mistakes.
Why use this skill?
Learn to write concise, high-impact CLAUDE.md files that maximize Claude Code adherence. Master pruning techniques to remove noise and enforce project standards.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/hexnickk/claude-optimisedWhat This Skill Does
The claude-optimised skill is a specialized documentation and prompt-engineering utility designed to help developers create and maintain effective CLAUDE.md files. It streamlines the instruction set for Claude Code by applying the principle of 'less is more,' ensuring that your project-specific guidelines are concise, actionable, and prioritized. By minimizing token noise, this skill helps ensure that Claude consistently adheres to your architectural patterns, build commands, and critical project 'gotchas' without ignoring core instructions.
Installation
Install the skill via the OpenClaw agent interface using the following command:
clawhub install openclaw/skills/skills/hexnickk/claude-optimised
Use Cases
- Project Initialization: Use this during the setup phase of a new repository to establish a clean, effective CLAUDE.md from the ground up.
- Performance Debugging: If you notice Claude is hallucinating patterns, missing build steps, or ignoring file conventions, invoke this skill to audit and prune your existing CLAUDE.md for clarity and impact.
- Standardization: Ensure consistency across large codebases by defining standard branch naming conventions, non-obvious architecture rules, and testing protocols.
- Token Management: Prevent instruction decay by identifying and removing redundant rules that Claude already handles natively, allowing for higher priority for complex, project-specific logic.
Example Prompts
- "Review my current CLAUDE.md and suggest which lines are redundant or confusing. I want to make sure my build steps are clearly prioritized."
- "I'm setting up a new Next.js project. Can you generate a minimal, high-impact CLAUDE.md template that includes our strict directory structure and testing conventions?"
- "Claude keeps suggesting 'useState' even though we use a custom state management hook. How should I phrase this rule in CLAUDE.md to ensure maximum adherence?"
Tips & Limitations
- Aggressive Pruning: The most common mistake is creating a 'documentation dump.' Treat your CLAUDE.md as a surgical tool, not a manual. If a rule doesn't solve a repeat mistake, remove it.
- Hierarchical Loading: Remember that CLAUDE.md files at different levels (root vs. subdirectory) have different scopes. Use the skill to balance instructions between global preferences and local project quirks.
- Maintenance: Set a reminder to review your file every few weeks. If Claude misbehaves, the solution is almost always to remove 3-5 lines rather than adding more.
- Limitations: This skill focuses on the content and structure of instructions. It does not control Claude's internal model weights or the underlying codebase complexity.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-hexnickk-claude-optimised": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: file-read, file-write