$ lovelace chat

🤖 Lovelace CLI v1.0.0

You: I need to organize my project files. They're a disaster.

🤖 I can help with that! Let me understand what we're working with.

A few questions:
1. What type of project is this? (code, design files, documentation, mixed)
2. Roughly how many files are we talking about?
3. What's the biggest problem? (can't find things, unclear naming, mixed content types?)

You: It's a design system project - Figma files, component documentation, design tokens, and some React code. Maybe 200+ files across 15 folders. The problem is I can't find anything and neither can my team.

🤖 Got it - a multi-format design system with findability issues. Let's start with a quick audit.

Can you share your current folder structure? You can use:
  • Paste it here
  • Or run: ls -R (Mac/Linux) or tree (if installed)

You: /context ./

🤖 Thanks! I can see your project structure now. Let me analyze it:

**Current State Analysis:**

📁 Root Issues:
• 8 folders at root level - no clear hierarchy
• Mix of asset types in same folders
• Inconsistent naming (camelCase, snake_case, spaces)

Example of chaos I see:

**Top 3 Problems:**
1. **No separation** of Figma files vs code vs docs
2. **Versioning nightmare** (v2, old-, final- in names)
3. **Duplicate/outdated** files everywhere

Want me to propose a new structure?

You: Yes, propose a structure

🤖 **Proposed Organization Structure:**

**Key Principles:**
• Separate by **function** (design, code, docs)
• Clear **naming** hierarchy
• Archive instead of delete
• Single source of truth per asset

Want me to create a migration plan?

You: Create naming conventions for all these file types

🤖 **Naming Convention Guide**

**1. Figma Files**
Format: `[category]-[name]-[version].[stage].fig`

Examples:

Rules:
• Lowercase with hyphens
• Version number (v1, v2, v3)
• Optional stage suffix (.draft, .review, .approved)
• No spaces or underscores

**2. React Components**
Format: `PascalCase.tsx`

Examples:

Rules:
• PascalCase (capital first letter)
• Descriptive, not abbreviated
• No version numbers (use git)

**3. Design Tokens**
Format: `category.tokens.json`

Examples:

Rules:
• Lowercase
• Always `.tokens.json` suffix
• Category name describes content

**4. Documentation**
Format: `component-name.md`

Examples:

Rules:
• Lowercase with hyphens
• Markdown extension
• Match component name exactly

**5. Exported Assets**
Format: `component-name-variant-size.extension`

Examples:

Rules:
• Lowercase with hyphens
• Include all relevant metadata in name
• Descriptive, not cryptic

**6. Archive Files**
Format: `original-name.YYYY-MM-DD.extension`

Examples:

Rules:
• Preserve original name
• Add ISO date before extension
• Never delete, always archive

Want me to create a rename script for your current files?

You: Yes, show me what would change

🤖 **Proposed Renaming**

I'll show you what would change with examples from each category:

**Figma Files (15 files):**

**React Components (28 files):**

**Documentation (42 files):**

**Design Tokens (8 files):**

**Total Changes:**
• 93 files to rename
• 87 files to move
• 12 duplicates to archive

**Risk Assessment:**
🟢 Low risk - Most are static assets
🟡 Medium risk - 28 component imports may need updating
🔴 No high-risk changes

Want me to:
1. Generate shell script to perform these changes
2. Create step-by-step manual instructions
3. Show just high-priority changes first

You: Show step-by-step manual instructions

🤖 **Manual Migration Guide**

**Phase 1: Create New Structure (15 minutes)**

Step 1: Create new folders
```bash
mkdir -p design/{figma/{components,foundations,patterns},exports,archive}
mkdir -p code/{components,tokens,utils}
mkdir -p docs/{guides,reference,decisions}
mkdir -p assets/{images,fonts}
mkdir -p admin/{meetings,roadmap,archive}

tree -L 2 .

Current location: /components/Button v2.fig
New location: design/figma/components/components-button-v2.fig

Actions:
1. Open file in Figma
2. "Save As" → rename to new convention
3. Save to new location
4. Verify file opens correctly
5. Move original to design/archive/ with date

Priority files to move:
1. Button Component.md → docs/reference/button.md
2. Installation Guide.md → docs/guides/installation.md
3. README.txt → README.md (root level)

Let me search your docs for file references and suggest updates.

[AI searches and finds]:
• 12 docs reference old file paths
• 8 Figma links need updating
• 5 component imports need fixing

Don't delete! Move to appropriate archive:
• Old Figma files → design/archive/
• Old docs → admin/archive/
• Old code → code/archive/ (create if needed)

Document what changed, why, and where things are now.
This helps your team adjust.

---

## Phase 3: Documentation Update (45 minutes)

Alex creates documentation for the new structure:

design/
├── figma/         # Source Figma files
├── exports/       # Generated PNG/SVG
└── archive/       # Old versions (don't delete)

code/
├── components/    # React components
├── tokens/        # JSON design tokens
└── utils/         # Helper functions

docs/
├── guides/        # Step-by-step tutorials
├── reference/     # Component documentation
└── decisions/     # Why we made certain choices

Format: category-name-version.fig
Example: components-button-v3.fig

Format: ComponentName.tsx
Example: Button.tsx

Format: component-name.md
Example: button.md

Format: category.tokens.json
Example: colors.tokens.json

**What happened:**
- ✅ Created clear, scannable documentation
- ✅ Included visual structure diagrams
- ✅ Added "how to find things" guidance
- ✅ Covered common questions

---

## Phase 4: Team Onboarding (30 minutes)

Creating materials to help the team adapt:

Figma:        components-button-v3.fig
React:        Button.tsx
Docs:         button.md
Tokens:       colors.tokens.json
Exports:      icon-close-24px.svg
Archives:     old-file.2024-01-15.fig

Don't delete!
Move to archive folder with date:
old-button.2024-01-15.fig

---

## What Alex Accomplished

In **2-3 hours**, Alex:

1. ✅ Audited current mess and identified problems
2. ✅ Designed logical organization structure
3. ✅ Created comprehensive naming conventions
4. ✅ Generated step-by-step migration guide
5. ✅ Documented new structure in README
6. ✅ Created team quick reference guide

**No coding required**—just conversational problem-solving with AI.

## Key Takeaways

### Universal File Organization Principles

The AI helped Alex apply proven organizational principles:
- **Separation of concerns** (design vs code vs docs)
- **Consistent naming** (predictable = findable)
- **Never delete** (archive with dates)
- **Single source of truth** (one place per file type)

### For Anyone Managing Information

You can use this workflow for:
- Personal file organization
- Team shared drives
- Documentation systems
- Asset management
- Knowledge bases

### Best Practices

**Start with assessment:**
- Show AI your current state
- Let it identify specific problems
- Get objective analysis

**Iterate on structure:**
- Propose ideal structure
- Refine based on constraints
- Validate with AI before implementing

**Document everything:**
- README for high-level structure
- Quick reference for daily use
- Migration guide for transition

**Communicate clearly:**
- Explain why changes were made
- Provide before/after examples
- Make it easy to adapt

## Try It Yourself

Start organizing your files:

```bash
$ lovelace chat "Help me organize my project files"