Instructions file GitHub Copilot
Instructions for jackfioru92/mcp-aruba-email, covering mcp aruba email server - copilot instructions, project overview, technology stack, project structure and development guidelines.
53 tagged calendar, measured the same way as everything else here.
Browse within: email 14macos 14contacts 11eventkit 9model-context-protocol 6
Instructions file GitHub Copilot
Instructions for jackfioru92/mcp-aruba-email, covering mcp aruba email server - copilot instructions, project overview, technology stack, project structure and development guidelines.
Instructions file CodexOpenCode
Instructions for dbhq-uk/outlook-graph-skill, covering agents.md, what this is, layout, conventions and validating a change.
Instructions file CodexOpenCode
AGENTS.md instructions for limey/cal-scheduler-mcp, covering agents.md, what it is, when it fits, when it doesn't and install.
Instructions file
A set of project instructions for Claude Code covering the konbu project, issue handling, and handoff notes for continuing work later.
Instructions file
Claude Code instructions for rumbitopi/mail-cal-drive-mcp, covering workspace mcp server - project instructions, project overview, development commands, install dependencies and start postgres + mcp server (docker).
Instructions file GitHub Copilot
Copilot instructions for Jordonh18/fastmail-mcp-server, covering copilot instructions for fastmail mcp server, project overview, architecture, directory structure and tool groups registered in server.ts.
Instructions file
Claude Code instructions for redpop/apple-calendar-mcp, covering claude.md, commands, the architecture constraint that explains everything, invariants that are easy to break and dependencies worth knowing.
Instructions file GitHub Copilot
Copilot instructions for goddivor/teams-mcp, covering copilot instructions — teams-mcp, project overview, architecture, commands and ci/cd.
Instructions file GitHub Copilot
Instructions for theexperiencecompany/gaia: Write clean and minimalistic code. Do not create unnecessary test files, markdown files, or unnecessary files. Prioritize writing clean, modular, and production-level code. Reuse existing logic, paradigms, and abstractions if present. Do not do anything unnecessary or extra.…