This document provides guidelines for maintaining high-quality Rust code. These rules MUST be followed by all AI coding agents and contributors.
All code you write MUST be fully optimized.
"Fully optimized" includes:
package.json, etc.) for available scripts.Here's my AGENTS.md (also linked from CLAUDE.md as @AGENTS.md) for hacking
agentically on MDFlow recipes.
I have this in ~/.mdflow/, and the agents/recipes live in ~/.mdflow/agents/ and added to the path
so that they can be invoked as commands.
With this I can use a coding agent like Claude Code or GitHub Copilot in VSCode and say something like:
> create a new agent using copilot that reviews all the code files in this directory as a poem
Applied rationality for a coding agent. Defensive epistemology: minimize false beliefs, catch errors early, avoid compounding mistakes.
This is correct for code, where:
Ultimate resource for extending Claude Code with custom skills, specialized agents, slash commands, and professional utilities
Last Updated: October 28, 2025 | Author: Alireza Rezvani | License: MIT
Claude Flow treats memory as the backbone and MCP tools as the hands. You get concurrent agents that coordinate cleanly, keep context tight, and ship durable artifacts without dragging long text through prompts. It feels like an ops layer for intelligence.
The stack is simple. Claude Code as the client. Claude Flow as the MCP server. SQLite memory at .swarm/memory.db for state, events, patterns, workflow checkpoints, and consensus. Artifacts hold the big payloads. Manifests in memory link everything with ids, tags, and checksums.
Coordination is explicit. Agents write hints to a shared blackboard, gate risky steps behind consensus, and record every transition as an event. Hooks inject minimal context before tools run and persist verified outcomes after. Small bundles in, durable facts out.
Planning keeps runs stable. Use GOAP to sequence actions with clear preconditions. Use OODA to shorten loops.
Observe metrics, orient with patterns, decide through votes, act with orchestration. Topology adapts from hi
| """ | |
| A micro event loop library implementation from scratch. | |
| This library provides a minimal but feature-complete asynchronous event loop | |
| implementation for educational purposes. It demonstrates the core concepts of | |
| asynchronous programming including: | |
| - Task scheduling and management | |
| - I/O multiplexing with non-blocking sockets | |
| - Timeouts and sleep functionality |