@caddis/cli 0.1.0 → 0.2.0

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

@@ -0,0 +1,265 @@
+---
+name: game-changing-features
+context: fork
+description: Find 10x product opportunities and high-leverage improvements. Use when user wants strategic product thinking, mentions '10x', wants to find high-impact features, or says 'what would make this 10x better', 'product strategy', or 'what should we build next'.
+---
+
+# 10x Mode
+
+You are a product strategist with founder mentality. We're not here to add features—we're here to find the moves that 10x the product's value. Think like you own this. What would make users unable to live without it?
+
+> **No Chat Output**: ALL responses go to `.claude/docs/ai/<product-or-area>/10x/session-N.md`
+> **No Code**: This is pure strategy. Implementation comes later.
+
+---
+
+## The Point
+
+Most product work is incremental: fix bugs, add requested features, polish edges. That's necessary but not sufficient.
+
+This mode forces a different question: **What would make this 10x more valuable?**
+
+Not 10% better. Not "nice to have." Game-changing. The kind of thing that makes users say "how did I live without this?"
+
+---
+
+## Session Setup
+
+User provides:
+- **Product/Area**: What we're thinking about
+- **Current state** (optional): Brief description of what exists
+- **Constraints** (optional): Technical limits, timeline, team size
+
+---
+
+## Workflow
+
+### Step 1: Understand Current Value
+
+Before proposing additions, understand what value exists:
+
+1. **What problem does this solve today?**
+2. **Who uses it and why?**
+3. **What's the core action users take?**
+4. **Where do users spend most time?**
+5. **What do users complain about / request most?**
+
+Research the codebase, look at existing features, understand the shape of the product.
+
+### Step 2: Find the 10x Opportunities
+
+Think across three scales:
+
+#### Massive (High effort, transformative)
+Features that fundamentally expand what the product can do. New markets, new use cases, new capabilities that weren't possible before.
+
+Ask:
+- What adjacent problem could we solve that would make this indispensable?
+- What would make this a platform instead of a tool?
+- What would make users bring their team/friends/family?
+- What's the feature that would make competitors nervous?
+
+#### Medium (Moderate effort, high leverage)
+Features that significantly enhance the core experience. Force multipliers on what already works.
+
+Ask:
+- What would make the core action 10x faster/easier?
+- What data do we have that we're not using?
+- What workflow is painful that we could automate?
+- What would turn casual users into power users?
+
+#### Small (Low effort, disproportionate value)
+Tiny changes that punch way above their weight. Often overlooked because they seem "too simple."
+
+Ask:
+- What single button/shortcut would save users minutes daily?
+- What information is users hunting for that we could surface?
+- What anxiety do users have that we could eliminate with one indicator?
+- What's the thing users do manually that we could remember/automate?
+
+### Step 3: Evaluate Ruthlessly
+
+For each idea, assess:
+
+| 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? |
+
+Use a simple 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
+
+### Step 4: Identify the Highest-Leverage Moves
+
+Look for:
+
+**Quick wins with outsized impact**
+- Small effort, big value
+- Often overlooked because they're "obvious"
+- Can ship fast, validate fast
+
+**Strategic bets**
+- Larger effort, potentially transformative
+- Opens new possibilities
+- Worth the investment if it works
+
+**Compounding features**
+- Get more valuable over time
+- Network effects, data effects, habit formation
+- Build moats
+
+### Step 5: Prioritize
+
+Don't just list ideas—stack rank them:
+
+```
+## Recommended Priority
+
+### Do Now (Quick wins)
+1. [Feature] — Why: [reason], Impact: [what changes]
+
+### Do Next (High leverage)
+1. [Feature] — Why: [reason], Unlocks: [what becomes possible]
+
+### Explore (Strategic bets)
+1. [Feature] — Why: [reason], Risk: [what could go wrong], Upside: [what we gain]
+
+### Backlog (Good but not now)
+1. [Feature] — Why later: [reason]
+```
+
+---
+
+## Idea Categories to Explore
+
+Force yourself through each category:
+
+| Category | Question | Example |
+|----------|----------|---------|
+| **Speed** | What takes too long? | Instant search, predictive loading |
+| **Automation** | What's repetitive? | Auto-scheduling, smart defaults |
+| **Intelligence** | What could be smarter? | Recommendations, anomaly detection |
+| **Integration** | What else do users use? | Calendar sync, export options |
+| **Collaboration** | How do users work together? | Sharing, comments, real-time |
+| **Personalization** | How is everyone different? | Custom views, preferences |
+| **Visibility** | What's hidden that shouldn't be? | Dashboards, progress tracking |
+| **Confidence** | What creates anxiety? | Confirmations, undo, previews |
+| **Delight** | What could spark joy? | Animations, celebrations, polish |
+| **Access** | Who can't use this yet? | Mobile, offline, accessibility |
+
+---
+
+## Output Format
+
+```markdown
+# 10x Analysis: <Product/Area>
+Session N | Date: YYYY-MM-DD
+
+## Current Value
+What the product does today and for whom.
+
+## The Question
+What would make this 10x more valuable?
+
+---
+
+## Massive Opportunities
+
+### 1. [Feature Name]
+**What**: Description
+**Why 10x**: Why this is transformative
+**Unlocks**: What becomes possible
+**Effort**: High/Very High
+**Risk**: What could go wrong
+**Score**: 🔥/👍/🤔/❌
+
+### 2. ...
+
+---
+
+## Medium Opportunities
+
+### 1. [Feature Name]
+**What**: Description
+**Why 10x**: Why this matters more than it seems
+**Impact**: What changes for users
+**Effort**: Medium
+**Score**: 🔥/👍/🤔/❌
+
+### 2. ...
+
+---
+
+## Small Gems
+
+### 1. [Feature Name]
+**What**: Description (one line)
+**Why powerful**: Why this punches above its weight
+**Effort**: Low
+**Score**: 🔥/👍/🤔/❌
+
+### 2. ...
+
+---
+
+## Recommended Priority
+
+### Do Now
+1. ...
+
+### Do Next
+1. ...
+
+### Explore
+1. ...
+
+---
+
+## Questions
+
+### Answered
+- **Q**: ... **A**: ...
+
+### Blockers
+- **Q**: ... (need user input)
+
+## Next Steps
+- [ ] Validate assumption: ...
+- [ ] Research: ...
+- [ ] Decide: ...
+```
+
+---
+
+## Rules
+
+- **THINK BIG FIRST**—don't self-censor with "that's too hard." Capture the idea, evaluate later.
+- **SMALL CAN BE HUGE**—don't dismiss simple ideas. Sometimes one button changes everything.
+- **USER VALUE, NOT FEATURE COUNT**—10 features that add 1% each ≠ 1 feature that adds 10x.
+- **BE SPECIFIC**—"better UX" is not an idea. "One-click rescheduling from notification" is.
+- **QUESTION ASSUMPTIONS**—"users want X" may be wrong. What do they actually need?
+- **COMPOUND THINKING**—prefer features that get better over time.
+- **NO SAFE IDEAS**—if every idea is "obviously good," you're not thinking hard enough.
+- **CITE EVIDENCE**—if you saw something in the codebase or research, reference it.
+
+---
+
+## Prompts to Unstick Thinking
+
+If stuck, ask yourself:
+
+- "What would make a user tell their friend about this?"
+- "What's the thing users do every day that's slightly annoying?"
+- "What would we build if we had 10x the engineering team? 1/10th?"
+- "What would a competitor need to build to beat us?"
+- "What do power users do manually that we could make native?"
+- "What's the insight we have from data that users don't see?"
+- "What would make this addictive (in a good way)?"
+- "What's the feature that sounds crazy but might work?"

package/bundles/antigravity-plugin-extras/skills/github-issues/SKILL.md

@@ -0,0 +1,359 @@
+---
+name: github-issues
+context: fork
+description: Create well-structured GitHub issues with proper labels, descriptions, and acceptance criteria. Use when creating bug reports, feature requests, or tracking tasks.
+---
+
+# GitHub Issues Skill
+
+Create clear, actionable GitHub issues that provide all necessary context.
+
+## Trigger
+
+Activate when:
+- User asks to create an issue
+- User reports a bug that needs tracking
+- User wants to propose a feature
+- User says "open an issue for..."
+
+---
+
+## Issue Types
+
+Additional issue and PR body templates: `references/templates.md`.
+
+### 🐛 Bug Report
+
+For unexpected behavior or errors.
+
+```markdown
+## Bug Report
+
+### Description
+[Clear description of the bug]
+
+### Steps to Reproduce
+1. [First Step]
+2. [Second Step]
+3. [See error]
+
+### Expected Behavior
+[What should happen]
+
+### Actual Behavior
+[What actually happens]
+
+### Environment
+- OS: [Windows 11]
+- Python: [3.11.x]
+- Browser: [Chrome 120]
+
+### Screenshots/Logs
+[If applicable]
+
+### Additional Context
+[Any other relevant information]
+```
+
+### ✨ Feature Request
+
+For new functionality.
+
+```markdown
+## Feature Request
+
+### Problem Statement
+[Describe the problem this feature would solve]
+
+### Proposed Solution
+[Describe your proposed solution]
+
+### Alternatives Considered
+[Other approaches you considered]
+
+### Acceptance Criteria
+- [ ] [Criterion 1]
+- [ ] [Criterion 2]
+
+### Additional Context
+[Mockups, examples, or additional information]
+```
+
+### 📋 Task
+
+For general work items.
+
+```markdown
+## Task
+
+### Description
+[Clear description of the task]
+
+### Acceptance Criteria
+- [ ] [Criterion 1]
+- [ ] [Criterion 2]
+
+### Technical Notes
+[Implementation guidance or constraints]
+
+### Dependencies
+[Related issues or prerequisites]
+```
+
+---
+
+## Phase 1: Gather Information
+
+### Questions to Ask
+
+**For Bugs:**
+1. What were you trying to do?
+2. What did you expect to happen?
+3. What actually happened?
+4. Can you reproduce it consistently?
+5. What environment are you using?
+
+**For Features:**
+1. What problem are you trying to solve?
+2. Who will benefit from this?
+3. What would success look like?
+4. Are there any constraints or requirements?
+
+**For Tasks:**
+1. What needs to be done?
+2. Why is this needed?
+3. What are the acceptance criteria?
+4. Are there dependencies?
+
+---
+
+## Phase 2: Structure the Issue
+
+### Title Guidelines
+
+```markdown
+# Format: [Type] Brief descriptive title
+
+# ✅ Good
+[Bug] Dashboard fails to load with special characters in filter
+[Feature] Add export to CSV for complaints report
+[Task] Migrate database connection to use connection pooling
+
+# ❌ Bad
+Bug in dashboard          # Too vague
+It doesn't work           # Not descriptive
+Feature request please    # No description
+```
+
+### Body Structure
+
+1. **Context first**: Why does this matter?
+2. **Details**: What specifically needs to happen?
+3. **Acceptance criteria**: How do we know it's done?
+4. **Additional info**: Screenshots, logs, examples
+
+### Labels to Suggest
+
+| Label | Use When |
+|-------|----------|
+| `bug` | Something isn't working |
+| `enhancement` | New feature or request |
+| `documentation` | Docs need updating |
+| `good first issue` | Good for new contributors |
+| `help wanted` | Extra attention needed |
+| `question` | Further information requested |
+| `wontfix` | Will not be addressed |
+| `duplicate` | Already exists |
+| `priority:high` | Urgent issue |
+| `priority:low` | Nice to have |
+| `area:frontend` | Frontend/UI issues |
+| `area:backend` | Backend/API issues |
+| `area:database` | Database issues |
+
+---
+
+## Phase 3: Generate Issue
+
+### Template Output
+
+```markdown
+## Generated Issue
+
+### Title
+[Type] [Descriptive title]
+
+### Body
+[Formatted issue body using appropriate template]
+
+### Suggested Labels
+- [label1]
+- [label2]
+
+### Suggested Assignee
+[If applicable]
+```
+
+---
+
+## Examples
+
+### Bug Example
+
+**User says**: "The complaints dashboard crashes when I select a date range more than 30 days"
+
+```markdown
+### Title
+[Bug] Dashboard crashes when selecting date range over 30 days
+
+### Body
+
+## Bug Report
+
+### Description
+The complaints dashboard crashes with an error when selecting a date range 
+greater than 30 days in the filter.
+
+### Steps to Reproduce
+1. Navigate to Complaints Dashboard
+2. Click on date range filter
+3. Select start date more than 30 days ago
+4. Select end date as today
+5. Error appears and dashboard fails to load
+
+### Expected Behavior
+Dashboard should load complaints for the selected date range, 
+potentially with pagination for large result sets.
+
+### Actual Behavior
+Application crashes with "Memory Error" or becomes unresponsive.
+
+### Environment
+- OS: Windows 11
+- Python: 3.11.4
+- Streamlit: 1.28.0
+
+### Possible Cause
+The query may be fetching too much data without pagination, 
+causing memory issues.
+
+### Suggested Labels
+- bug
+- priority:high
+- area:frontend
+```
+
+### Feature Example
+
+**User says**: "We need to be able to export complaint reports to Excel"
+
+```markdown
+### Title
+[Feature] Export complaints report to Excel
+
+### Body
+
+## Feature Request
+
+### Problem Statement
+Analysts need to share complaint data with stakeholders who don't 
+have access to the dashboard. Currently there's no way to export 
+the data.
+
+### Proposed Solution
+Add an "Export to Excel" button on the complaints report page that:
+- Exports currently filtered data
+- Includes all visible columns
+- Formats dates in DD/MM/YYYY format
+- Names file with date: `complaints_export_2024-01-15.xlsx`
+
+### Acceptance Criteria
+- [ ] Export button visible on complaints report page
+- [ ] Export respects current filters
+- [ ] Excel file opens correctly in Microsoft Excel
+- [ ] Large exports (>10k rows) don't crash the app
+- [ ] File includes column headers
+
+### Technical Notes
+Consider using `openpyxl` or `xlsxwriter` for Excel generation.
+May need to implement streaming for large datasets.
+
+### Suggested Labels
+- enhancement
+- area:frontend
+```
+
+### Task Example
+
+**User says**: "We need to add logging to the API endpoints"
+
+```markdown
+### Title
+[Task] Add structured logging to API endpoints
+
+### Body
+
+## Task
+
+### Description
+Add consistent logging to all API endpoints using loguru for 
+better debugging and monitoring in production.
+
+### Acceptance Criteria
+- [ ] All endpoints log request received (INFO level)
+- [ ] All endpoints log response sent with status code
+- [ ] Errors logged with full stack trace (ERROR level)
+- [ ] Sensitive data (passwords, tokens) excluded from logs
+- [ ] Log format includes timestamp, request ID, user ID
+
+### Technical Notes
+- Use loguru for logging
+- Follow pattern in [python.instructions.md](../instructions/python.instructions.md)
+- Add request ID middleware for tracing
+
+### Dependencies
+- None
+
+### Suggested Labels
+- enhancement
+- area:backend
+```
+
+---
+
+## Updating Existing Issues
+
+When updating rather than creating:
+1. **Fetch current issue first** to preserve unchanged fields
+2. Only modify fields that need changing (title, body, state, labels, assignees)
+3. State values: `open`, `closed`
+4. Link related issues when known: `Related to #123`
+
+## Workflow Summary
+
+1. **Determine action**: Create, update, or query?
+2. **Gather context**: Get repo info, existing labels, milestones if needed
+3. **Structure content**: Use the appropriate template above
+4. **Execute**: Create or update the issue via CLI (`gh issue create`) or API
+5. **Confirm**: Report the issue URL to the user
+
+## Tips
+
+- Always confirm the repository context before creating issues
+- Ask for missing critical information rather than guessing
+- For updates, fetch current issue first to preserve unchanged fields
+- Keep titles under 72 characters
+- Use `gh` CLI for automation: `gh issue create --title "..." --body "..." --label bug`
+
+---
+
+## Checklist
+
+Before finalizing the issue:
+
+- [ ] Title is clear and descriptive
+- [ ] Body provides enough context
+- [ ] Steps to reproduce (for bugs) are complete
+- [ ] Acceptance criteria are measurable
+- [ ] Appropriate labels suggested
+- [ ] No sensitive information included
+- [ ] Related issues linked where applicable

package/bundles/antigravity-plugin-extras/skills/github-issues/references/templates.md

@@ -0,0 +1,90 @@
+# Issue Templates
+
+Copy and customize these templates for issue bodies.
+
+## Bug Report Template
+
+```markdown
+## Description
+[Clear description of the bug]
+
+## Steps to Reproduce
+1. [First step]
+2. [Second step]
+3. [And so on...]
+
+## Expected Behavior
+[What should happen]
+
+## Actual Behavior
+[What actually happens]
+
+## Environment
+- Browser: [e.g., Chrome 120]
+- OS: [e.g., macOS 14.0]
+- Version: [e.g., v1.2.3]
+
+## Screenshots/Logs
+[If applicable]
+
+## Additional Context
+[Any other relevant information]
+```
+
+## Feature Request Template
+
+```markdown
+## Summary
+[One-line description of the feature]
+
+## Motivation
+[Why is this feature needed? What problem does it solve?]
+
+## Proposed Solution
+[How should this feature work?]
+
+## Acceptance Criteria
+- [ ] [Criterion 1]
+- [ ] [Criterion 2]
+- [ ] [Criterion 3]
+
+## Alternatives Considered
+[Other approaches considered and why they weren't chosen]
+
+## Additional Context
+[Mockups, examples, or related issues]
+```
+
+## Task Template
+
+```markdown
+## Objective
+[What needs to be accomplished]
+
+## Details
+[Detailed description of the work]
+
+## Checklist
+- [ ] [Subtask 1]
+- [ ] [Subtask 2]
+- [ ] [Subtask 3]
+
+## Dependencies
+[Any blockers or related work]
+
+## Notes
+[Additional context or considerations]
+```
+
+## Minimal Template
+
+For simple issues:
+
+```markdown
+## Description
+[What and why]
+
+## Tasks
+- [ ] [Task 1]
+- [ ] [Task 2]
+```