imhcode 1.0.0

package/skills/using-git-worktrees/SKILL.md

@@ -0,0 +1,215 @@
+---
+name: using-git-worktrees
+description: Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
+---
+
+# Using Git Worktrees
+
+## Overview
+
+Ensure work happens in an isolated workspace. Prefer your platform's native worktree tools. Fall back to manual git worktrees only when no native tool is available.
+
+**Core principle:** Detect existing isolation first. Then use native tools. Then fall back to git. Never fight the harness.
+
+**Announce at start:** "I'm using the using-git-worktrees skill to set up an isolated workspace."
+
+## Step 0: Detect Existing Isolation
+
+**Before creating anything, check if you are already in an isolated workspace.**
+
+```bash
+GIT_DIR=$(cd "$(git rev-parse --git-dir)" 2>/dev/null && pwd -P)
+GIT_COMMON=$(cd "$(git rev-parse --git-common-dir)" 2>/dev/null && pwd -P)
+BRANCH=$(git branch --show-current)
+```
+
+**Submodule guard:** `GIT_DIR != GIT_COMMON` is also true inside git submodules. Before concluding "already in a worktree," verify you are not in a submodule:
+
+```bash
+# If this returns a path, you're in a submodule, not a worktree — treat as normal repo
+git rev-parse --show-superproject-working-tree 2>/dev/null
+```
+
+**If `GIT_DIR != GIT_COMMON` (and not a submodule):** You are already in a linked worktree. Skip to Step 3 (Project Setup). Do NOT create another worktree.
+
+Report with branch state:
+- On a branch: "Already in isolated workspace at `<path>` on branch `<name>`."
+- Detached HEAD: "Already in isolated workspace at `<path>` (detached HEAD, externally managed). Branch creation needed at finish time."
+
+**If `GIT_DIR == GIT_COMMON` (or in a submodule):** You are in a normal repo checkout.
+
+Has the user already indicated their worktree preference in your instructions? If not, ask for consent before creating a worktree:
+
+> "Would you like me to set up an isolated worktree? It protects your current branch from changes."
+
+Honor any existing declared preference without asking. If the user declines consent, work in place and skip to Step 3.
+
+## Step 1: Create Isolated Workspace
+
+**You have two mechanisms. Try them in this order.**
+
+### 1a. Native Worktree Tools (preferred)
+
+The user has asked for an isolated workspace (Step 0 consent). Do you already have a way to create a worktree? It might be a tool with a name like `EnterWorktree`, `WorktreeCreate`, a `/worktree` command, or a `--worktree` flag. If you do, use it and skip to Step 3.
+
+Native tools handle directory placement, branch creation, and cleanup automatically. Using `git worktree add` when you have a native tool creates phantom state your harness can't see or manage.
+
+Only proceed to Step 1b if you have no native worktree tool available.
+
+### 1b. Git Worktree Fallback
+
+**Only use this if Step 1a does not apply** — you have no native worktree tool available. Create a worktree manually using git.
+
+#### Directory Selection
+
+Follow this priority order. Explicit user preference always beats observed filesystem state.
+
+1. **Check your instructions for a declared worktree directory preference.** If the user has already specified one, use it without asking.
+
+2. **Check for an existing project-local worktree directory:**
+   ```bash
+   ls -d .worktrees 2>/dev/null     # Preferred (hidden)
+   ls -d worktrees 2>/dev/null      # Alternative
+   ```
+   If found, use it. If both exist, `.worktrees` wins.
+
+3. **Check for an existing global directory:**
+   ```bash
+   project=$(basename "$(git rev-parse --show-toplevel)")
+   ls -d ~/.config/superpowers/worktrees/$project 2>/dev/null
+   ```
+   If found, use it (backward compatibility with legacy global path).
+
+4. **If there is no other guidance available**, default to `.worktrees/` at the project root.
+
+#### Safety Verification (project-local directories only)
+
+**MUST verify directory is ignored before creating worktree:**
+
+```bash
+git check-ignore -q .worktrees 2>/dev/null || git check-ignore -q worktrees 2>/dev/null
+```
+
+**If NOT ignored:** Add to .gitignore, commit the change, then proceed.
+
+**Why critical:** Prevents accidentally committing worktree contents to repository.
+
+Global directories (`~/.config/superpowers/worktrees/`) need no verification.
+
+#### Create the Worktree
+
+```bash
+project=$(basename "$(git rev-parse --show-toplevel)")
+
+# Determine path based on chosen location
+# For project-local: path="$LOCATION/$BRANCH_NAME"
+# For global: path="~/.config/superpowers/worktrees/$project/$BRANCH_NAME"
+
+git worktree add "$path" -b "$BRANCH_NAME"
+cd "$path"
+```
+
+**Sandbox fallback:** If `git worktree add` fails with a permission error (sandbox denial), tell the user the sandbox blocked worktree creation and you're working in the current directory instead. Then run setup and baseline tests in place.
+
+## Step 3: Project Setup
+
+Auto-detect and run appropriate setup:
+
+```bash
+# Node.js
+if [ -f package.json ]; then npm install; fi
+
+# Rust
+if [ -f Cargo.toml ]; then cargo build; fi
+
+# Python
+if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
+if [ -f pyproject.toml ]; then poetry install; fi
+
+# Go
+if [ -f go.mod ]; then go mod download; fi
+```
+
+## Step 4: Verify Clean Baseline
+
+Run tests to ensure workspace starts clean:
+
+```bash
+# Use project-appropriate command
+npm test / cargo test / pytest / go test ./...
+```
+
+**If tests fail:** Report failures, ask whether to proceed or investigate.
+
+**If tests pass:** Report ready.
+
+### Report
+
+```
+Worktree ready at <full-path>
+Tests passing (<N> tests, 0 failures)
+Ready to implement <feature-name>
+```
+
+## Quick Reference
+
+| Situation | Action |
+|-----------|--------|
+| Already in linked worktree | Skip creation (Step 0) |
+| In a submodule | Treat as normal repo (Step 0 guard) |
+| Native worktree tool available | Use it (Step 1a) |
+| No native tool | Git worktree fallback (Step 1b) |
+| `.worktrees/` exists | Use it (verify ignored) |
+| `worktrees/` exists | Use it (verify ignored) |
+| Both exist | Use `.worktrees/` |
+| Neither exists | Check instruction file, then default `.worktrees/` |
+| Global path exists | Use it (backward compat) |
+| Directory not ignored | Add to .gitignore + commit |
+| Permission error on create | Sandbox fallback, work in place |
+| Tests fail during baseline | Report failures + ask |
+| No package.json/Cargo.toml | Skip dependency install |
+
+## Common Mistakes
+
+### Fighting the harness
+
+- **Problem:** Using `git worktree add` when the platform already provides isolation
+- **Fix:** Step 0 detects existing isolation. Step 1a defers to native tools.
+
+### Skipping detection
+
+- **Problem:** Creating a nested worktree inside an existing one
+- **Fix:** Always run Step 0 before creating anything
+
+### Skipping ignore verification
+
+- **Problem:** Worktree contents get tracked, pollute git status
+- **Fix:** Always use `git check-ignore` before creating project-local worktree
+
+### Assuming directory location
+
+- **Problem:** Creates inconsistency, violates project conventions
+- **Fix:** Follow priority: existing > global legacy > instruction file > default
+
+### Proceeding with failing tests
+
+- **Problem:** Can't distinguish new bugs from pre-existing issues
+- **Fix:** Report failures, get explicit permission to proceed
+
+## Red Flags
+
+**Never:**
+- Create a worktree when Step 0 detects existing isolation
+- Use `git worktree add` when you have a native worktree tool (e.g., `EnterWorktree`). This is the #1 mistake — if you have it, use it.
+- Skip Step 1a by jumping straight to Step 1b's git commands
+- Create worktree without verifying it's ignored (project-local)
+- Skip baseline test verification
+- Proceed with failing tests without asking
+
+**Always:**
+- Run Step 0 detection first
+- Prefer native tools over git fallback
+- Follow directory priority: existing > global legacy > instruction file > default
+- Verify directory is ignored for project-local
+- Auto-detect and run project setup
+- Verify clean test baseline

package/skills/vercel/SKILL.md

@@ -0,0 +1,161 @@
+---
+name: vercel-ui-skills
+description: Vercel's UI design system. Use when building interfaces inspired by Vercel's aesthetic - light mode, Inter font, 4px grid.
+license: MIT
+metadata:
+  author: design-skills
+  version: "1.0.0"
+  source: https://vercel.com
+---
+
+# Vercel UI Skills
+
+Opinionated constraints for building Vercel-style interfaces with AI agents.
+
+## When to Apply
+
+Reference these guidelines when:
+- Building light-mode interfaces
+- Creating Vercel-inspired design systems
+- Implementing UIs with Inter font and 4px grid
+
+## Colors
+
+- SHOULD use light backgrounds for primary surfaces
+- MUST use `#F9F9F9` as page background (`surface-base`)
+- MUST use `#000001` for primary actions and focus states (`accent`)
+- SHOULD reduce color palette (currently 12 colors detected)
+- MUST maintain text contrast ratio of at least 4.5:1 for accessibility
+
+### Semantic Tokens
+
+| Token | HEX | RGB | Usage |
+|-------|-----|-----|-------|
+| `surface-base` | #F9F9F9 | rgb(249,249,249) | Page background |
+| `surface-raised` | #111111 | rgb(17,17,17) | Cards, modals, raised surfaces |
+| `surface-overlay` | #000001 | rgb(0,0,1) | Overlays, tooltips, dropdowns |
+| `text-primary` | #797979 | rgb(121,121,121) | Headings, body text |
+| `text-secondary` | #929292 | rgb(146,146,146) | Secondary, muted text |
+| `text-tertiary` | #1B1B1B | rgb(27,27,27) | Additional text |
+| `border-default` | #C8CDD1 | rgb(200,205,209) | Subtle borders, dividers |
+| `accent` | #000001 | rgb(0,0,1) | Primary actions, links, focus |
+
+## Typography
+
+- MUST use `Inter` as primary font family
+- SHOULD use single font family for consistency
+- MUST use `44px` / `extra_bold` for primary headings
+- MUST use `29px` / `700` for body text
+- SHOULD reduce font weights (currently 5 detected)
+- MUST use `text-balance` for headings and `text-pretty` for body text
+- SHOULD use `tabular-nums` for numeric data
+- NEVER modify letter-spacing unless explicitly requested
+
+### Text Styles
+
+| Style | Font | Size | Weight | Color | Count |
+|-------|------|------|--------|-------|-------|
+| `heading-1` | Inter | 44px | extra_bold | #383838 | 1 |
+| `body` | Inter | 29px | 700 | #1B1B1B | 1 |
+| `body-secondary` | Inter | 28px | 500 | #717171 | 1 |
+| `text-25px` | Inter | 25px | 500 | #828282 | 1 |
+| `text-24px` | Inter | 24px | 500 | #797979 | 1 |
+| `text-24px` | Inter | 24px | 700 | #1E1E1E | 1 |
+| `text-23px` | Inter | 23px | 400 | #6C6C6C | 1 |
+| `text-20px` | Inter | 20px | 500 | #262626 | 1 |
+| `text-18px` | Inter | 18px | 400 | #797979 | 1 |
+| `text-18px` | Inter | 18px | 500 | #373737 | 1 |
+
+### Typography Reference
+
+**Font Families:**
+- `Inter` (used 21x)
+
+**Font Sizes:** 10px, 12px, 13px, 14px, 15px, 18px, 20px, 23px, 24px, 25px, 28px, 29px, 44px
+
+## Spacing
+
+- MUST use 4px grid for spacing
+- SHOULD use spacing from scale: 4px, 5px, 6px, 10px, 25px, 54px, 59px, 92px
+- SHOULD use 5px as default gap between elements
+- NEVER use arbitrary spacing values (use design scale)
+- SHOULD maintain consistent padding within containers
+
+## Borders
+
+- MUST use border-radius from scale: 5px, 6px, 7px, 22px, 23px
+- SHOULD use 22px+ radius for pill-shaped elements
+- SHOULD limit border widths to: 1px, 3px
+- SHOULD use 23px as default border-radius
+- NEVER use arbitrary border-radius values (use design scale)
+- SHOULD use subtle borders (1px) for element separation
+
+### Border Radius Reference
+
+**Scale:** 5px, 6px, 7px, 22px, 23px
+
+## Layout
+
+- MUST design for 1920px base viewport width
+- SHOULD use consistent element widths: 8px, 181px, 66px
+- SHOULD maintain text-heavy layout with clear hierarchy
+- NEVER use `h-screen`, use `h-dvh` for full viewport height
+- MUST respect `safe-area-inset` for fixed elements
+- SHOULD use `size-*` for square elements instead of `w-*` + `h-*`
+
+### Detected Layout Patterns
+
+- **Main Content**: width: 1920px, height: 1080px
+- **Main Content**: width: 1511px, height: 790px
+- **Main Content**: width: 1098px, height: 735px
+- **Header**: height: 59px
+
+## Components
+
+### Buttons
+
+| Variant | Background | Text | Border | Height | Radius |
+|---------|------------|------|--------|--------|--------|
+| Ghost | transparent | #545454 | none | - | - |
+
+## Interactive States
+
+### Focus
+
+- MUST use `2px` outline with accent color (`#000001`)
+- MUST use `2px` outline-offset
+- NEVER remove focus indicators
+
+### Hover
+
+- Buttons (primary): lighten background by 10%
+- Buttons (secondary): use `#111111` background
+- List items: use `#111111` background
+
+### Disabled
+
+- MUST use `opacity: 0.5`
+- MUST use `cursor: not-allowed`
+
+## Interaction
+
+- MUST use an `AlertDialog` for destructive or irreversible actions
+- SHOULD use structural skeletons for loading states
+- MUST show errors next to where the action happens
+- NEVER block paste in `input` or `textarea` elements
+- MUST add an `aria-label` to icon-only buttons
+
+## Animation
+
+- NEVER add animation unless it is explicitly requested
+- MUST animate only compositor props (`transform`, `opacity`)
+- NEVER animate layout properties (`width`, `height`, `top`, `left`, `margin`, `padding`)
+- SHOULD use `ease-out` on entrance animations
+- NEVER exceed `200ms` for interaction feedback
+- SHOULD respect `prefers-reduced-motion`
+
+## Performance
+
+- NEVER animate large `blur()` or `backdrop-filter` surfaces
+- NEVER apply `will-change` outside an active animation
+- NEVER use `useEffect` for anything that can be expressed as render logic

package/skills/vercel/metadata.json

@@ -0,0 +1,16 @@
+{
+  "version": "1.0.0",
+  "organization": "Vercel",
+  "source": "https://vercel.com",
+  "extracted": "2026-01-25",
+  "categories": [
+    "ui-design",
+    "light-mode"
+  ],
+  "tokens": {
+    "colors": 8,
+    "typography": 21,
+    "spacing": 0,
+    "borders": 5
+  }
+}

package/skills/verification-loop/SKILL.md

@@ -0,0 +1,126 @@
+---
+name: verification-loop
+description: "A comprehensive verification system for Claude Code sessions."
+origin: ECC
+---
+
+# Verification Loop Skill
+
+A comprehensive verification system for Claude Code sessions.
+
+## When to Use
+
+Invoke this skill:
+- After completing a feature or significant code change
+- Before creating a PR
+- When you want to ensure quality gates pass
+- After refactoring
+
+## Verification Phases
+
+### Phase 1: Build Verification
+```bash
+# Check if project builds
+npm run build 2>&1 | tail -20
+# OR
+pnpm build 2>&1 | tail -20
+```
+
+If build fails, STOP and fix before continuing.
+
+### Phase 2: Type Check
+```bash
+# TypeScript projects
+npx tsc --noEmit 2>&1 | head -30
+
+# Python projects
+pyright . 2>&1 | head -30
+```
+
+Report all type errors. Fix critical ones before continuing.
+
+### Phase 3: Lint Check
+```bash
+# JavaScript/TypeScript
+npm run lint 2>&1 | head -30
+
+# Python
+ruff check . 2>&1 | head -30
+```
+
+### Phase 4: Test Suite
+```bash
+# Run tests with coverage
+npm run test -- --coverage 2>&1 | tail -50
+
+# Check coverage threshold
+# Target: 80% minimum
+```
+
+Report:
+- Total tests: X
+- Passed: X
+- Failed: X
+- Coverage: X%
+
+### Phase 5: Security Scan
+```bash
+# Check for secrets
+grep -rn "sk-" --include="*.ts" --include="*.js" . 2>/dev/null | head -10
+grep -rn "api_key" --include="*.ts" --include="*.js" . 2>/dev/null | head -10
+
+# Check for console.log
+grep -rn "console.log" --include="*.ts" --include="*.tsx" src/ 2>/dev/null | head -10
+```
+
+### Phase 6: Diff Review
+```bash
+# Show what changed
+git diff --stat
+git diff HEAD~1 --name-only
+```
+
+Review each changed file for:
+- Unintended changes
+- Missing error handling
+- Potential edge cases
+
+## Output Format
+
+After running all phases, produce a verification report:
+
+```
+VERIFICATION REPORT
+==================
+
+Build:     [PASS/FAIL]
+Types:     [PASS/FAIL] (X errors)
+Lint:      [PASS/FAIL] (X warnings)
+Tests:     [PASS/FAIL] (X/Y passed, Z% coverage)
+Security:  [PASS/FAIL] (X issues)
+Diff:      [X files changed]
+
+Overall:   [READY/NOT READY] for PR
+
+Issues to Fix:
+1. ...
+2. ...
+```
+
+## Continuous Mode
+
+For long sessions, run verification every 15 minutes or after major changes:
+
+```markdown
+Set a mental checkpoint:
+- After completing each function
+- After finishing a component
+- Before moving to next task
+
+Run: /verify
+```
+
+## Integration with Hooks
+
+This skill complements PostToolUse hooks but provides deeper verification.
+Hooks catch issues immediately; this skill provides comprehensive review.

package/skills/view-transitions-api/SKILL.md

@@ -0,0 +1,108 @@
+---
+name: view-transitions-api
+description: >-
+  Native browser View Transitions API for seamless page and state transitions.
+  Covers same-document transitions, cross-document MPA transitions, and framework integration.
+---
+
+# View Transitions API
+
+## Overview
+
+The View Transitions API provides a native mechanism for creating animated transitions between different views (DOM states) in a web application. It works for both SPAs (same-document) and MPAs (cross-document), eliminating the need for JavaScript animation libraries for page transitions.
+
+## When to Use
+
+- Page-to-page transitions in Next.js, Nuxt, or any framework
+- Animating between UI states (list ↔ detail, tabs, modal open/close)
+- Creating smooth "shared element" transitions (image expanding to detail page)
+- Replacing Barba.js or custom page transition code with native APIs
+
+## Same-Document Transitions (SPA)
+
+```javascript
+// Basic transition
+document.startViewTransition(() => {
+  // Update the DOM
+  updateContent(newContent);
+});
+
+// With async operations
+document.startViewTransition(async () => {
+  const data = await fetchNewPage(url);
+  document.querySelector('#content').innerHTML = data;
+});
+```
+
+### CSS for Transitions
+
+```css
+/* Default crossfade (works automatically) */
+::view-transition-old(root) {
+  animation: fade-out 0.3s ease-out;
+}
+::view-transition-new(root) {
+  animation: fade-in 0.3s ease-in;
+}
+
+/* Named transitions for specific elements */
+.hero-image {
+  view-transition-name: hero;
+}
+
+::view-transition-old(hero) {
+  animation: scale-down 0.4s ease-in-out;
+}
+::view-transition-new(hero) {
+  animation: scale-up 0.4s ease-in-out;
+}
+```
+
+## Cross-Document Transitions (MPA)
+
+```css
+/* Enable in CSS — no JavaScript needed */
+@view-transition {
+  navigation: auto;
+}
+
+/* Shared elements across pages */
+.product-card img {
+  view-transition-name: product-image;
+}
+.product-detail img {
+  view-transition-name: product-image;
+}
+```
+
+## Next.js Integration
+
+```tsx
+// app/layout.tsx
+import { unstable_ViewTransition as ViewTransition } from 'react'
+
+export default function Layout({ children }) {
+  return (
+    <html>
+      <body>
+        <ViewTransition>{children}</ViewTransition>
+      </body>
+    </html>
+  )
+}
+```
+
+## Guidelines
+
+1. **Use `view-transition-name`** to create shared element transitions
+2. **Each `view-transition-name` must be unique** on the page at transition time
+3. **Respect `prefers-reduced-motion`** — disable animations for accessibility
+4. **Use CSS for transition styling**, JavaScript for triggering
+5. **Progressive enhancement** — transitions are purely visual, pages work without them
+
+## Anti-Patterns
+
+- ❌ Using duplicate `view-transition-name` values on the same page
+- ❌ Ignoring `prefers-reduced-motion` media query
+- ❌ Heavy JavaScript animations when CSS view transitions suffice
+- ❌ Not providing fallback for unsupported browsers