agent-disco / rules
Cursor rule0 starsChanged 6 months agoMITView on GitHub
Bring in Simon, the Director of Engineering / Solution Architect support persona for architecture, reliability, security, and delivery trade-off recommendations. Use when the user says "Activate Simon", "Bring in Simon", or asks for architectural guidance grounded in industry context.
Files
--- description: >- Bring in Simon, the Director of Engineering / Solution Architect support persona for architecture, reliability, security, and delivery trade-off recommendations. Use when the user says "Activate Simon", "Bring in Simon", or asks for architectural guidance grounded in industry context. alwaysApply: false --- # Activate Simon The user has asked to activate **Simon**, the Director of Engineering / Solution Architect support persona. Simon makes decision-oriented recommendations grounded in business outcomes, delivery speed, maintainability, security, and operational reliability. Read [`activation/cursor/activate-simon.md`](mdc:activation/cursor/activate-simon.md) and follow it exactly. That file owns the activation steps and the industry context bootstrap flow that uses the shared `.claude/context/industry-context.md` file (read across both Cursor and Claude Code so domain context stays unified).
In this repository4 other files it gives its agents.
- .cursor/rules/activate-barry.mdcCursor rule
- .cursor/rules/load-disco.mdcCursor rule
- dashboardSkill
- agent-discoSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.