import-existing-ai-config

Migrate Claude, Copilot, and Cursor configurations into universal-ai-config templates.

2|1|Updated May 3, 2025
One-click install
npx skills add https://github.com/specklesystems/speckle-docs-NEW --skill import-existing-ai-config-specklesystems
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: import-existing-ai-config
Source: https://github.com/specklesystems/speckle-docs-NEW/tree/main/.universal-ai-config/skills/import-existing-ai-config
Command: npx skills add https://github.com/specklesystems/speckle-docs-NEW --skill import-existing-ai-config-specklesystems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrates and unifies existing AI tool configurations from Claude, Copilot, or Cursor into universal-ai-config templates to simplify multi-target setup and ongoing maintenance.

Core Features & Use Cases

  • Migrates target-specific configuration data into universal templates while preserving key fields and relationships.
  • Standardizes definitions across targets, enabling reuse across environments and teams.
  • Use cases include onboarding new AI tooling, consolidating disparate configurations, and maintaining consistency across projects.

Quick Start

Specify the source target and run the migration to generate universal templates.

Frequently Asked Questions about import-existing-ai-config

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

FAQPage Schema
How do I migrate Claude, Copilot, or Cursor configurations into a universal template?

To migrate AI configurations, specify your source target and run the conversion to map target-specific frontmatter fields into universal-ai-config templates. This standardizes definitions across environments while preserving key fields and relationships.

What are universal AI config templates and when do I need them?

Universal AI config templates are standardized configuration files that unify definitions across multiple AI targets. You need them when onboarding new AI tooling, consolidating disparate configurations, or maintaining consistency across projects and teams.

How do I convert target frontmatter fields to universal fields during a migration?

Converting target frontmatter fields involves mapping specific configuration keys to universal fields such as name, description, globs, alwaysApply, mcpServers, and hooks. This ensures a faithful conversion across multi-target environments.

Can I preserve companion files like scripts and assets when consolidating AI tool configurations?

Yes, consolidating AI tool configurations preserves companion files such as references, scripts, and assets alongside the mapped frontmatter. This maintains the integrity of the original configuration setup during the migration.

What is the best way to maintain consistency across multiple AI tool configurations in multi-target environments?

The best way to maintain consistency is migrating target-specific AI configurations into universal-ai-config templates. This standardizes definitions across targets, enabling reuse across environments and teams while simplifying ongoing maintenance.