Hello People,
i try to use Ruflo and have it intstalled and initialized in a project folder. But i was wondering why the memory usage is low and also things like swarm are not in use if i don´t explicitly tell claude to.
This was Claudes analysis:
Rules I Always Apply Automatically
These align with my built-in behavior or are clear and sensible:
From CLAUDE.md:
- "Do what has been asked; nothing more, nothing less" — core principle of my system prompt, always active
- Never create files unnecessarily / prefer editing existing ones — built-in behavior
- No docs/READMEs unless explicitly requested — built-in behavior
- Read file before editing — technically enforced by the Edit tool
- Never commit secrets, credentials, or
.env files — security rule, always active
- Input validation at system boundaries — standard security practice
From Memory:
- Never configure cloud services independently — clear feedback from you, I always ask first
- MOCO sync rules — I apply these whenever I touch MOCO-related code
- UI patterns (detail panel, breadcrumbs, date format, etc.) — I reference these for any UI work
- Task modules instead of types — I respect this conceptual shift in task features
Rules I Apply Situationally
- "ALWAYS run tests after code changes" — I do when it makes sense, but not after every one-liner. Depends on whether tests exist and are runnable.
- File Organization (
/src, /tests, etc.) — your project actually uses Next.js conventions (app/, components/, lib/), so I follow the real structure, not what's listed.
- "Keep files under 500 lines" — good guideline, but I won't proactively split files that are already longer.
- DDD / Event Sourcing / TDD London School — only if you're actively using it. I see no event sourcing in the project. The rule is aspirational, not reality.
Rules I Do Not Apply
These come from the claude-flow framework and are largely generic boilerplate with little relevance to your project:
- Swarm Orchestration / Execution Rules — you don't use a multi-agent swarm system. I won't spin up swarms when you say "fix the button."
- 3-Tier Model Routing (ADR-026) — Haiku/Sonnet/Opus routing, WASM Agent Booster. Claude-flow internals, not relevant to your work.
- "ALWAYS batch ALL todos in ONE TodoWrite call (5-10+)" — overkill for normal tasks. I batch where sensible, not dogmatically.
- Concurrency rules ("1 MESSAGE = ALL OPERATIONS") — I already parallelize where possible, but forced parallelization can hurt quality when dependencies exist.
- Memory/HNSW/Neural Commands — framework features you don't actively use.
- 60+ Agent Types / SPARC Methodology — reference docs, not active tooling in your project.
- Security scan CLI command — exists but I don't run it automatically.
- Project Config (Topology, Max Agents, etc.) — configures a framework you're not actively using.
Summary
Your CLAUDE.md is roughly ~40% useful, ~60% claude-flow boilerplate. The memory files are all highly relevant — I actively use those.
Recommendation:
Strip the CLAUDE.md down to what matters for day-to-day development — behavioral rules, file organization adapted to your actual Next.js structure, build/test/lint commands, security rules, and project-specific conventions. Move or remove the claude-flow framework docs.
What am i missing to use ruflos full potenzial?
Hello People,
i try to use Ruflo and have it intstalled and initialized in a project folder. But i was wondering why the memory usage is low and also things like swarm are not in use if i don´t explicitly tell claude to.
This was Claudes analysis:
Rules I Always Apply Automatically
These align with my built-in behavior or are clear and sensible:
From CLAUDE.md:
.envfiles — security rule, always activeFrom Memory:
Rules I Apply Situationally
/src,/tests, etc.) — your project actually uses Next.js conventions (app/,components/,lib/), so I follow the real structure, not what's listed.Rules I Do Not Apply
These come from the claude-flow framework and are largely generic boilerplate with little relevance to your project:
Summary
Your
CLAUDE.mdis roughly ~40% useful, ~60% claude-flow boilerplate. The memory files are all highly relevant — I actively use those.Recommendation:
Strip the
CLAUDE.mddown to what matters for day-to-day development — behavioral rules, file organization adapted to your actual Next.js structure, build/test/lint commands, security rules, and project-specific conventions. Move or remove the claude-flow framework docs.What am i missing to use ruflos full potenzial?