TETRA2000/import-project

Import Project Skill

Parameters

• archivePath (required): Path to the .tar.gz archive to import
• conflictStrategy (optional): rename, replace, or skip (default: ask user per conflict)

Workflow

1. Extract and Inspect

• Extract the archive to a temporary directory
• Read the manifest.json
• List all files to be imported

2. Check Conflicts

For each component in the manifest:

• Check if src/components/{Name}/ already exists
• If conflict found, apply conflict strategy:
  • rename: Import as {Name}2 (or next available number)
  • replace: Overwrite existing files
  • skip: Do not import this component

For the page:

• Check if src/pages/{route}/ already exists
• Apply same conflict strategy

3. Import Files

• Copy page file to src/pages/{route}/index.tsx
• Copy component directories to src/components/{Name}/
• Merge design tokens if different (warn user of conflicts)

4. Update Indexes

• Add imported components to docs/components.md
• Add imported page to docs/pages.md
• Update shared/references/component-registry.md

5. Verify

• Run npm run build to verify no import errors
• Report any missing dependencies

Output

Report:

1. Files imported (list)
2. Files skipped (if conflicts)
3. Files renamed (if conflicts)
4. Index documents updated
5. Build verification result