pyeye-mcp
CLAUDE.md0 starsChanged yesterdayMITView on GitHub
This file loads modular Claude behavior instructions. The actual instructions are in .claude/instructions/. @.claude/instructions/00-documentation-system.md @.claude/instructions/01-core-rules.md @.claude/instructions/02-session-startup.md @.claude/instructions/05-workflow-issues.md @.claude/instructions/06-workflow-commits.md @.claude/instructions/07-validation.md @.claude/instructions/11-pr-requirements.md @.claude/instructions/03-mcp-dogfooding.md @.claude/instructions/04-agent-triggers.md @.claude/instructions/09-task-management.md @.claude/instructions/10-cross-platform.md @.claude/instructions/08-project-specific.md @docs/LABELS.md This file defines the GitHub label system you MUST use when creating issues, PRs, or suggesting labels. These files contain detailed human documentation that you can reference if needed: Note: The mandatory Claude-specific rules from CONTRIBUTING.md have been extracted to appropriate instruction files For personal development settings (worktrees, local paths, etc.): @~/.claude/projects/okeefeco/pyeye-mcp.md This file…
In this repository5 other files it gives its agents.
- pyeye-scenariosSkill
- pyeye-verifySkill
- architecture-reviewSkill
- decision-logSkill
- python-exploreSkill
The file
Files
PyEye Server - Claude Instructions
This file loads modular Claude behavior instructions. The actual instructions are in .claude/instructions/.
🎯 CRITICAL: First, Understand the Documentation System
@.claude/instructions/00-documentation-system.md
Core Behavior and Rules
@.claude/instructions/01-core-rules.md @.claude/instructions/02-session-startup.md
Development Workflows
@.claude/instructions/05-workflow-issues.md @.claude/instructions/06-workflow-commits.md @.claude/instructions/07-validation.md @.claude/instructions/11-pr-requirements.md
Required Development Practices
@.claude/instructions/03-mcp-dogfooding.md @.claude/instructions/04-agent-triggers.md
Tools and Utilities
@.claude/instructions/09-task-management.md @.claude/instructions/10-cross-platform.md
Project-Specific Configuration
@.claude/instructions/08-project-specific.md
GitHub Labels Reference
@docs/LABELS.md
This file defines the GitHub label system you MUST use when creating issues, PRs, or suggesting labels.
Optional Human Documentation References
These files contain detailed human documentation that you can reference if needed:
CONTRIBUTING.md- Detailed setup guides, explanations, and human-oriented documentation
Note: The mandatory Claude-specific rules from CONTRIBUTING.md have been extracted to appropriate instruction files
Optional User-Specific Configuration
For personal development settings (worktrees, local paths, etc.):
@~/.claude/projects/okeefeco/pyeye-mcp.md
This file is optional and ignored if it doesn't exist. It won't be committed to the repository.
Dogfooding Metrics Tracking
To measure our MCP adoption:
# View real-time analytics
mcp-report # 7-day report
mcp-report-month # 30-day report
mcp-logs # Watch live activity
mcp-session # View active session
mcp-errors # Check for hook errorsMetrics tracking is automatic via Claude Code hooks. See scripts/claude_hooks/README.md for details.
For Humans: This directory contains Claude's behavioral instructions. See .claude/README.md for details.
For Claude: You MUST read and follow ALL imported instruction files above. They define your required behavior.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

