clikit-plugin 0.2.44 → 0.2.46

package/skill/gemini-large-context/SKILL.md

@@ -1,80 +0,0 @@
----
-name: gemini-large-context
-description: Use when context exceeds session limits or analyzing 100KB+ files. Leverages Gemini CLI's 1M token window.
----
-
-# Gemini Large Context Skill
-
-You are running the **gemini-large-context** skill. When you hit limits, scale up.
-
-## When to Use
-
-| Scenario | Why Gemini |
-|----------|------------|
-| Single file >100KB | Won't fit in standard context |
-| Project-wide pattern search | Need full codebase visibility |
-| Multi-file diff analysis | Compare across dozens of files |
-| Legacy code archaeology | Understand decade-old systems |
-| Full test suite review | See all tests at once |
-
-## Process
-
-### 1. Prepare Input
-
-```bash
-# Single large file
-gemini -p "Analyze this file for [task]: $(cat large_file.ts)"
-
-# Multiple files
-cat file1.ts file2.ts file3.ts | gemini -p "Compare these files:"
-
-# Full directory
-find src -name "*.ts" -exec cat {} \; | gemini -p "Find patterns in codebase:"
-```
-
-### 2. Structure Your Prompt
-
-```
-Context: [what you're analyzing]
-Task: [specific question or goal]
-Constraints: [limitations, requirements]
-Output: [expected format]
-```
-
-### 3. Handle Output
-
-- Gemini returns full analysis
-- Extract actionable items
-- If incomplete, prompt for continuation
-- Save important findings to memory
-
-## Use Cases
-
-### Large File Analysis
-```
-gemini -p "Map all exports and their dependencies in this file: $(cat huge_api.ts)"
-```
-
-### Pattern Detection
-```
-cat src/**/*.ts | gemini -p "Find all authentication patterns and security issues:"
-```
-
-### Multi-file Comparison
-```
-cat v1/api.ts v2/api.ts | gemini -p "Breaking changes between v1 and v2:"
-```
-
-## Checklist
-
-- [ ] Confirmed file/directory size justifies large context
-- [ ] Prompt includes specific task (not "analyze this")
-- [ ] Output format specified
-- [ ] Results saved to `.opencode/memory/` for reference
-
-## Red Flags
-
-- Using for small files (wastes resources)
-- Vague prompts ("what do you think?")
-- Not saving results (lose context on next session)
-- Ignoring token limits still exists (1M isn't infinite)

package/skill/mockup-to-code/SKILL.md

@@ -1,98 +0,0 @@
----
-name: mockup-to-code
-description: Use when converting UI mockups, screenshots, or Figma/Sketch designs into production-ready code.
----
-
-# Mockup to Code Skill
-
-You are running the **mockup-to-code** skill. Pixels to production.
-
-## Input Types
-
-| Source | Extraction Method |
-|--------|-------------------|
-| Screenshot | Visual analysis via Gemini |
-| Figma export | Design tokens + component mapping |
-| Sketch file | Layer structure + styles |
-| Design URL | Direct inspection or screenshot |
-
-## Process
-
-### 1. Extract Design Tokens
-
-```bash
-gemini -p "Extract design tokens from this mockup as JSON: $(cat mockup.png)"
-```
-
-Expected output structure:
-```json
-{
-  "colors": { "primary": "#...", "secondary": "#..." },
-  "typography": { "heading": "...", "body": "..." },
-  "spacing": { "base": 8, "scale": [8, 16, 24, 32] },
-  "shadows": ["0 2px 4px rgba(...)", ...],
-  "radii": [4, 8, 16]
-}
-```
-
-### 2. Identify Components
-
-```
-Component: [Name]
-- Props: [list]
-- Variants: [list]
-- States: [default, hover, active, disabled]
-- Dependencies: [child components]
-```
-
-### 3. Map to Tech Stack
-
-| Design Element | Implementation |
-|----------------|----------------|
-| Typography | Tailwind classes / CSS variables |
-| Colors | CSS custom properties |
-| Spacing | Tailwind spacing scale |
-| Components | React/Vue/Svelte components |
-| Icons | Lucide / Heroicons / custom SVG |
-
-### 4. Build Incrementally
-
-1. Structure: Semantic HTML
-2. Layout: Flexbox/Grid
-3. Styling: Tokens → classes
-4. Interaction: States and events
-5. Responsive: Breakpoint adjustments
-6. Polish: Animations and details
-
-## Component Library Handling
-
-### Existing Library
-- Check for matching components first
-- Extend or compose before creating new
-- Document any custom overrides
-
-### New Components
-- Follow existing patterns
-- Use established tokens
-- Ensure accessibility built-in
-
-## Checklist
-
-- [ ] Design tokens extracted and defined
-- [ ] Components identified and documented
-- [ ] Semantic HTML structure
-- [ ] Responsive breakpoints handled
-- [ ] All interactive states implemented
-- [ ] Accessibility attributes added
-- [ ] Matches mockup pixel-perfectly
-- [ ] Code follows project conventions
-
-## Red Flags
-
-- Skipping semantic HTML for div soup
-- Hardcoded values instead of tokens
-- Ignoring component library
-- Missing interactive states
-- No accessibility attributes
-- Inline styles over classes
-- Breaking responsive behavior

package/skill/mqdh/SKILL.md

@@ -1,54 +0,0 @@
----
-name: mqdh
-description: Use when building Meta Quest VR/AR applications, needing Meta Horizon OS documentation, or managing Quest devices via ADB.
----
-
-# Meta Quest Developer Hub (MQDH) Skill
-
-MCP integration for Meta Quest Developer Hub providing VR/AR development tools, documentation access, and device management capabilities.
-
-## Capabilities
-
-- **Documentation Access**: Query Meta Horizon OS and XR development docs
-- **ADB Tools**: Device debugging, app installation, log streaming
-- **Device Management**: Connect, configure, and manage Quest devices
-- **Build Tools**: APK management, app deployment workflows
-- **Debugging**: Performance profiling, log analysis
-- **Project Setup**: Quest project scaffolding and configuration
-
-## When to Use
-
-- Building applications for Meta Quest headsets
-- Looking up Meta XR SDK documentation
-- Debugging Quest applications on device
-- Managing Quest device settings and configurations
-- Deploying builds to Quest devices
-- Setting up XR development environments
-
-## Key Tools
-
-- `query_docs`: Search Meta Horizon OS documentation
-- `device_list`: List connected Quest devices
-- `device_install`: Install APK to device
-- `device_logs`: Stream device logs
-- `adb_command`: Execute ADB commands
-- `project_configure`: Set up Quest project settings
-
-## Example Usage
-
-```
-// Query documentation
-query_docs({ query: "hand tracking setup Quest 3" })
-
-// Install app
-device_install({ apk_path: "./build/app.apk", device_id: "quest-3" })
-
-// Stream logs
-device_logs({ device_id: "quest-3", filter: "Unity" })
-```
-
-## Prerequisites
-
-- Meta Quest Developer Hub installed
-- Developer mode enabled on Quest device
-- USB connection or ADB over Wi-Fi configured

package/skill/notebooklm/SKILL.md

@@ -1,71 +0,0 @@
----
-name: notebooklm
-description: Use when querying Google NotebookLM notebooks for source-grounded answers with citations, or managing notebook libraries.
----
-
-# NotebookLM Skill
-
-Query Google NotebookLM notebooks for source-grounded, citation-backed answers. Provides browser automation for notebook access, library management, and persistent authentication.
-
-## Capabilities
-
-- **Query Notebooks**: Ask questions against uploaded sources
-- **Citation-Backed Answers**: Responses reference specific source documents
-- **Notebook Management**: Create, update, delete notebooks
-- **Source Management**: Add/remove sources from notebooks
-- **Persistent Auth**: Maintain Google session across sessions
-- **Library Access**: Browse and search notebook collections
-
-## When to Use
-
-- Research with document-grounded answers
-- Querying knowledge bases with citations
-- Extracting insights from uploaded documents
-- Building research workflows
-- Creating Q&A systems from documents
-- Getting answers with verifiable sources
-
-## Key Tools
-
-- `query_notebook`: Ask questions to a specific notebook
-- `list_notebooks`: Get all available notebooks
-- `create_notebook`: Create new notebook with sources
-- `add_sources`: Add documents/URLs to notebook
-- `get_answer_sources`: Retrieve citations for an answer
-
-## Example Usage
-
-```
-// Query notebook
-query_notebook({
-  notebook_id: "research-papers",
-  question: "What are the key findings about LLM hallucinations?"
-})
-
-// Returns answer with citations:
-// "According to Source 1, LLM hallucinations occur when..."
-// Citations: [Source 1, p.3], [Source 2, Section 4.2]
-
-// List notebooks
-list_notebooks()
-
-// Create notebook
-create_notebook({
-  name: "Project Documentation",
-  sources: ["https://docs.example.com", "./local-docs/"]
-})
-```
-
-## Authentication
-
-- Browser-based OAuth flow
-- Session persistence in secure storage
-- Automatic token refresh
-- Supports multiple Google accounts
-
-## Notes
-
-- Requires Google account access
-- Browser automation handles auth
-- Source limits based on NotebookLM tiers
-- Answers grounded in uploaded sources only

package/skill/playwriter/SKILL.md

@@ -1,56 +0,0 @@
----
-name: playwriter
-description: Use when automating browser interactions, web scraping, or testing with existing Chrome sessions. 90% less context than traditional browser MCP.
----
-
-# Playwriter Skill
-
-Browser automation via Chrome extension integration. Provides a single `execute` tool with full Playwright API access while using your existing browser with all extensions, sessions, and cookies intact.
-
-## Capabilities
-
-- **Session Reuse**: Works with your logged-in browser sessions
-- **Extension Support**: Full access to Chrome extensions during automation
-- **Full Playwright API**: Navigation, clicks, inputs, screenshots, waits
-- **Cookie Persistence**: No need to re-authenticate
-- **Lightweight**: Minimal context usage compared to traditional browser MCPs
-
-## When to Use
-
-- Web scraping behind logins
-- Automating repetitive browser tasks
-- Testing web applications with existing sessions
-- Taking screenshots of authenticated pages
-- Form filling and submission
-- Multi-step browser workflows
-
-## Usage Pattern
-
-```
-Use the execute tool with Playwright-style commands:
-- navigate(url)
-- click(selector)
-- fill(selector, value)
-- screenshot()
-- wait(selector)
-- evaluate(script)
-```
-
-## Example
-
-```javascript
-execute({
-  actions: [
-    { type: "navigate", url: "https://example.com/dashboard" },
-    { type: "wait", selector: ".data-table" },
-    { type: "screenshot", path: "dashboard.png" }
-  ]
-})
-```
-
-## Notes
-
-- Requires Chrome extension installation
-- Browser must be running with remote debugging enabled
-- Supports headless and headed modes
-- Maintains state between execute calls

package/skill/polar/SKILL.md

@@ -1,39 +0,0 @@
----
-name: polar
-description: Use for Polar payment integration, subscriptions, license keys, and customer portal implementation.
----
-
-# Polar Skill
-
-You are running the **polar** skill. Polar payment platform integration.
-
-## Capabilities
-
-| Action | Description |
-|--------|-------------|
-| Create products | Define products, pricing, billing cycles |
-| Implement checkout | Embedded checkout, custom flows |
-| Manage subscriptions | Create, update, cancel, webhook handling |
-| License keys | Generate, validate, manage keys |
-| Customer portal | Self-service billing management |
-
-## Usage
-
-1. Configure Polar credentials in environment
-2. Create or reference products in Polar dashboard
-3. Implement checkout flow with webhooks
-4. Handle subscription state in your app
-
-## Key Integration Points
-
-- Checkout: `POST /checkout/`
-- Webhooks: subscription events, payment status
-- License validation: server-side key verification
-- Customer portal: embeddable billing UI
-
-## Best Practices
-
-- Always verify webhooks using signature validation
-- Store Polar IDs, not email addresses, for user linking
-- Handle all subscription states (active, past_due, canceled)
-- Test with Polar sandbox before production

package/skill/resend/SKILL.md

@@ -1,85 +0,0 @@
----
-name: resend
-description: Use when sending transactional emails, receiving inbound emails, creating email templates with React Email, or handling email webhooks.
----
-
-# Resend Skill
-
-Comprehensive Resend email platform integration for transactional emails, inbound email handling, template management with React Email, and webhook processing.
-
-## Capabilities
-
-- **Send Emails**: Transactional and bulk email sending
-- **Inbound Email**: Receive and process incoming emails
-- **React Email Templates**: Create emails with React components
-- **Webhook Handling**: Process email events (delivered, opened, bounced)
-- **Domain Management**: Configure sending domains and DNS
-- **Analytics**: Track email delivery and engagement metrics
-
-## When to Use
-
-- Sending transactional emails (password resets, notifications)
-- Building email templates with React
-- Receiving and processing inbound emails
-- Setting up email webhooks
-- Managing sending domains
-- Implementing email workflows
-
-## Key Tools
-
-- `send_email`: Send single or batch emails
-- `create_template`: Create React Email templates
-- `get_inbound`: Retrieve inbound emails
-- `list_domains`: Manage sending domains
-- `get_events`: Query email events
-- `create_webhook`: Set up event webhooks
-
-## Example Usage
-
-```
-// Send email
-send_email({
-  to: "user@example.com",
-  subject: "Welcome!",
-  html: "<h1>Welcome aboard!</h1>",
-  from: "noreply@myapp.com"
-})
-
-// React Email template
-create_template({
-  name: "password-reset",
-  component: "./emails/PasswordReset.tsx"
-})
-
-// Handle inbound
-get_inbound({
-  limit: 10,
-  status: "unread"
-})
-```
-
-## React Email Integration
-
-```tsx
-// emails/Welcome.tsx
-import { Html, Body, Container, Text } from '@react-email/components';
-
-export default function Welcome({ name }) {
-  return (
-    <Html>
-      <Body>
-        <Container>
-          <Text>Welcome, {name}!</Text>
-        </Container>
-      </Body>
-    </Html>
-  );
-}
-```
-
-## Notes
-
-- Requires Resend API key
-- Domain verification needed for sending
-- Supports attachments up to 40MB
-- Rate limits apply based on plan

package/skill/sharing-skills/SKILL.md

@@ -1,50 +0,0 @@
----
-name: sharing-skills
-description: Use when contributing skills to the community. One skill per PR.
----
-
-# Sharing Skills Skill
-
-You are running the **sharing-skills** skill. Contribute effectively.
-
-## When to Share
-
-- Broadly useful across projects
-- Solves common workflow problems
-- Encapsulates best practices
-- Not project-specific
-
-## Keep Personal
-
-- Project-specific configurations
-- Team-specific conventions
-- Environment-dependent logic
-- One-off automations
-
-## Contribution Workflow
-
-1. **Branch** — Create feature branch from main
-2. **Edit/Create** — Add or modify skill file
-3. **Commit** — Clear commit message describing skill
-4. **Push** — Push to your fork
-5. **PR** — Open pull request with description
-
-## PR Guidelines
-
-- One skill per PR
-- Include rationale in PR description
-- Reference any related issues
-- Be responsive to feedback
-
-## Skill File Structure
-
-```
-skill-name/
-  SKILL.md
-```
-
-## Red Flags
-
-- Sharing project-specific skills as general
-- Bundling multiple skills in one PR
-- Not documenting when/why to use the skill

package/skill/subagent-driven-development/SKILL.md

@@ -1,69 +0,0 @@
----
-name: subagent-driven-development
-description: Use when working on multi-task development cycles. Fresh subagent per task for fast iteration with code review between tasks via @review.
----
-
-# Subagent-Driven Development Skill
-
-You are running the **subagent-driven-development** skill. Work autonomously for hours with quality gates between tasks.
-
-## Core Principle
-
-Fresh subagent per task. Each task is a clean slate with clear objectives. Code review between tasks via @review agent ensures quality accumulation.
-
-## Workflow
-
-### 1. Task Breakdown
-- Split work into discrete, completable tasks
-- Each task should be 15-30 minutes of work
-- Tasks should have clear success criteria
-- Order tasks by dependency
-
-### 2. Task Execution Cycle
-```
-For each task:
-  1. Spawn fresh subagent for task
-  2. Subagent completes task autonomously
-  3. Run @review for code quality check
-  4. Fix issues from review
-  5. Commit or stage changes
-  6. Move to next task
-```
-
-### 3. Quality Gates
-Between each task:
-- Run @review agent on changed files
-- Address all critical and high-priority issues
-- Verify tests pass
-- Confirm task completion criteria met
-
-## Agent Autonomy
-
-The subagent works autonomously:
-- No mid-task questions to user
-- Make reasonable assumptions
-- Document decisions in code
-- Flag blockers only when truly stuck
-
-## Benefits
-
-| Benefit | Why |
-|---------|-----|
-| Fresh context | No accumulated confusion |
-| Fast iteration | Quick task completion |
-| Quality accumulation | Review catches issues early |
-| Autonomous work | Hours of productive work |
-
-## Anti-Patterns
-
-- Tasks too large (lose the benefit of fresh context)
-- Skipping review between tasks
-- Asking user for every decision
-- No clear success criteria per task
-
-## When to Use
-
-- Multi-hour development sessions
-- Features with multiple components
-- Refactoring with clear steps
-- Bug fix chains with review gates

package/skill/supabase/SKILL.md

@@ -1,80 +0,0 @@
----
-name: supabase
-description: Use when working with Supabase databases, edge functions, authentication, real-time subscriptions, or managing Supabase projects.
----
-
-# Supabase Skill
-
-Comprehensive Supabase platform MCP covering database operations, edge functions, authentication, real-time features, development tools, debugging, and project management.
-
-## Capabilities
-
-- **Database Operations**: Query, migrate, manage PostgreSQL
-- **Edge Functions**: Deploy, manage, debug serverless functions
-- **Authentication**: User management, auth providers, JWT handling
-- **Real-time**: Subscribe to database changes
-- **Storage**: File upload, management, signed URLs
-- **Development Tools**: Local development, type generation
-- **Debugging**: Logs, metrics, query analysis
-
-## When to Use
-
-- Querying or modifying Supabase databases
-- Deploying and managing edge functions
-- Setting up authentication flows
-- Generating TypeScript types from schema
-- Debugging database queries and functions
-- Managing Supabase projects
-
-## Key Tools
-
-- `query`: Execute SQL queries
-- `migrate`: Run database migrations
-- `deploy_function`: Deploy edge function
-- `generate_types`: Generate TypeScript types
-- `list_logs`: View function/database logs
-- `manage_auth`: User operations
-
-## Example Usage
-
-```
-// Query database
-query({
-  sql: "SELECT * FROM users WHERE active = true LIMIT 10"
-})
-
-// Deploy edge function
-deploy_function({
-  name: "send-notification",
-  entrypoint: "./functions/send-notification/index.ts"
-})
-
-// Generate types
-generate_types({
-  output: "./src/types/supabase.ts"
-})
-
-// Auth operations
-manage_auth({
-  action: "create_user",
-  email: "user@example.com",
-  password: "secure123"
-})
-```
-
-## Development Workflow
-
-```bash
-# Local development
-supabase start          # Start local stack
-supabase db reset       # Reset with migrations
-supabase functions serve # Local function dev
-supabase types gen      # Generate types
-```
-
-## Notes
-
-- Requires Supabase project credentials
-- Supports both local and remote projects
-- Row Level Security policies respected
-- Connection pooling for serverless