Profile Schema
A profile is a JSON file capturing what dxai system / dxai project should install. CLI flags always beat profile values.
Auto-discovery: ./.dxai/profile.json → ~/.dxai/config.json → ~/.dxairc. Override with --profile <nameOrPath>. See Guide / Profiles for usage.
Fields
Section titled “Fields”| Key | Type | Description |
|---|---|---|
mode | "system" | "project" | "both" | Default mode dxai apply runs when this profile is active. |
agents | string[] | Agent IDs to configure (cursor, claude-code, vscode, codex, gemini, windsurf, antigravity). |
mcp | string[] | MCP server IDs to install. See Registry / MCP servers. |
skills | string[] | Skill IDs to install. See Registry / Skills. |
features | string[] | Project features to generate (cursor-rules, agents-md, editorconfig, etc.). |
stack | string[] | Tech stack IDs. See Registry / Stacks. |
mcpInputs | object | Per-server input values, keyed by server ID. Example: {"filesystem": {"allowedPath": "~"}}. |
Example
Section titled “Example”{ "mode": "both", "agents": [ "cursor", "claude-code" ], "mcp": [ "github", "playwright", "context7" ], "skills": [ "frontend-design" ], "features": [ "cursor-rules", "agents-md", "editorconfig" ], "stack": [ "react", "node" ], "mcpInputs": { "filesystem": { "allowedPath": "~/Code" } }}Forward compatibility
Section titled “Forward compatibility”Unknown keys are silently dropped when the profile is read. New keys can be added in future dxai releases without breaking existing profiles.