skills.rest
luiseiman
luiseimanCOMMUNITY
Explore all skills by this author →
GitHub

export-config

Export dotforge configuration to Cursor, Codex, Windsurf, and OpenClaw artifacts.

8|1|Updated Mar 19, 2026
Search Tags:#automation#migration#configuration#export#code-editor#dotforge
One-click install
npx skills add https://github.com/luiseiman/dotforge --skill export-config-luiseiman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: export-config
Source: https://github.com/luiseiman/dotforge/tree/main/skills/export-config
Command: npx skills add https://github.com/luiseiman/dotforge --skill export-config-luiseiman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Replicating a project's dotforge configuration across different AI code editors is error-prone and tedious; this Skill automates the porting process to maintain consistency.

Core Features & Use Cases

  • Convert and export dotforge configurations for Cursor, Codex, Windsurf, and OpenClaw.
  • Read project-level configuration files (CLAUDE.md, .claude/rules/*.md, .claude/settings.json) and generate editor-specific artifacts.
  • Use case: migrate a project setup to a new editor environment without manual reconfiguration.

Quick Start

Run the export command in your project root to generate the appropriate editor-specific configuration artifacts.

Frequently Asked Questions about export-config

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate dotforge configuration to Cursor or Windsurf?▼

To migrate dotforge configuration to Cursor or Windsurf, run the export command in your project root. The Skill reads CLAUDE.md, .claude/rules/*.md, and .claude/settings.json, then generates editor-specific artifacts like .cursorrules or .windsurfrules automatically.

What is the process to port AI code editor rules from CLAUDE.md?▼

Porting AI code editor rules from CLAUDE.md involves reading project-level configuration files and converting them into tool-specific formats. The Skill validates configuration presence, reports conflicts, and generates artifacts like AGENTS.md for Codex or SKILL.md for OpenClaw.

Can I convert .claude settings to multiple AI code editors at once?▼

Yes, you can convert .claude settings to multiple AI code editors. The Skill exports dotforge configuration to Cursor, Codex, Windsurf, and OpenClaw simultaneously, generating tool-specific artifacts for each platform from a single source.

What happens if there are configuration conflicts during dotforge export?▼

During dotforge export, the Skill validates configuration presence and reports success or conflicts. It ensures safe overwrite of existing editor-specific artifacts while maintaining clear source references for traceability across Cursor, Codex, Windsurf, and OpenClaw.

Do I need specific files in my project root to export dotforge configuration?▼

Yes, you need CLAUDE.md, .claude/rules/*.md, and .claude/settings.json in your project root to export dotforge configuration. The Skill reads these source files to generate editor-specific artifacts like .cursorrules, AGENTS.md, .windsurfrules, or OpenClaw SKILL.md.

Related Skills

Explore More Software Engineering Skills→
luiseimanluiseiman
8

bootstrap-project

Bootstrap Claude Code configuration from the dotforge template in projects.

Community
Advanced
euroconiceuroconic
1

ai-native-architect

Create decoupled AI-native project folders with explicit agent rules.

Community
Advanced
NirusanNirusan
7

sync-config

Synchronize local Claude configuration files to a GitHub repository.

Community
Basic
fmoda3fmoda3
42

doc-sync

Sync CLAUDE.md and README.md files across a repository.

Community
Basic