@caddis/cli 0.4.10 → 0.4.12

package/bundles/antigravity-plugin-extras/skills/domain-name-brainstormer/SKILL.md

@@ -1,213 +0,0 @@
----
-name: domain-name-brainstormer
-context: fork
-description: Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
----
-
-# Domain Name Brainstormer
-
-This skill helps you find the perfect domain name for your project by generating creative options and checking what's actually available to register.
-
-## When to Use This Skill
-
-- Starting a new project or company
-- Launching a product or service
-- Creating a personal brand or portfolio site
-- Rebranding an existing project
-- Registering a domain for a side project
-- Finding available alternatives when your first choice is taken
-
-## What This Skill Does
-
-1. **Understands Your Project**: Analyzes what you're building and who it's for
-2. **Generates Creative Names**: Creates relevant, memorable domain options
-3. **Checks Availability**: Verifies which domains are actually available across multiple TLDs
-4. **Multiple Extensions**: Suggests .com, .io, .dev, .ai, .app, and more
-5. **Provides Alternatives**: Offers variations if top choices are taken
-6. **Branding Insights**: Explains why certain names work well
-
-## How to Use
-
-### Basic Brainstorming
-
-```
-I'm building a project management tool for remote teams. 
-Suggest domain names.
-```
-
-```
-Help me brainstorm domain names for a personal finance app
-```
-
-### Specific Preferences
-
-```
-I need a domain name for my AI writing assistant. 
-Prefer short names with .ai or .io extension.
-```
-
-### With Keywords
-
-```
-Suggest domain names using the words "pixel" or "studio" 
-for my design agency
-```
-
-## Example
-
-**User**: "I'm building a tool for developers to share code snippets. Suggest creative domain names."
-
-**Output**:
-```
-Analyzing your project...
-Target audience: Developers
-Key features: Code sharing, snippets, collaboration
-
-🎯 Domain Name Suggestions
-
-## Available (.com)
-1. ✓ snippetbox.com - Clear, memorable, available!
-   Why: Directly describes the product, easy to remember
-
-2. ✓ codeclip.com - Short and snappy
-   Why: Implies quick code sharing, only 8 characters
-
-3. ✓ devpaste.com - Developer-focused
-   Why: Familiar to devs (like pastebin), clear purpose
-
-## Available (Alternative TLDs)
-4. ✓ snippet.dev - Perfect extension for developers
-   Why: .dev extension signals developer tool
-
-5. ✓ codebox.io - Tech-forward
-   Why: .io popular with tech startups, clean name
-
-6. ✓ sharecode.app - Descriptive
-   Why: .app extension, clearly states the action
-
-## Premium/Taken (.com)
-- codeshare.com (Taken, est. $2,500)
-- snippets.com (Taken, premium domain)
-
-## Recommendations
-
-🏆 Top Pick: snippet.dev
-- Perfect for developer audience
-- Short and memorable  
-- .dev extension adds credibility
-- Available now!
-
-🥈 Runner-up: snippetbox.com
-- .com is universally recognized
-- Slightly longer but descriptive
-- Great brandability
-
-Next steps:
-1. Register your favorite before someone else does!
-2. Want me to check more variations?
-3. Need help with logo ideas for these names?
-```
-
-**Inspired by:** Ben Aiad's use case from Lenny's Newsletter
-
-## Domain Naming Tips
-
-### What Makes a Good Domain
-
-✓ **Short**: Under 15 characters ideal
-✓ **Memorable**: Easy to recall and spell
-✓ **Pronounceable**: Can be said in conversation
-✓ **Descriptive**: Hints at what you do
-✓ **Brandable**: Unique enough to stand out
-✓ **No hyphens**: Easier to share verbally
-
-### TLD Guide
-
-- **.com**: Universal, trusted, great for businesses
-- **.io**: Tech startups, developer tools
-- **.dev**: Developer-focused products
-- **.ai**: AI/ML products
-- **.app**: Mobile or web applications
-- **.co**: Alternative to .com
-- **.xyz**: Modern, creative projects
-- **.design**: Creative/design agencies
-- **.tech**: Technology companies
-
-## Advanced Features
-
-### Check Similar Variations
-
-```
-Check availability for "codebase" and similar variations 
-across .com, .io, .dev
-```
-
-### Industry-Specific
-
-```
-Suggest domain names for a sustainable fashion brand, 
-checking .eco and .fashion TLDs
-```
-
-### Multilingual Options
-
-```
-Brainstorm domain names in English and Spanish for 
-a language learning app
-```
-
-### Competitor Analysis
-
-```
-Show me domain patterns used by successful project 
-management tools, then suggest similar available ones
-```
-
-## Example Workflows
-
-### Startup Launch
-1. Describe your startup idea
-2. Get 10-15 domain suggestions across TLDs
-3. Review availability and pricing
-4. Pick top 3 favorites
-5. Register immediately
-
-### Personal Brand
-1. Share your name and profession
-2. Get variations (firstname.com, firstnamelastname.dev, etc.)
-3. Check social media handle availability too
-4. Register consistent brand across platforms
-
-### Product Naming
-1. Describe product and target market
-2. Get creative, brandable names
-3. Check trademark conflicts
-4. Verify domain and social availability
-5. Test names with target audience
-
-## Tips for Success
-
-1. **Act Fast**: Good domains get taken quickly
-2. **Register Variations**: Get .com and .io to protect brand
-3. **Avoid Numbers**: Hard to communicate verbally
-4. **Check Social Media**: Make sure @username is available too
-5. **Say It Out Loud**: Test if it's easy to pronounce
-6. **Check Trademarks**: Ensure no legal conflicts
-7. **Think Long-term**: Will it still make sense in 5 years?
-
-## Pricing Context
-
-When suggesting domains, I'll note:
-- Standard domains: ~$10-15/year
-- Premium TLDs (.io, .ai): ~$30-50/year
-- Taken domains: Market price if listed
-- Premium domains: $hundreds to $thousands
-
-## Related Tools
-
-After picking a domain:
-- Check logo design options
-- Verify social media handles
-- Research trademark availability
-- Plan brand identity colors/fonts
-

package/bundles/antigravity-plugin-extras/skills/humanizer/SKILL.md

@@ -1,194 +0,0 @@
----
-name: humanizer
-description: Identify and remove AI writing patterns from text to make it sound natural and human. Covers 29 documented LLM output patterns. Use when asked to humanize, de-AI, un-ChatGPT, or rewrite drafts (blogs, docs, emails, PRs, releases) to sound authentic.
-source: NousResearch/hermes-agent
-license: MIT
----
-
-# Humanizer
-
-Remove AI-generated writing patterns and restore authentic voice. Based on Wikipedia's "Signs of AI writing" guide and Siqi Chen's original [blader/humanizer](https://github.com/blader/humanizer) (MIT).
-
-**Core insight**: LLMs guess statistically likely continuations. The result trends toward the most probable phrasing — which is how telltale patterns get baked in. Removing them is necessary but not sufficient. The output also needs personality.
-
-## When to Load
-
-- "Humanize this", "de-AI this", "un-ChatGPT this"
-- "Rewrite this to sound more natural"
-- "This sounds like it was written by AI"
-- Before publishing: blog posts, release notes, docs, emails, social posts
-- Applying to Claude's own output in a conversation
-
-## Input Methods
-
-1. **Inline** — user pastes text; rewrite in place
-2. **File** — `read_file` to load, `write_file` or `patch` to apply
-3. **Voice calibration** — user provides a writing sample to match their tone
-
-## The 29 AI Patterns
-
-### Content Patterns (1–6)
-
-**1. Undue significance/legacy emphasis**
-Watch for: "stands as," "testament to," "pivotal moment," "broader trends"
-Fix: Replace with the specific fact, not the editorial wrapper
-
-**2. Undue notability/media emphasis**
-Watch for: "cited by," "leading expert," "active on social media"
-Fix: Either state the credential specifically or cut it
-
-**3. Superficial analysis with -ing endings**
-Watch for: "highlighting," "underscoring," "reflecting," "symbolizing," "demonstrating"
-Fix: Rewrite as a direct statement of what the fact means
-
-**4. Promotional / ad-copy language**
-Watch for: "nestled," "vibrant," "breathtaking," "stunning," "renowned," "world-class"
-Fix: Describe the actual attribute instead of the adjective
-
-**5. Vague attributions / weasel words**
-Watch for: "experts argue," "industry reports suggest," "observers cite"
-Fix: Name the source or cut the attribution entirely
-
-**6. Formulaic "Challenges and Future Prospects" sections**
-Watch for: Sections that end with "Despite challenges..." followed by optimistic filler
-Fix: Either include specific named challenges or remove the section
-
-### Language & Grammar Patterns (7–13)
-
-**7. Overused AI vocabulary**
-Post-2023 words that appear far more in AI text than human text:
-`actually`, `crucial`, `delve`, `landscape`, `tapestry`, `underscore`, `interplay`, `intricacies`, `groundbreaking`, `revolutionary`, `unleash`, `game-changing`, `seamlessly`, `robust`
-Fix: Replace with plain language or cut
-
-**8. Copula avoidance** (replacing "is" with indirect constructions)
-Watch for: "serves as," "marks," "boasts," "features," "represents"
-Fix: Use "is" or rewrite directly — "X serves as a hub" → "X is a hub"
-
-**9. Negative parallelisms / tailing negations**
-Watch for: "not only...but," sentence-ending fragments like "no guessing required"
-Fix: Write complete parallel clauses
-
-**10. Rule-of-three overuse**
-Watch for: Every point being grouped into exactly three items
-Fix: Use the number the content actually requires
-
-**11. Elegant variation** (synonym substitution to avoid repetition)
-Watch for: The same concept referred to by a different word every sentence
-Fix: Repeat the word if that's what you mean — humans do this
-
-**12. False ranges**
-Watch for: "From A to B" where A and B aren't on a meaningful spectrum
-Fix: Drop the range framing; state the things directly
-
-**13. Passive voice / subjectless fragments**
-Watch for: "It was determined that," "Steps were taken to"
-Fix: Name the actor — "We determined," "The team took steps"
-
-### Style Patterns (14–19)
-
-**14. Em dash overuse**
-LLMs use "—" far more than humans. Replace with commas, periods, colons, or parentheses in most cases.
-
-**15. Overuse of boldface**
-Mechanical emphasis bolding every third concept. Remove unless the bold is doing real work.
-
-**16. Inline-header vertical lists**
-Pattern: **Bold phrase**: followed by description, repeated. Fix: Rewrite as flowing prose unless it's genuinely tabular.
-
-**17. Title Case Headings**
-Only capitalize the first word and proper nouns. Not Every Main Word.
-
-**18. Decorative emojis**
-Remove emojis from headings, bullet points, and lists unless the context requires them (Slack messages, social posts).
-
-**19. Curly quotation marks**
-Use straight quotes ("...") not curly ("...") in code contexts.
-
-### Communication Patterns (20–22)
-
-**20. Collaborative chatbot artifacts**
-Remove: "I hope this helps!", "Let me know if you need anything!", "Certainly!", "Of course!", "Great question!"
-
-**21. Knowledge-cutoff disclaimers**
-Strip: "as of my last update," "based on available information," "while I cannot verify"
-
-**22. Sycophantic / servile tone**
-Remove excessive positivity, hedging-to-please, and "let me know what you think" endings
-
-### Filler & Hedging (23–29)
-
-**23. Filler phrases**
-| Replace | With |
-|---------|------|
-| "in order to" | "to" |
-| "due to the fact that" | "because" |
-| "at this point in time" | "now" |
-| "it is important to note that" | just state the fact |
-| "please note that" | just state the fact |
-
-**24. Excessive hedging**
-"could potentially possibly be argued to suggest" → "may suggest" or just "suggests"
-
-**25. Generic positive conclusions**
-"the future looks bright" / "exciting times ahead" → state a specific fact or expectation, or cut entirely
-
-**26. Hyphenated word-pair overuse**
-`cross-functional`, `data-driven`, `client-facing`, `best-in-class` — vary usage or replace with plain language
-
-**27. Persuasive authority tropes**
-Remove: "at its core," "the real question is," "what really matters here," "the key insight is"
-
-**28. Signposting / meta-announcements**
-Cut: "let's dive in," "here's what you need to know," "without further ado," "in this article, we will"
-
-**29. Fragmented headers**
-Headers that just restate the section name as a sentence, contributing no information. Remove or make specific.
-
-## Adding Soul (Required — Not Optional)
-
-Removing AI patterns alone leaves soulless prose. Signs your rewrite is still lifeless:
-- Uniform sentence length throughout
-- No opinions, only neutral reporting
-- No acknowledgment of uncertainty or complexity
-- Missing first-person perspective where appropriate
-- No humor, specificity, or texture
-
-**How to add voice:**
-- Have opinions — react to facts, don't just present them
-- Vary rhythm — alternate short punchy sentences with longer ones
-- Acknowledge complexity — "this is messier than it sounds"
-- Use "I" where honest
-- Allow specific details — exact numbers, real names, concrete comparisons
-- Let tangents exist — a brief aside feels human
-
-## Voice Calibration (Optional)
-
-If the user provides a writing sample:
-1. Analyze: sentence length patterns, word choice register, paragraph starters, punctuation habits, recurring phrases
-2. Mirror those patterns in the rewrite
-3. Don't just remove AI patterns — replace them with patterns from the sample
-
-## Process
-
-1. Read input (use `read_file` if a file path is given)
-2. Identify all pattern instances (annotate mentally)
-3. Rewrite problematic sections
-4. Inject voice — opinions, rhythm variation, specificity
-5. Present draft rewrite
-6. Self-audit: "What still sounds AI-generated?" (brief bullets)
-7. Address remaining tells
-8. Present final version
-9. For file edits: apply with `patch` (targeted) or `write_file` (full)
-
-## Output Format
-
-```
-DRAFT REWRITE
-[rewritten text]
-
-REMAINING TELLS
-- [bullet: what still sounds AI-generated and why]
-
-FINAL REWRITE
-[final version addressing the tells]
-```

package/bundles/antigravity-plugin-extras/skills/image-enhancer/SKILL.md

@@ -1,100 +0,0 @@
----
-name: image-enhancer
-context: fork
-description: Improves the quality of images, especially screenshots, by enhancing resolution, sharpness, and clarity. Perfect for preparing images for presentations, documentation, or social media posts.
----
-
-# Image Enhancer
-
-This skill takes your images and screenshots and makes them look better—sharper, clearer, and more professional.
-
-## When to Use This Skill
-
-- Improving screenshot quality for blog posts or documentation
-- Enhancing images before sharing on social media
-- Preparing images for presentations or reports
-- Upscaling low-resolution images
-- Sharpening blurry photos
-- Cleaning up compressed images
-
-## What This Skill Does
-
-1. **Analyzes Image Quality**: Checks resolution, sharpness, and compression artifacts
-2. **Enhances Resolution**: Upscales images intelligently
-3. **Improves Sharpness**: Enhances edges and details
-4. **Reduces Artifacts**: Cleans up compression artifacts and noise
-5. **Optimizes for Use Case**: Adjusts based on intended use (web, print, social media)
-
-## How to Use
-
-### Basic Enhancement
-
-```
-Improve the image quality of screenshot.png
-```
-
-```
-Enhance all images in this folder
-```
-
-### Specific Improvements
-
-```
-Upscale this image to 4K resolution
-```
-
-```
-Sharpen this blurry screenshot
-```
-
-```
-Reduce compression artifacts in this image
-```
-
-### Batch Processing
-
-```
-Improve the quality of all PNG files in this directory
-```
-
-## Example
-
-**User**: "Improve the image quality of screenshot-2024.png"
-
-**Output**:
-```
-Analyzing screenshot-2024.png...
-
-Current specs:
-- Resolution: 1920x1080
-- Format: PNG
-- Quality: Good, but slight blur
-
-Enhancements applied:
-✓ Upscaled to 2560x1440 (retina)
-✓ Sharpened edges
-✓ Enhanced text clarity
-✓ Optimized file size
-
-Saved as: screenshot-2024-enhanced.png
-Original preserved as: screenshot-2024-original.png
-```
-
-**Inspired by:** Lenny Rachitsky's workflow from his newsletter - used for screenshots in his articles
-
-## Tips
-
-- Always keeps original files as backup
-- Works best with screenshots and digital images
-- Can batch process entire folders
-- Specify output format if needed (PNG for quality, JPG for smaller size)
-- For social media, mention the platform for optimal sizing
-
-## Common Use Cases
-
-- **Blog Posts**: Enhance screenshots before publishing
-- **Documentation**: Make UI screenshots crystal clear
-- **Social Media**: Optimize images for Twitter, LinkedIn, Instagram
-- **Presentations**: Upscale images for large screens
-- **Print Materials**: Increase resolution for physical media
-