Skip to content
LumenFlow

Vendor capability matrix

LumenFlow stays vendor-agnostic by anchoring on shared concepts first:

  • Persistent repo instructions
  • Reusable skill or workflow surfaces
  • Optional subagents or background agents
  • Memory or personalization layers
  • Model and reasoning controls

The details vary by vendor. Use this matrix to decide which LumenFlow surfaces can be projected directly and which need a vendor-specific overlay.

Matrix

Section titled “Matrix”
VendorInstructions / rules surfaceSkills / reusable workflowsSub-agentsHooksSlash commandsMemory / personalizationModel / effort controls
Claude CodeCLAUDE.md, .claude/CLAUDE.md, .claude/rules/Native skills in .claude/skills/; custom slash commandsYes. Native subagents in .claude/agents/Yes. Project/user/local hooks via settings, plus skill/agent-scoped hooksYesCLAUDE.md plus auto memory/model and explicit effort controls are documented
Codex CLIAGENTS.md (root + nested), configurable fallback filenamesNative skills from .agents/skills/Yes, but explicit ask onlyYes, via Codex hooksYesNative memories are documented/model; reasoning effort available when the selected model supports it
Cursor.cursor/rules/, root AGENTS.md, root CLAUDE.md in CLINo documented SKILL.md surface; use rules insteadYes, background agentsNo documented project hook surface in the public docs reviewedCLI slash commands documentedNative Memories plus user rulesModel picker and Auto/Max modes documented
Windsurf.windsurf/rules/ and location-scoped AGENTS.mdNative skills in .windsurf/skills/; also discovers .agents/skills/; workflows in .windsurf/workflows/Caution: public docs describe Cascade, skills, and workflows, but do not document user-authored subagents the way Claude/Codex/Gemini doNo documented project hook surface in the public docs reviewedYes, workflows run via /[workflow-name]Native Memories and RulesModel picker documented; no separate reasoning-effort control documented in the public docs reviewed
Gemini CLIGEMINI.md by default; configurable to also read AGENTS.mdCustom commands and extensions are documented; no official .agents/skills/ skill surface found in the docs reviewedYes. Local and remote subagents under .gemini/agentsNo documented project hook surface in the public docs reviewedYesHierarchical GEMINI.md memory plus /memory management/model and per-agent model configuration are documented

Notes

Section titled “Notes”

Shared instruction surfaces

Section titled “Shared instruction surfaces”
  • AGENTS.md is a strong cross-vendor baseline today for Codex, Cursor, and Windsurf.
  • Claude Code still centers CLAUDE.md, not AGENTS.md.
  • Gemini CLI centers GEMINI.md, but its documented config allows additional context filenames, including AGENTS.md.

Shared skills surface

Section titled “Shared skills surface”
  • .agents/skills/ is a real cross-vendor projection target today for Codex and Windsurf.
  • Claude Code still expects .claude/skills/.
  • Cursor’s current public docs emphasize rules rather than a native SKILL.md skills surface.
  • Gemini CLI currently documents commands/extensions/subagents rather than a SKILL.md skill registry.

Sub-agent caution

Section titled “Sub-agent caution”

Windsurf is intentionally marked cautiously in the sub-agent column. Its public docs clearly cover Cascade, skills, rules, workflows, and memories, but the docs reviewed for this page do not expose an explicit user-authored subagent surface comparable to Claude Code’s .claude/agents/, Codex’s subagents, or Gemini CLI’s .gemini/agents.

Official vendor docs

Section titled “Official vendor docs”