clikit-plugin 0.2.44 → 0.2.46

package/skill/supabase-postgres-best-practices/SKILL.md

@@ -1,168 +0,0 @@
----
-name: supabase-postgres-best-practices
-description: Use when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations from Supabase.
----
-
-# Supabase Postgres Best Practices Skill
-
-You are running the **supabase-postgres-best-practices** skill. Postgres optimization from Supabase.
-
-## Core Principles
-
-Production-hardened patterns from Supabase's managed Postgres experience.
-
-## Query Optimization
-
-### 1. Index Strategy
-```sql
--- Index for common query patterns
-CREATE INDEX idx_users_email ON users(email);
-CREATE INDEX idx_posts_user_created ON posts(user_id, created_at DESC);
-
--- Partial index for filtered queries
-CREATE INDEX idx_active_users ON users(email) WHERE active = true;
-
--- GIN for JSONB and arrays
-CREATE INDEX idx_metadata ON items USING GIN(metadata);
-```
-
-### 2. Query Patterns
-```sql
--- Good: Sargable query
-SELECT * FROM users WHERE email = 'user@example.com';
-
--- Avoid: Function on column prevents index usage
-SELECT * FROM users WHERE LOWER(email) = 'user@example.com';
-
--- Fix: Use functional index or normalize data
-CREATE INDEX idx_users_email_lower ON users(LOWER(email));
-```
-
-### 3. EXPLAIN ANALYZE
-```sql
--- Always analyze slow queries
-EXPLAIN ANALYZE SELECT * FROM posts WHERE user_id = 123;
-
--- Look for:
--- - Seq Scan (should be Index Scan)
--- - High cost values
--- - Large row estimates vs actual
-```
-
-## Schema Design
-
-### 1. Appropriate Types
-```sql
--- Use appropriate types
-CREATE TABLE events (
-  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
-  created_at TIMESTAMPTZ DEFAULT NOW(), -- Not TIMESTAMP
-  status TEXT,                          -- Not VARCHAR(n)
-  metadata JSONB DEFAULT '{}'           -- Not JSON
-);
-```
-
-### 2. Foreign Keys
-```sql
--- Always index foreign keys
-CREATE TABLE posts (
-  id UUID PRIMARY KEY,
-  user_id UUID REFERENCES users(id)
-);
-CREATE INDEX idx_posts_user_id ON posts(user_id);
-```
-
-### 3. Partitioning
-```sql
--- Partition large tables by time
-CREATE TABLE events (
-  id UUID,
-  created_at TIMESTAMPTZ
-) PARTITION BY RANGE (created_at);
-
-CREATE TABLE events_2024_01 PARTITION OF events
-  FOR VALUES FROM ('2024-01-01') TO ('2024-02-01');
-```
-
-## Connection Management
-
-### 1. Connection Pooling
-```javascript
-// Use Supavisor or PgBouncer
-// Transaction mode for serverless
-const pool = new Pool({
-  connectionString: process.env.DATABASE_URL,
-  max: 10,                    // Limit connections
-  idleTimeoutMillis: 30000,
-  connectionTimeoutMillis: 2000
-});
-```
-
-### 2. Prepared Statements
-```sql
--- Use prepared statements for repeated queries
-PREPARE get_user(UUID) AS
-  SELECT * FROM users WHERE id = $1;
-
-EXECUTE get_user('uuid-here');
-```
-
-## Performance Checklist
-
-| Check | Why |
-|-------|-----|
-| Index foreign keys | Join performance |
-| Use TIMESTAMPTZ | Timezone handling |
-| Use JSONB not JSON | Binary format, indexing |
-| Analyze slow queries | EXPLAIN ANALYZE |
-| Limit connections | Prevent exhaustion |
-
-## Common Anti-Patterns
-
-| Anti-Pattern | Fix |
-|--------------|-----|
-| SELECT * | Select only needed columns |
-| N+1 queries | Use JOINs or batch fetch |
-| Missing indexes | Add appropriate indexes |
-| VARCHAR(n) | Use TEXT with CHECK constraint |
-| TIMESTAMP | Use TIMESTAMPTZ |
-| Unindexed JSON queries | Use GIN index |
-
-## RLS (Row Level Security)
-
-```sql
--- Enable RLS
-ALTER TABLE posts ENABLE ROW LEVEL SECURITY;
-
--- Policy for user's own posts
-CREATE POLICY "Users can manage own posts"
-  ON posts FOR ALL
-  USING (auth.uid() = user_id)
-  WITH CHECK (auth.uid() = user_id);
-```
-
-## Monitoring Queries
-
-```sql
--- Find slow queries
-SELECT query, mean_exec_time, calls
-FROM pg_stat_statements
-ORDER BY mean_exec_time DESC
-LIMIT 10;
-
--- Check table bloat
-SELECT schemaname, tablename,
-       pg_size_pretty(pg_total_relation_size(schemaname||'.'||tablename)) as size
-FROM pg_tables
-ORDER BY pg_total_relation_size(schemaname||'.'||tablename) DESC;
-```
-
-## Quick Reference
-
-| Scenario | Solution |
-|----------|----------|
-| Slow reads | Add index, check EXPLAIN |
-| Slow writes | Reduce indexes, batch inserts |
-| Connection limits | Use pooling |
-| Large tables | Partition by time |
-| JSON queries | GIN index on JSONB |

package/skill/swarm-coordination/SKILL.md

@@ -1,54 +0,0 @@
----
-name: swarm-coordination
-description: Use for implementing plans with multiple independent tasks in parallel using Kimi K2.5 PARL patterns.
----
-
-# Swarm Coordination Skill
-
-You are running the **swarm-coordination** skill. Parallel multi-task execution.
-
-## PARL Pattern (Parallel Agent Runtime Loop)
-
-Kimi K2.5 patterns for coordinating multiple agents:
-
-| Phase | Action |
-|-------|--------|
-| Plan | Decompose into independent tasks |
-| Assign | Route tasks to available agents |
-| Run | Execute tasks in parallel |
-| Learn | Aggregate results, iterate |
-
-## Task Classification
-
-```
-Independent → Parallel execution
-Dependent   → Sequential with dependency tracking
-Blocked     → Wait for blocker completion
-```
-
-## Anti-Serial-Collapse Detection
-
-Warning signs of serial execution:
-- All tasks waiting on one agent
-- Sequential claims despite no dependencies
-- Long queue with no parallelism
-
-Mitigations:
-- Rebalance task assignments
-- Split blocking tasks
-- Add more agents to bottleneck role
-
-## Graceful Shutdown
-
-1. Complete in-progress tasks
-2. Checkpoint state to Beads
-3. Release all file reservations
-4. Sync to git
-5. Broadcast session end
-
-## Best Practices
-
-- Claim only ready (unblocked) tasks
-- Reserve files early, release promptly
-- Use `beads-village_broadcast` for coordination
-- Check `beads-village_discover` for active agents

package/skill/testing-skills-with-subagents/SKILL.md

@@ -1,102 +0,0 @@
----
-name: testing-skills-with-subagents
-description: TDD applied to process documentation. RED (baseline without skill) → GREEN (write skill) → REFACTOR (close loopholes).
----
-
-# Testing Skills with Subagents Skill
-
-You are running the **testing-skills-with-subagents** skill. Skills are code. Test them like code.
-
-## The Problem
-
-Skills are process documentation that guide agent behavior. Untested skills:
-- Have loopholes agents can exploit
-- Miss edge cases
-- Drift from original intent over edits
-
-## The Solution: TDD for Skills
-
-Apply RED-GREEN-REFACTOR to skill creation and validation.
-
-### Phase 1: RED — Establish Baseline
-
-Before writing the skill:
-
-1. **Define the desired behavior** — What should the agent do differently?
-2. **Run a subagent WITHOUT the skill** — Document what it does wrong
-3. **Capture the failure mode** — This is your "failing test"
-
-```
-Example for TDD skill:
-- Desired: Agent writes tests before code
-- Baseline run: Agent writes code first, then adds tests
-- Failure: "I'll implement the function, then write tests"
-```
-
-### Phase 2: GREEN — Write the Skill
-
-1. **Write the skill** — Target the specific failure mode
-2. **Run a subagent WITH the skill** — It should now behave correctly
-3. **Verify the fix** — Did it change behavior as intended?
-
-```
-Skill added: "No code without tests. Delete any code written before test."
-- With skill: Agent refuses to write code, asks for test first
-- Success: Behavior changed in expected direction
-```
-
-### Phase 3: REFACTOR — Close Loopholes
-
-1. **Try to bypass the skill** — Look for edge cases and exploits
-2. **Add constraints** — Tighten rules to prevent bypasses
-3. **Re-run with edge cases** — Verify loopholes are closed
-
-```
-Loophole: "What if I keep the code as 'reference' while writing test?"
-Fix: Add rule: "Write code before test? DELETE the code. Don't keep as reference."
-```
-
-## Workflow
-
-```
-1. Define → What behavior change do you want?
-2. RED → Run subagent without skill, capture failure
-3. GREEN → Write skill, run subagent with skill, verify fix
-4. REFACTOR → Find loopholes, close them, verify
-5. Document → Record test cases in skill or memory
-```
-
-## Test Cases for Skills
-
-Store validated test cases in `.opencode/memory/skill-tests/`:
-
-```markdown
-# tdd-skill-tests.md
-
-## Test 1: Code Before Test
-- Input: "Implement a user service"
-- Without skill: Writes UserService, then asks about tests
-- With skill: Refuses, asks for test first
-- Status: PASS
-
-## Test 2: Reference Code Loophole
-- Input: "Here's reference code for UserService, write tests"
-- Without explicit rule: Keeps reference, writes tests to match
-- With rule: Deletes reference, writes test from spec
-- Status: PASS
-```
-
-## Rules
-
-1. **Never trust a skill you haven't tested** — Run it against a subagent
-2. **Baseline first** — You can't know the skill works without comparison
-3. **Hunt for loopholes** — Actively try to break your own rules
-4. **Document test cases** — Future editors need to know what was validated
-
-## Red Flags
-
-- Skill added without testing against baseline
-- Rules with obvious exceptions
-- Vague language that agents can interpret loosely
-- No documented test cases
-- Skill that "feels right" but has no evidence

package/skill/ui-ux-research/SKILL.md

@@ -1,93 +0,0 @@
----
-name: ui-ux-research
-description: Use when analyzing UI mockups, conducting UX audits, or researching design patterns with multimodal analysis.
----
-
-# UI/UX Research Skill
-
-You are running the **ui-ux-research** skill. Multimodal design analysis with Gemini.
-
-## Capabilities
-
-| Analysis Type | Input | Output |
-|---------------|-------|--------|
-| Mockup Review | Screenshot/Image | Component breakdown, issues |
-| Design System Audit | Multiple screenshots | Consistency report |
-| Accessibility Check | UI screenshot | WCAG violations |
-| Competitive Analysis | Multiple designs | Comparison matrix |
-| User Flow Mapping | Screenshots | Flow diagram |
-
-## Process
-
-### 1. Prepare Visual Input
-
-```bash
-# Single screenshot
-gemini -p "Analyze this UI for usability issues: $(cat screenshot.png)"
-
-# Multiple screens
-gemini -p "Review this user flow: $(cat screen1.png screen2.png screen3.png)"
-
-# With context
-gemini -p "Audit this dashboard for a financial app: $(cat dashboard.png)"
-```
-
-### 2. Analysis Dimensions
-
-**Visual Hierarchy**
-- Eye flow direction
-- F-pattern or Z-pattern compliance
-- Contrast and emphasis
-- Whitespace usage
-
-**Interaction Patterns**
-- Button placement and affordance
-- Form field grouping
-- Navigation clarity
-- Feedback mechanisms
-
-**Accessibility**
-- Color contrast ratios
-- Touch target sizes
-- Screen reader compatibility
-- Keyboard navigation
-
-**Responsive Behavior**
-- Breakpoint handling
-- Content reflow
-- Touch vs mouse patterns
-- Portrait/landscape considerations
-
-### 3. Output Structure
-
-```
-## Summary
-[2-3 sentence overall assessment]
-
-## Strengths
-- [What works well]
-
-## Issues
-| Priority | Issue | Location | Fix |
-|----------|-------|----------|-----|
-| High | [issue] | [where] | [how] |
-
-## Recommendations
-[Specific, actionable suggestions]
-```
-
-## Checklist
-
-- [ ] Image quality is sufficient for analysis
-- [ ] Context provided (user type, device, goal)
-- [ ] Multiple angles if analyzing flow
-- [ ] Accessibility explicitly checked
-- [ ] Findings saved to `.opencode/memory/research/`
-
-## Red Flags
-
-- Analyzing without user context
-- Ignoring device constraints
-- Missing accessibility review
-- Not considering edge cases
-- Vague recommendations ("improve UX")

package/skill/v0/SKILL.md

@@ -1,67 +0,0 @@
----
-name: v0
-description: Use when generating UI components, building dashboards, creating design systems, or need AI-assisted design implementation.
----
-
-# V0 Skill
-
-AI-powered UI generation via Vercel's v0 platform MCP. Create React components, generate complete UIs, and get design assistance through natural language prompts.
-
-## Capabilities
-
-- **Component Generation**: Create React components from descriptions
-- **Chat Interface**: Interactive design conversations
-- **Design System Support**: Generate components matching existing design tokens
-- **Dashboard Creation**: Build data visualizations and admin panels
-- **Rapid Prototyping**: Quick iteration on UI concepts
-- **Code Export**: Production-ready React/Next.js code
-
-## When to Use
-
-- Building new UI components from scratch
-- Creating dashboards and admin interfaces
-- Exploring design alternatives
-- Converting mockups to code
-- Generating responsive layouts
-- Building form interfaces
-
-## Key Tools
-
-- `create_chat`: Start a new design conversation
-- `generate_component`: Create component from description
-- `iterate_design`: Refine existing designs
-- `export_code`: Get production-ready code
-
-## Example Usage
-
-```
-// Start design chat
-create_chat({ prompt: "Create a user profile card with avatar, stats, and edit button" })
-
-// Generate component
-generate_component({
-  description: "Data table with sorting, filtering, and pagination",
-  framework: "react",
-  styling: "tailwind"
-})
-
-// Iterate on design
-iterate_design({
-  chat_id: "abc123",
-  feedback: "Make the header sticky and add a search bar"
-})
-```
-
-## Output Format
-
-- React components with TypeScript
-- Tailwind CSS styling by default
-- Accessible by default (WCAG compliant)
-- Mobile-responsive designs
-
-## Notes
-
-- Requires v0 API access
-- Best for React/Next.js projects
-- Integrates with shadcn/ui components
-- Supports custom design tokens

package/skill/v1-run/SKILL.md

@@ -1,85 +0,0 @@
----
-name: v1-run
-description: Use when selecting npm packages, checking for vulnerabilities, comparing package alternatives, or evaluating package health scores.
----
-
-# V1-Run Skill
-
-npm package intelligence via MCP providing real-time version data, vulnerability information, health scores, and package comparisons for informed dependency decisions.
-
-## Capabilities
-
-- **Version Info**: Real-time package versions and changelogs
-- **Vulnerability Data**: Security advisories and CVE information
-- **Health Scores**: Package maintenance and popularity metrics
-- **Package Comparisons**: Side-by-side alternative analysis
-- **Dependency Analysis**: Transitive dependency inspection
-- **Download Stats**: npm download trends and patterns
-
-## When to Use
-
-- Selecting between npm package alternatives
-- Checking packages for known vulnerabilities
-- Evaluating package maintenance status
-- Comparing bundle sizes and dependencies
-- Researching package popularity and adoption
-- Making informed dependency decisions
-
-## Key Tools
-
-- `get_package`: Get package details and metadata
-- `check_vulnerabilities`: Security vulnerability scan
-- `get_health_score`: Package health metrics
-- `compare_packages`: Compare multiple packages
-- `get_dependencies`: Analyze dependency tree
-- `get_downloads`: Download statistics
-
-## Example Usage
-
-```
-// Get package info
-get_package({ name: "lodash" })
-
-// Check vulnerabilities
-check_vulnerabilities({ name: "express", version: "4.17.0" })
-// Returns: { vulnerabilities: 2, severity: "medium", cves: [...] }
-
-// Get health score
-get_health_score({ name: "react" })
-// Returns: { score: 95, maintenance: "active", popularity: "very-high" }
-
-// Compare alternatives
-compare_packages({
-  packages: ["axios", "ky", "got", "node-fetch"]
-})
-// Returns comparison table with scores, size, deps
-```
-
-## Health Score Components
-
-- **Maintenance**: Commit frequency, release cadence
-- **Popularity**: Downloads, stars, forks
-- **Quality**: Test coverage, documentation
-- **Security**: Vulnerability history, response time
-- **Community**: Contributors, issue responsiveness
-
-## Decision Support
-
-```
-Example comparison output:
-┌─────────────┬───────┬────────┬────────┬────────┐
-│ Package     │ Score │ Vulns  │ Size   │ Deps   │
-├─────────────┼───────┼────────┼────────┼────────┤
-│ axios       │ 92    │ 0      │ 13KB   │ 1      │
-│ ky          │ 88    │ 0      │ 4KB    │ 0      │
-│ got         │ 85    │ 1(low) │ 68KB   │ 12     │
-│ node-fetch  │ 78    │ 2(med) │ 24KB   │ 0      │
-└─────────────┴───────┴────────┴────────┴────────┘
-```
-
-## Notes
-
-- Real-time data from npm registry
-- Integrates Snyk/npm audit for vulnerabilities
-- Supports scoped packages (@org/package)
-- Includes ESM/CJS compatibility info

package/skill/visual-analysis/SKILL.md

@@ -1,113 +0,0 @@
----
-name: visual-analysis
-description: Use when analyzing images, screenshots, or UI mockups to extract colors, typography, layout, and design patterns.
----
-
-# Visual Analysis Skill
-
-You are running the **visual-analysis** skill. See everything. Extract what matters.
-
-## Analysis Types
-
-| Type | Purpose | Output |
-|------|---------|--------|
-| Color Extraction | Get palette from design | Hex codes with roles |
-| Typography Audit | Font identification | Font stack suggestions |
-| Layout Analysis | Grid and spacing | Spacing system |
-| Component Mapping | UI inventory | Component list |
-| Design Comparison | Compare multiple designs | Diff report |
-
-## Process
-
-### 1. Color Extraction
-
-```bash
-gemini -p "Extract all colors from this design with their approximate usage percentage: $(cat design.png)"
-```
-
-Output format:
-```
-Primary: #2563EB (45%)
-Secondary: #1E40AF (20%)
-Accent: #F59E0B (10%)
-Background: #FFFFFF (15%)
-Text: #1F2937 (10%)
-```
-
-### 2. Typography Analysis
-
-```bash
-gemini -p "Identify fonts and type scale in this design: $(cat design.png)"
-```
-
-Extract:
-- Font family (heading, body, mono)
-- Size scale (heading levels, body sizes)
-- Weight variations
-- Line height patterns
-
-### 3. Layout Analysis
-
-```bash
-gemini -p "Analyze the grid system and spacing in this layout: $(cat layout.png)"
-```
-
-Identify:
-- Column count
-- Gutter width
-- Margin/padding patterns
-- Component spacing rhythm
-
-### 4. Design Comparison
-
-```bash
-gemini -p "Compare these two designs and list all differences: $(cat design1.png design2.png)"
-```
-
-Report:
-- Structural differences
-- Color differences
-- Typography differences
-- Spacing differences
-- Missing/added elements
-
-## Checklist
-
-- [ ] Image quality verified
-- [ ] All colors extracted with context
-- [ ] Typography identified or approximated
-- [ ] Spacing system documented
-- [ ] Components inventoried
-- [ ] Analysis saved to `.opencode/memory/research/`
-
-## Output Template
-
-```markdown
-## Visual Analysis: [Design Name]
-
-### Colors
-| Role | Hex | Usage |
-|------|-----|-------|
-| Primary | #... | buttons, links |
-
-### Typography
-| Element | Font | Size | Weight |
-|---------|------|------|--------|
-| H1 | [font] | [size] | [weight] |
-
-### Layout
-- Columns: [N]
-- Gutter: [X]px
-- Base spacing: [X]px
-
-### Components
-- [Component list]
-```
-
-## Red Flags
-
-- Low resolution images (can't extract details)
-- Missing color context (what's primary vs accent)
-- Ignoring accessibility (contrast ratios)
-- Not saving analysis for future reference
-- Assuming fonts without verification