Refined Corporate Preset

Enterprise-grade Claude Code configuration preset optimized for corporate development environments with strict governance policies.

When to Use This Setting

Apply this setting when you need to:

• Enforce corporate coding standards, naming conventions, and commit message formats across all team members
• Restrict Claude Code operations to approved tools, directories, and workflows within a corporate network
• Standardize AI-assisted development behavior across departments for compliance auditing

Consider alternatives when:

• You are working on personal or open-source projects without corporate governance requirements
• Your team needs maximum flexibility and minimal restrictions during rapid prototyping phases

Quick Start

Configuration

Copy
name: refined-corporate-preset
type: setting
category: api

Example Application

Copy
claude setting:apply refined-corporate-preset

Example Output

Setting applied successfully. Configuration changes:
- API routing: corporate proxy endpoint
- Permissions: corporate-restricted mode
- Logging: audit trail enabled
- Commit format: conventional commits enforced

Core Concepts

Corporate Governance Overview

Aspect	Details
Access Control	Role-based with directory restrictions
Audit Trail	All operations logged with timestamps
Code Standards	Enforced via pre-commit hooks
Data Handling	Sensitive file patterns blocked
Network Policy	Corporate proxy routing supported

Corporate Preset Architecture

┌─────────────────────────────────────────────┐
│              Corporate Preset               │
│  ┌─────────┐  ┌──────────┐  ┌───────────┐  │
│  │ API      │  │ Perms    │  │ Hooks     │  │
│  │ Routing  │  │ Matrix   │  │ Pipeline  │  │
│  └────┬─────┘  └────┬─────┘  └─────┬─────┘  │
│       │             │              │         │
│  ┌────┴─────────────┴──────────────┴─────┐  │
│  │        Compliance Layer               │  │
│  │  (logging, restrictions, validation)  │  │
│  └───────────────────────────────────────┘  │
└─────────────────────────────────────────────┘

Configuration

Parameter	Type	Default	Description
corporateProxy	string	none	URL of the corporate API proxy endpoint
auditLogPath	string	./logs	Directory for operation audit logs
allowedDirectories	array	["."]	Whitelisted workspace directories
commitFormat	string	conventional	Enforced commit message format
sensitivePatterns	array	[".env","*.key"]	File patterns blocked from reads

Best Practices

1. Layer Settings Hierarchically - Apply corporate presets at the organization level, then allow team-level overrides for non-security settings. This balances governance with team autonomy and prevents bottlenecks on configuration changes.

2. Audit Before Enforcement - Run the preset in monitoring-only mode for one sprint before enabling enforcement. Review the audit logs to identify legitimate workflows that would be blocked, and whitelist them before hard enforcement begins.

3. Version Your Presets - Store corporate preset configurations in your internal package registry with semantic versioning. This allows teams to pin to stable configurations and roll forward deliberately rather than receiving surprise policy changes.

4. Document Exceptions - Maintain a living document of approved exceptions to corporate restrictions. When a team needs elevated permissions for a specific workflow, record the justification and expiration date alongside the override configuration.

5. Integrate with SSO - Connect the preset's authentication layer to your corporate SSO provider. This ensures that Claude Code sessions inherit the same identity and permission boundaries as other corporate development tools.

Common Issues

1. Proxy connection timeouts - Corporate proxies may add latency. Increase the API timeout value and ensure the proxy allows WebSocket connections for streaming responses from Claude.

2. Overly restrictive permissions blocking normal workflow - Start with a permissive baseline and tighten incrementally. Use the audit log to identify which operations are most commonly needed before restricting them.

3. Commit hooks rejecting valid messages - Ensure the conventional commit regex accounts for all valid types (feat, fix, docs, style, refactor, perf, test, chore, ci, build, revert) and optional scope patterns used by your teams.