MiniClau In-Depth Guide — Chapter 18: Best Practices and Optimization Tips

> 💡 This chapter provides best practices and optimization tips for using MiniClaw.

---

18.1 Daily Usage Recommendations

18.1.1 Starting a Conversation

✅ Recommended:

1. Make the project context explicit

• "I'm working on a React project using TypeScript"
2. State the current task
• "I need to implement a user authentication feature"
3. Provide relevant files
• "Please look at the files under src/auth/"

❌ Avoid:

• Overly short prompts
• Providing no context
• Asking multiple unrelated questions at once

18.1.2 Memory Management

✅ Recommended:

1. Proactively record important information

• "Remember that I use pnpm instead of npm"
2. Review MEMORY.md periodically
• Check that memories are still accurate
• Remove outdated information
3. Use miniclaw_note to record key decisions
• "Note: decided to use Zod for parameter validation"

❌ Avoid:

• Recording sensitive information (passwords, keys, etc.)
• Recording temporary or irrelevant information
• Never cleaning up outdated memories

---

18.2 DNA File Optimization

18.2.1 AGENTS.md Optimization

✅ Recommended:

1. Customize by project type

• Web projects: add frontend framework rules
• Node projects: add server-side rules
• Python projects: add Python conventions
2. Keep it concise
• 5–10 core rules
• Avoid verbose descriptions
3. Update regularly
• Adjust as the project evolves
• Remove rules that no longer apply

Example of improvement:

• ❌ "Don't use var, because var has variable hoisting issues that may cause..."
• ✅ "Use const/let, not var"

18.2.2 SOUL.md Optimization

✅ Recommended:

1. Define a clear tone

• Professional and rigorous
• Friendly and relaxed
• Concise and direct
2. Set boundaries
• What it can do
• What it cannot do
• How to handle edge cases
3. Include examples
• Examples of good responses
• Examples of responses to avoid

---

18.3 Skill Development Recommendations

18.3.1 Skill Design Principles

1. Single responsibility

• Each skill solves one class of problems
• Avoid overly complex functionality
2. Clear naming
• Use descriptive names
• Avoid abbreviations
3. Complete documentation
• Detailed SKILL.md
• Include usage examples
• State prerequisites
4. Version management
• Use semantic versioning
• Keep a changelog

---

Chapter Summary

• 💬 Daily usage: provide clear context; proactively record important information; clean up outdated memories regularly
• 📝 DNA file optimization: AGENTS.md for project rule customization; SOUL.md for tone and boundaries; USER.md for personal preferences
• 🔧 Skill development: single responsibility principle; clear naming conventions; complete documentation
• ⚡ Performance: set reasonable token budgets; archive old logs regularly; optimize skill caching

*This document is Chapter 18 of the "MiniClaw In-Depth Guide" series. The next chapter covers common problems and solutions.*