virtualization-mcp / rules
Cursor rule17 starsChanged 34 days agoMITView on GitHub
Enforce no fake-success behavior in runtime code and UI.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/architect.mdcCursor rule
- llms-full.txtllms.txt
- llms.txtllms.txt
- virtualizationSkill
- full-stack-developerSkill
- mcp-server-architectSkill
The file
Files
--- description: Enforce no fake-success behavior in runtime code and UI. globs: ["src/**/*.py", "webapp/backend/**/*.py", "webapp/frontend/src/**/*.tsx"] alwaysApply: true --- # Implementation Honesty Rule - Prototype placeholders are temporary and must be clearly marked. - Runtime code must not return simulated success for unimplemented behavior. - Missing integrations/models/providers must return explicit `not_implemented` errors. - Security/runtime findings must never be synthetic in production paths. - Webapp must show **Under construction** for unavailable functionality.
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.