@caddis/cli 0.0.0 → 0.2.0

package/bundles/antigravity-plugin-extras/skills/file-organizer/SKILL.md

@@ -0,0 +1,434 @@
+---
+name: file-organizer
+context: fork
+description: Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
+---
+
+# File Organizer
+
+This skill acts as your personal organization assistant, helping you maintain a clean, logical file structure across your computer without the mental overhead of constant manual organization.
+
+## When to Use This Skill
+
+- Your Downloads folder is a chaotic mess
+- You can't find files because they're scattered everywhere
+- You have duplicate files taking up space
+- Your folder structure doesn't make sense anymore
+- You want to establish better organization habits
+- You're starting a new project and need a good structure
+- You're cleaning up before archiving old projects
+
+## What This Skill Does
+
+1. **Analyzes Current Structure**: Reviews your folders and files to understand what you have
+2. **Finds Duplicates**: Identifies duplicate files across your system
+3. **Suggests Organization**: Proposes logical folder structures based on your content
+4. **Automates Cleanup**: Moves, renames, and organizes files with your approval
+5. **Maintains Context**: Makes smart decisions based on file types, dates, and content
+6. **Reduces Clutter**: Identifies old files you probably don't need anymore
+
+## How to Use
+
+### From Your Home Directory
+
+```
+cd ~
+```
+
+Then run Claude Code and ask for help:
+
+```
+Help me organize my Downloads folder
+```
+
+```
+Find duplicate files in my Documents folder
+```
+
+```
+Review my project directories and suggest improvements
+```
+
+### Specific Organization Tasks
+
+```
+Organize these downloads into proper folders based on what they are
+```
+
+```
+Find duplicate files and help me decide which to keep
+```
+
+```
+Clean up old files I haven't touched in 6+ months
+```
+
+```
+Create a better folder structure for my [work/projects/photos/etc]
+```
+
+## Instructions
+
+When a user requests file organization help:
+
+1. **Understand the Scope**
+   
+   Ask clarifying questions:
+   - Which directory needs organization? (Downloads, Documents, entire home folder?)
+   - What's the main problem? (Can't find things, duplicates, too messy, no structure?)
+   - Any files or folders to avoid? (Current projects, sensitive data?)
+   - How aggressively to organize? (Conservative vs. comprehensive cleanup)
+
+2. **Analyze Current State**
+   
+   Review the target directory:
+   ```bash
+   # Get overview of current structure
+   ls -la [target_directory]
+   
+   # Check file types and sizes
+   find [target_directory] -type f -exec file {} \; | head -20
+   
+   # Identify largest files
+   du -sh [target_directory]/* | sort -rh | head -20
+   
+   # Count file types
+   find [target_directory] -type f | sed 's/.*\.//' | sort | uniq -c | sort -rn
+   ```
+   
+   Summarize findings:
+   - Total files and folders
+   - File type breakdown
+   - Size distribution
+   - Date ranges
+   - Obvious organization issues
+
+3. **Identify Organization Patterns**
+   
+   Based on the files, determine logical groupings:
+   
+   **By Type**:
+   - Documents (PDFs, DOCX, TXT)
+   - Images (JPG, PNG, SVG)
+   - Videos (MP4, MOV)
+   - Archives (ZIP, TAR, DMG)
+   - Code/Projects (directories with code)
+   - Spreadsheets (XLSX, CSV)
+   - Presentations (PPTX, KEY)
+   
+   **By Purpose**:
+   - Work vs. Personal
+   - Active vs. Archive
+   - Project-specific
+   - Reference materials
+   - Temporary/scratch files
+   
+   **By Date**:
+   - Current year/month
+   - Previous years
+   - Very old (archive candidates)
+
+4. **Find Duplicates**
+   
+   When requested, search for duplicates:
+   ```bash
+   # Find exact duplicates by hash
+   find [directory] -type f -exec md5 {} \; | sort | uniq -d
+   
+   # Find files with same name
+   find [directory] -type f -printf '%f\n' | sort | uniq -d
+   
+   # Find similar-sized files
+   find [directory] -type f -printf '%s %p\n' | sort -n
+   ```
+   
+   For each set of duplicates:
+   - Show all file paths
+   - Display sizes and modification dates
+   - Recommend which to keep (usually newest or best-named)
+   - **Important**: Always ask for confirmation before deleting
+
+5. **Propose Organization Plan**
+   
+   Present a clear plan before making changes:
+   
+   ```markdown
+   # Organization Plan for [Directory]
+   
+   ## Current State
+   - X files across Y folders
+   - [Size] total
+   - File types: [breakdown]
+   - Issues: [list problems]
+   
+   ## Proposed Structure
+   
+   ```
+   [Directory]/
+   ├── Work/
+   │   ├── Projects/
+   │   ├── Documents/
+   │   └── Archive/
+   ├── Personal/
+   │   ├── Photos/
+   │   ├── Documents/
+   │   └── Media/
+   └── Downloads/
+       ├── To-Sort/
+       └── Archive/
+   ```
+   
+   ## Changes I'll Make
+   
+   1. **Create new folders**: [list]
+   2. **Move files**:
+      - X PDFs → Work/Documents/
+      - Y images → Personal/Photos/
+      - Z old files → Archive/
+   3. **Rename files**: [any renaming patterns]
+   4. **Delete**: [duplicates or trash files]
+   
+   ## Files Needing Your Decision
+   
+   - [List any files you're unsure about]
+   
+   Ready to proceed? (yes/no/modify)
+   ```
+
+6. **Execute Organization**
+   
+   After approval, organize systematically:
+   
+   ```bash
+   # Create folder structure
+   mkdir -p "path/to/new/folders"
+   
+   # Move files with clear logging
+   mv "old/path/file.pdf" "new/path/file.pdf"
+   
+   # Rename files with consistent patterns
+   # Example: "YYYY-MM-DD - Description.ext"
+   ```
+   
+   **Important Rules**:
+   - Always confirm before deleting anything
+   - Log all moves for potential undo
+   - Preserve original modification dates
+   - Handle filename conflicts gracefully
+   - Stop and ask if you encounter unexpected situations
+
+7. **Provide Summary and Maintenance Tips**
+   
+   After organizing:
+   
+   ```markdown
+   # Organization Complete! ✨
+   
+   ## What Changed
+   
+   - Created [X] new folders
+   - Organized [Y] files
+   - Freed [Z] GB by removing duplicates
+   - Archived [W] old files
+   
+   ## New Structure
+   
+   [Show the new folder tree]
+   
+   ## Maintenance Tips
+   
+   To keep this organized:
+   
+   1. **Weekly**: Sort new downloads
+   2. **Monthly**: Review and archive completed projects
+   3. **Quarterly**: Check for new duplicates
+   4. **Yearly**: Archive old files
+   
+   ## Quick Commands for You
+   
+   ```bash
+   # Find files modified this week
+   find . -type f -mtime -7
+   
+   # Sort downloads by type
+   [custom command for their setup]
+   
+   # Find duplicates
+   [custom command]
+   ```
+   
+   Want to organize another folder?
+   ```
+
+## Examples
+
+### Example 1: Organizing Downloads (From Justin Dielmann)
+
+**User**: "My Downloads folder is a mess with 500+ files. Help me organize it."
+
+**Process**:
+1. Analyzes Downloads folder
+2. Finds patterns: work docs, personal photos, installers, random PDFs
+3. Proposes structure:
+   - Downloads/
+     - Work/
+     - Personal/
+     - Installers/ (DMG, PKG files)
+     - Archive/
+     - ToSort/ (things needing decisions)
+4. Asks for confirmation
+5. Moves files intelligently based on content and names
+6. Results: 500 files → 5 organized folders
+
+### Example 2: Finding and Removing Duplicates
+
+**User**: "Find duplicate files in my Documents and help me decide which to keep."
+
+**Output**:
+```markdown
+# Found 23 Sets of Duplicates (156 MB total)
+
+## Duplicate Set 1: "proposal.pdf"
+- `/Documents/proposal.pdf` (2.3 MB, modified: 2024-03-15)
+- `/Documents/old/proposal.pdf` (2.3 MB, modified: 2024-03-15)
+- `/Desktop/proposal.pdf` (2.3 MB, modified: 2024-03-10)
+
+**Recommendation**: Keep `/Documents/proposal.pdf` (most recent in correct location)
+Delete the other 2 copies?
+
+[Continue for all duplicates...]
+```
+
+### Example 3: Restructuring Projects Folder
+
+**User**: "Review my ~/Projects directory and suggest improvements."
+
+**Output**:
+```markdown
+# Analysis of ~/Projects
+
+## Current Structure Issues
+- Mix of active and archived projects (3+ years old)
+- No consistent naming convention
+- Some projects at root, others in random subfolders
+- Duplicate folders (project-name, project-name-old, project-name-v2)
+
+## Proposed Structure
+
+```
+Projects/
+├── Active/
+│   ├── client-work/
+│   ├── side-projects/
+│   └── learning/
+├── Archive/
+│   ├── 2022/
+│   ├── 2023/
+│   └── 2024/
+└── Templates/
+```
+
+## Specific Changes
+1. Move 12 projects not touched since 2022 → Archive/
+2. Consolidate 4 duplicate project folders
+3. Rename projects to consistent format: "client-name-project-name"
+4. Create Archive for old work
+
+Want me to implement this?
+```
+
+### Example 4: Organizing Photos by Date
+
+**User**: "Organize my photo folders by year and month."
+
+**Output**: Creates structure like:
+```
+Photos/
+├── 2023/
+│   ├── 01-January/
+│   ├── 02-February/
+│   └── ...
+├── 2024/
+│   ├── 01-January/
+│   └── ...
+└── Unsorted/
+```
+
+Then moves photos based on EXIF data or file modification dates.
+
+## Common Organization Tasks
+
+### Downloads Cleanup
+```
+Organize my Downloads folder - move documents to Documents, 
+images to Pictures, keep installers separate, and archive files 
+older than 3 months.
+```
+
+### Project Organization
+```
+Review my Projects folder structure and help me separate active 
+projects from old ones I should archive.
+```
+
+### Duplicate Removal
+```
+Find all duplicate files in my Documents folder and help me 
+decide which ones to keep.
+```
+
+### Desktop Cleanup
+```
+My Desktop is covered in files. Help me organize everything into 
+my Documents folder properly.
+```
+
+### Photo Organization
+```
+Organize all photos in this folder by date (year/month) based 
+on when they were taken.
+```
+
+### Work/Personal Separation
+```
+Help me separate my work files from personal files across my 
+Documents folder.
+```
+
+## Pro Tips
+
+1. **Start Small**: Begin with one messy folder (like Downloads) to build trust
+2. **Regular Maintenance**: Run weekly cleanup on Downloads
+3. **Consistent Naming**: Use "YYYY-MM-DD - Description" format for important files
+4. **Archive Aggressively**: Move old projects to Archive instead of deleting
+5. **Keep Active Separate**: Maintain clear boundaries between active and archived work
+6. **Trust the Process**: Let Claude handle the cognitive load of where things go
+
+## Best Practices
+
+### Folder Naming
+- Use clear, descriptive names
+- Avoid spaces (use hyphens or underscores)
+- Be specific: "client-proposals" not "docs"
+- Use prefixes for ordering: "01-current", "02-archive"
+
+### File Naming
+- Include dates: "2024-10-17-meeting-notes.md"
+- Be descriptive: "q3-financial-report.xlsx"
+- Avoid version numbers in names (use version control instead)
+- Remove download artifacts: "document-final-v2 (1).pdf" → "document.pdf"
+
+### When to Archive
+- Projects not touched in 6+ months
+- Completed work that might be referenced later
+- Old versions after migration to new systems
+- Files you're hesitant to delete (archive first)
+
+## Related Use Cases
+
+- Setting up organization for a new computer
+- Preparing files for backup/archiving
+- Cleaning up before storage cleanup
+- Organizing shared team folders
+- Structuring new project directories
+

package/bundles/antigravity-plugin-extras/skills/game-changing-features/README.md

@@ -0,0 +1,221 @@
+# Game-Changing Features
+
+A strategic product thinking skill that helps identify 10x opportunities and high-leverage improvements for your product.
+
+## Purpose
+
+This skill shifts your mindset from incremental improvements to transformative thinking. Instead of asking "what feature should we add next?", it asks "what would make this 10x more valuable?" It's designed for founders, product managers, and teams who want to find the moves that make users unable to live without their product.
+
+## When to Use
+
+Activate this skill when you need:
+
+- Strategic product thinking and prioritization
+- To identify high-impact features that differentiate from competitors
+- To find quick wins with outsized impact
+- To explore what would make your product 10x better
+- Product strategy discussions about "what should we build next?"
+- To validate if you're working on the right things
+
+Trigger phrases include:
+- "What would make this 10x better?"
+- "Product strategy"
+- "What should we build next?"
+- "10x opportunities"
+- "Game-changing features"
+- "High-leverage improvements"
+
+## How It Works
+
+### The Approach
+
+This skill follows a structured 5-step workflow:
+
+1. **Understand Current Value** - Deep dive into what the product does today, who uses it, and why
+2. **Find 10x Opportunities** - Think across three scales (Massive, Medium, Small)
+3. **Evaluate Ruthlessly** - Score ideas on impact, reach, frequency, differentiation, defensibility, and feasibility
+4. **Identify Highest-Leverage Moves** - Find quick wins, strategic bets, and compounding features
+5. **Prioritize** - Stack rank into Do Now, Do Next, Explore, and Backlog
+
+### Three Scales of Thinking
+
+**Massive (High effort, transformative)**
+- Features that fundamentally expand what the product can do
+- Opens new markets, use cases, or capabilities
+- Makes competitors nervous
+
+**Medium (Moderate effort, high leverage)**
+- Significantly enhances the core experience
+- Force multipliers on what already works
+- Turns casual users into power users
+
+**Small Gems (Low effort, disproportionate value)**
+- Tiny changes that punch way above their weight
+- Often overlooked because they seem "too simple"
+- Single buttons/shortcuts that save minutes daily
+
+### Evaluation Framework
+
+Each idea is assessed across 6 criteria:
+
+| Criteria | Question |
+|----------|----------|
+| Impact | How much more valuable does this make the product? |
+| Reach | What % of users would this affect? |
+| Frequency | How often would users encounter this value? |
+| Differentiation | Does this set us apart or just match competitors? |
+| Defensibility | Is this easy to copy or does it compound over time? |
+| Feasibility | Can we actually build this? |
+
+Scoring:
+- 🔥 **Must do** - High impact, clearly worth it
+- 👍 **Strong** - Good impact, should prioritize
+- 🤔 **Maybe** - Interesting but needs more thought
+- ❌ **Pass** - Not worth it right now
+
+## Key Features
+
+### Systematic Exploration
+
+Forces you through 10 idea categories to ensure comprehensive coverage:
+
+- Speed - What takes too long?
+- Automation - What's repetitive?
+- Intelligence - What could be smarter?
+- Integration - What else do users use?
+- Collaboration - How do users work together?
+- Personalization - How is everyone different?
+- Visibility - What's hidden that shouldn't be?
+- Confidence - What creates anxiety?
+- Delight - What could spark joy?
+- Access - Who can't use this yet?
+
+### Documentation-First
+
+All session outputs are saved to `.claude/docs/ai/<product-or-area>/10x/session-N.md`. This ensures:
+- Full traceability of strategic thinking
+- Easy sharing with team members
+- Historical record of decisions
+- No chat clutter - pure strategy focus
+
+### Pure Strategy Mode
+
+This skill is **code-free**. No implementation, no prototypes - just strategic thinking. Implementation comes later, after you've identified the right moves.
+
+## Usage Examples
+
+### Example 1: SaaS Dashboard Product
+
+```
+User: I want to think about 10x opportunities for our analytics dashboard
+
+[Skill activates and guides through:]
+1. Understanding current dashboard capabilities
+2. Exploring opportunities like:
+   - Massive: AI-powered anomaly detection that auto-investigates issues
+   - Medium: Collaborative annotations and shared insights
+   - Small: One-click report scheduling from any view
+3. Prioritizing quick wins vs strategic bets
+4. Output saved to `.claude/docs/ai/analytics-dashboard/10x/session-1.md`
+```
+
+### Example 2: Mobile App
+
+```
+User: What would make our fitness app 10x better?
+
+[Skill explores:]
+- Speed: Instant workout logging with voice
+- Automation: Smart rest day recommendations
+- Intelligence: Predictive injury prevention
+- Collaboration: Virtual workout buddies
+- Delight: Achievement celebrations that don't feel gamified
+
+[Result: Prioritized list of 15 opportunities with clear next steps]
+```
+
+### Example 3: Developer Tool
+
+```
+User: Product strategy session for our API testing tool
+
+[Skill identifies:]
+- Do Now: Auto-generate test cases from API docs (2 weeks, huge value)
+- Do Next: Team collaboration with shared test suites (1 month, unlocks enterprise)
+- Explore: AI that writes tests by watching you use the API (3 months, could be transformative)
+
+[Output: Full strategic document with rationale and risk assessment]
+```
+
+## What You Get
+
+After a session, you'll have:
+
+- **Current Value Assessment** - Clear understanding of your product's core value proposition
+- **Categorized Opportunities** - Ideas organized by scale (Massive/Medium/Small)
+- **Scored Ideas** - Each opportunity evaluated on 6 criteria with clear scoring
+- **Prioritized Roadmap** - Stack-ranked into Do Now / Do Next / Explore / Backlog
+- **Evidence-Based Reasoning** - Ideas grounded in codebase research and user behavior
+- **Unblocked Questions** - Clear list of assumptions to validate and decisions to make
+
+## Core Principles
+
+1. **Think Big First** - Don't self-censor with "that's too hard"
+2. **Small Can Be Huge** - Don't dismiss simple ideas; sometimes one button changes everything
+3. **User Value > Feature Count** - 10 features adding 1% each ≠ 1 feature adding 10x
+4. **Be Specific** - "Better UX" is not an idea; "One-click rescheduling from notification" is
+5. **Question Assumptions** - "Users want X" may be wrong
+6. **Compound Thinking** - Prefer features that get better over time
+7. **No Safe Ideas** - If every idea is "obviously good," you're not thinking hard enough
+8. **Cite Evidence** - Reference what you saw in codebase or research
+
+## Tips for Best Results
+
+### Before Starting
+
+Provide context on:
+- Product/Area you're thinking about
+- Current state (brief description)
+- Constraints (technical limits, timeline, team size)
+
+### During the Session
+
+- Be open to uncomfortable ideas
+- Push back on assumptions
+- Ask "what would make users tell their friends?"
+- Consider both 10x team size and 1/10th team size scenarios
+
+### After the Session
+
+- Validate key assumptions with users
+- Share the strategic document with your team
+- Pick 1-2 quick wins to test first
+- Revisit and update as you learn
+
+## Output Location
+
+All sessions are saved to:
+```
+.claude/docs/ai/<product-or-area>/10x/session-N.md
+```
+
+This keeps your strategic thinking organized, searchable, and shareable with your team.
+
+## Not Included
+
+This skill does NOT:
+- Write code or implementation plans (use after strategy is clear)
+- Make final decisions (provides recommendations, you decide)
+- Replace user research (complements it with strategic analysis)
+- Guarantee success (identifies high-potential opportunities to test)
+
+## Related Skills
+
+- `feature-planning` - For breaking down chosen features into implementation plans
+- `implementation-blueprint` - For architecting how to build selected opportunities
+- `dev-spec` - For creating detailed specs after strategy is set
+- `critical-brainstorm` - For stress-testing specific ideas before committing
+
+---
+
+**Remember**: This skill is about finding the moves that matter. Not every idea will work, but the goal is to identify the ones worth testing that could fundamentally change your product's trajectory.