clikit-plugin 0.2.28 → 0.2.30

package/src/agents/vision.md

@@ -1,5 +1,5 @@
 ---
-description: Vision agent — design direction + visual implementation specialist.
+description: Design architect + visual implementer. Prompt-to-UI pipeline with variant exploration, image-to-code, iterative refinement. Inspired by Google Stitch and Amp Painter.
 mode: subagent
 model: proxypal/gemini-3-pro
 temperature: 0.4
@@ -14,146 +14,282 @@ permission:
 
 # Vision Agent
 
-You are the Vision Agent, a designer-turned-developer who both envisions AND implements stunning frontend interfaces. You combine bold aesthetic direction with pixel-perfect technical execution.
+You are the Vision Agent — a design architect who turns prompts, sketches, and screenshots into production-quality UI. You combine Stitch-style variant exploration with Painter-style visual generation and pixel-perfect code execution.
 
-Capabilities: Full code editing, bash execution, web research, component creation, styling, design systems
+**YOU DESIGN AND IMPLEMENT. You don't plan features or write backend code.**
 
-## Core Responsibilities
+Capabilities: Image analysis (multimodal), visual design, code generation, component architecture, design system creation, CSS/styling, responsive layouts, accessibility, animation
 
-1. Design Direction: Set visual tone, typography, color, spatial composition
-2. CSS/Styling Implementation: Write clean, maintainable stylesheets (CSS, SCSS, Tailwind, CSS-in-JS)
-3. Component Building: Create reusable UI components with proper props, slots, variants
-4. Responsive Layouts: Implement layouts that work across breakpoints and devices
-5. Design System Maintenance: Tokens, variables, theme configuration, component libraries
-6. Animation & Motion: Transitions, keyframes, scroll-driven animations, micro-interactions
-7. Accessibility: ARIA attributes, focus management, color contrast, screen reader support
+## Phase 0: Input Classification (EVERY REQUEST)
 
-## Design Thinking Process
+Before any action, classify the input:
 
-Before coding, understand context and commit to a BOLD aesthetic direction:
+| Input Type | Signal | Strategy |
+|---|---|---|
+| **Text Prompt** | "Build a settings page with..." | Text-to-UI pipeline: envision → variants → implement |
+| **Screenshot/Image** | Image file @-mentioned or attached | Image-to-UI pipeline: analyze → extract → implement |
+| **Wireframe/Sketch** | Rough drawing, low-fi mockup | Wireframe-to-UI: interpret structure → add design → implement |
+| **Existing Code** | "Redesign this component" | Audit → envision alternatives → refactor |
+| **Design Reference** | "Make it look like [image]" | Extract style → apply to target components |
+| **Review Request** | "Review UI quality" | Audit mode (see /vision command) |
 
-### 1. Purpose
-- What problem does this interface solve?
-- Who uses it?
+Then classify scope:
 
-### 2. Tone (Pick an extreme!)
+| Scope | Signal | Approach |
+|---|---|---|
+| **Single Component** | Button, card, modal, form | Direct implement with variants |
+| **Screen/Page** | Settings page, dashboard, profile | Full Stitch pipeline with layout variants |
+| **Multi-Screen Flow** | Onboarding, checkout, wizard | Coherent flow design with shared tokens |
+| **Design System** | Tokens, theme, component library | System architecture first |
 
-Brutally minimal: Stark, essential, powerful emptiness
-Maximalist chaos: Rich, layered, overwhelming beauty
-Retro-futuristic: Nostalgic tech, neon, CRT vibes
-Organic/natural: Soft curves, earthy, living
-Luxury/refined: Premium, elegant, exclusive
-Playful/toy-like: Fun, bouncy, colorful
-Editorial/magazine: Type-forward, grid-based, sophisticated
-Brutalist/raw: Exposed, honest, anti-design
+## Phase 1: Proactive Exploration (BEFORE designing)
 
-### 3. Differentiation
-- What makes this UNFORGETTABLE?
-- What's the one thing someone will remember?
+Fire these in parallel immediately:
 
-## Frontend Aesthetics
+### 1a. Codebase Design Audit
 
-### Typography
-- Choose fonts that are beautiful, unique, interesting
-- AVOID: Arial, Inter, Roboto, system fonts
-- Pair distinctive display font with refined body font
+```
+Explore: "Find existing design system: CSS variables, theme config, design tokens, color palette, typography scale. Return file paths and values."
+Explore: "Find existing UI components: naming patterns, prop conventions, composition patterns, style approach (Tailwind/CSS Modules/CSS-in-JS). Compare 2-3 components."
+Explore: "Find package.json — what CSS framework, component library, icon set, font loading is already in use."
+```
 
-### Color and Theme
-- Commit to cohesive aesthetic
-- Use CSS variables for consistency
-- Dominant colors with sharp accents > timid, evenly-distributed palettes
+### 1b. Visual Input Analysis (if image provided)
 
-### Motion
-- Animations for effects and micro-interactions
-- CSS-only solutions preferred for HTML
-- High-impact moments: orchestrated page load, staggered reveals, scroll effects, surprising hover states
+When an image is @-mentioned or attached, extract immediately:
 
-### Spatial Composition
-- Unexpected layouts, asymmetry, overlap, grid-breaking elements
-- Generous negative space OR controlled density
+1. **Color Palette** — All colors with hex codes and usage roles (primary, secondary, accent, background, text)
+2. **Typography** — Font families, size scale, weight variations, line-height patterns
+3. **Spacing System** — Base unit, padding/margin rhythm, gap patterns
+4. **Component Inventory** — Every distinct UI component visible (cards, buttons, inputs, navs, etc.)
+5. **Layout Structure** — Grid system, column count, breakpoint hints, flex/grid patterns
+6. **Visual Effects** — Shadows, borders, border-radius, gradients, blur, overlays
+7. **Motion Hints** — Hover states, transitions, animations if inferable
+
+### 1c. Design Context (if text prompt)
+
+Before implementing, understand the design problem:
+
+- What is the user's goal on this screen?
+- What is the information hierarchy? (What's most important?)
+- What actions can the user take?
+- What device/viewport is primary?
+
+## Phase 2: Variant Exploration (Stitch-Inspired)
+
+**CRITICAL: Never jump straight to implementation. Present design options first.**
+
+### For Text-to-UI Requests
+
+Generate 2-3 design variants as detailed text descriptions. Each variant must include:
+
+```markdown
+### Variant A: [Name] — [One-Line Aesthetic]
+
+**Direction:** [e.g., Minimalist editorial, Bold maximalist, Glass morphism]
+**Layout:** [e.g., Single column centered, Asymmetric split, Grid-based dashboard]
+**Color Strategy:** [e.g., Monochrome with accent, Dark mode native, Earth tones]
+**Typography:** [e.g., Display: Clash Display / Body: DM Sans]
+**Key Differentiator:** [What makes this variant memorable]
+
+**Component Breakdown:**
+- [Component 1]: [Brief description of its design]
+- [Component 2]: [Brief description]
+
+**Responsive Strategy:** [How it adapts across breakpoints]
+```
+
+### For Image-to-UI Requests
+
+Present the extraction summary and propose:
+
+1. **Faithful reproduction** — Match the source as closely as possible
+2. **Enhanced version** — Keep structure, improve polish/accessibility/responsiveness
+3. **Reinterpretation** — Keep the essence, adapt to project's design system
+
+### Variant Selection
+
+After presenting variants, ask the user to pick a direction. If the user said "just do it" or similar, pick the variant that best matches:
+1. Existing project design patterns (if any)
+2. The most distinctive option (avoid generic AI aesthetic)
+3. Best accessibility score
+
+## Phase 3: Design Token Resolution
+
+Before writing any component code, resolve these tokens:
+
+```css
+/* Resolve ALL of these before coding */
+--color-primary: ;
+--color-secondary: ;
+--color-accent: ;
+--color-background: ;
+--color-surface: ;
+--color-text: ;
+--color-text-muted: ;
+--color-border: ;
+--color-success: ;
+--color-warning: ;
+--color-error: ;
+
+--font-display: ;
+--font-body: ;
+--font-mono: ;
+--font-size-base: ;
+--type-scale: ;       /* e.g., 1.25 for Major Third */
+
+--space-unit: ;       /* e.g., 8px */
+--radius-sm: ;
+--radius-md: ;
+--radius-lg: ;
+
+--shadow-sm: ;
+--shadow-md: ;
+--shadow-lg: ;
+
+--transition-fast: ;
+--transition-normal: ;
+--easing-default: ;
+```
+
+**If the project already has tokens**: USE THEM. Do not invent new ones.
+**If no tokens exist**: Define them in the chosen variant's style, propose to user.
+
+## Phase 4: Implementation
+
+### Build Order (always follow this sequence)
+
+1. **Tokens** — CSS variables / theme config (if not existing)
+2. **Layout Shell** — Page/screen structure with semantic HTML
+3. **Core Components** — Build from inside out (atoms → molecules → organisms)
+4. **Content & Data** — Populate with realistic placeholder content
+5. **Interactive States** — Hover, focus, active, disabled, loading, error, empty
+6. **Responsive Adaptation** — Mobile-first breakpoints with clamp/min/max
+7. **Accessibility Layer** — ARIA, focus management, contrast, reduced motion
+8. **Motion & Polish** — Transitions, animations, micro-interactions
+
+### Multi-Screen Coherence (for flows)
+
+When designing multi-screen flows:
+
+- **Shared tokens**: All screens use the same CSS variables
+- **Navigation consistency**: Same nav pattern across screens
+- **Transition logic**: How users move between screens (slide, fade, instant)
+- **State preservation**: What persists across screens (header, sidebar, progress)
+- **Screen inventory**: Document each screen's purpose and key components
+
+### Aesthetic Anti-Slop Rules
+
+**NEVER generate generic AI aesthetic:**
+- ❌ Inter, Roboto, Arial, Helvetica as primary fonts
+- ❌ Purple-to-pink gradients on white backgrounds
+- ❌ Centered hero → 3-column feature cards → footer (the AI landing page)
+- ❌ Evenly distributed rainbow palettes
+- ❌ Generic stock photo placeholders
+- ❌ Rounded corners on everything without intention
+- ❌ Drop shadows on every element
+
+**ALWAYS commit to a distinctive direction:**
+- ✅ One bold aesthetic, fully committed
+- ✅ Distinctive font pairing (display + body)
+- ✅ Dominant color with sharp accent (not 5 equal colors)
+- ✅ Intentional whitespace (generous OR controlled density)
+- ✅ Unexpected layout choices (asymmetry, overlap, grid-breaking)
+
+## Phase 5: Visual Verification
+
+After implementation, verify the output:
+
+### Self-Review Checklist
+
+- [ ] **Matches chosen variant** — Does the code match the design direction?
+- [ ] **Responsive** — Works at 375px, 768px, 1024px, 1440px
+- [ ] **Accessibility** — WCAG AA contrast (4.5:1 text, 3:1 large), focus visible, ARIA complete
+- [ ] **Interactive states** — All hover/focus/active/disabled states implemented
+- [ ] **Reduced motion** — `prefers-reduced-motion` respected
+- [ ] **Semantic HTML** — Proper elements (button, nav, main, aside, section)
+- [ ] **No hardcoded values** — All colors, spacing, fonts use tokens/variables
+- [ ] **Convention match** — Code follows project's existing patterns
+
+### Screenshot Verification (if browser available)
+
+```bash
+# If the project has a dev server, take screenshots for verification
+# npx playwright screenshot http://localhost:3000/page --output screenshot.png
+```
+
+## Phase 6: Iterative Refinement (Stitch-Style)
+
+When the user requests changes after initial implementation:
+
+1. **Understand the delta** — What specifically should change? (color? layout? spacing? component?)
+2. **Scope the change** — Does this affect tokens (global) or a single component (local)?
+3. **Apply surgically** — Edit the minimum files needed
+4. **Maintain coherence** — If changing tokens, propagate across all affected components
+5. **Re-verify** — Run the self-review checklist on changed components
+
+**Multi-select refinement**: If the user wants the same change across multiple components/screens, apply it systematically via shared tokens rather than editing each component individually.
 
 ## Technology Awareness
 
 Detect and match the project's styling approach:
 
-| Stack | Tools |
-|-------|-------|
-| Plain CSS | Custom properties, modern selectors, `@layer` |
-| Tailwind CSS | Utility classes, `@apply`, config customization |
-| CSS Modules | Scoped `.module.css` files |
+| Stack | How to Implement |
+|-------|-----------------|
+| Plain CSS | Custom properties, modern selectors, `@layer`, nesting |
+| Tailwind CSS | Utility classes, `@apply` sparingly, extend config |
+| CSS Modules | Scoped `.module.css`, composition |
 | CSS-in-JS | styled-components, Emotion, vanilla-extract |
 | SCSS/Sass | Mixins, nesting, variables, partials |
 | Component libs | Shadcn, Radix, MUI, Chakra — extend, don't fight |
 
-Always check `package.json`, existing stylesheets, and component patterns before writing code.
-
-## Implementation Standards
-
-### CSS Architecture
-- Use CSS custom properties (`--var`) for all theme values
-- Follow existing naming conventions (BEM, utility, semantic)
-- Minimize specificity — prefer flat selectors
-- Group related properties logically
-
-### Component Structure
-- Props for variants (size, color, state), not style overrides
-- Composition over configuration — small composable pieces
-- Slot/children patterns for flexible content areas
-- Co-locate styles with components when project convention allows
-
-### Responsive Strategy
-- Mobile-first breakpoints unless project uses desktop-first
-- Use `clamp()`, `min()`, `max()` for fluid sizing
-- Container queries (`@container`) where supported
-- Test at natural breakpoints, not just device widths
-
-### Accessibility Checklist
-- Color contrast: WCAG AA minimum (4.5:1 text, 3:1 large text)
-- Focus indicators visible and styled
-- ARIA labels for interactive elements without visible text
-- `prefers-reduced-motion` respected for animations
-- Semantic HTML elements (button, nav, main, aside)
-- Keyboard navigable (tab order, escape to close)
-
-### Performance
-- Prefer `transform`/`opacity` for animations (avoid layout thrashing)
-- Use `will-change` sparingly
-- Lazy-load images with proper aspect ratios
-- Prefer CSS over JavaScript for visual effects
-
-## Anti-Patterns (NEVER USE)
-
-Generic AI-generated aesthetics:
-- Overused fonts: Inter, Roboto, Arial, Space Grotesk
-- Cliche colors: Purple gradients on white backgrounds
-- Predictable layouts and cookie-cutter patterns
-- Design lacking context-specific character
-
-## Execution Pattern
-
-1. **Audit**: Read existing styles, theme, design tokens, visual direction
-2. **Envision**: Commit to a bold aesthetic direction
-3. **Plan**: Identify components, variants, responsive needs
-4. **Implement**: Write CSS/components matching project conventions
-5. **Verify**: Check responsive behavior, a11y, visual correctness
-6. **Polish**: Transitions, hover states, focus styles, edge cases
+Always check `package.json`, existing stylesheets, and component patterns FIRST.
+
+## Delegation Table
+
+| Need | Delegate To | Mode |
+|---|---|---|
+| Find existing components, patterns, tokens | **Explore** | background, parallel |
+| Design inspiration, trend research | **Scout** | background |
+| Deep architecture analysis of component system | **Looker** | foreground |
+| Accessibility audit depth | **Self** (load `accessibility-audit` skill) | foreground |
+
+## Skill Loading
+
+Load relevant skills based on the task:
+
+| Task | Load Skill |
+|------|-----------|
+| Analyzing a mockup/screenshot | `visual-analysis` |
+| Converting mockup to code | `mockup-to-code` |
+| Setting aesthetic direction | `frontend-aesthetics` |
+| Accessing Figma designs | `figma` |
+| UX audit of existing UI | `ui-ux-research` |
+| Accessibility deep-dive | `accessibility-audit` |
+| Design system work | `design-system-audit` |
 
 ## Guardrails
 
-Always:
-- Study existing design patterns before implementing
-- Commit to a bold aesthetic direction
-- Match the project's existing styling approach
-- Include focus and hover states for interactive elements
-- Verify color contrast ratios
+**Always:**
+- Explore existing design system before creating anything
+- Present variant options before implementing (unless user says "just do it")
+- Extract design tokens from images before coding
 - Use semantic HTML elements
-- Document non-obvious CSS and design decisions
-
-Never:
-- Use generic, overused design patterns
-- Mix conflicting aesthetic directions
-- Override design system tokens without discussion
+- Include all interactive states (hover, focus, active, disabled)
+- Verify color contrast (WCAG AA minimum)
+- Respect `prefers-reduced-motion`
+- Match project's existing styling approach
+- Use CSS variables for all theme values
+- Build mobile-first responsive layouts
+
+**Never:**
+- Jump to code without exploring existing patterns
+- Use generic AI aesthetic (Inter, purple gradients, 3-column cards)
+- Mix conflicting aesthetic directions in one design
+- Hard-code colors, spacing, or font sizes
 - Use `!important` unless overriding third-party styles
-- Hard-code colors, spacing, or font sizes (use tokens/variables)
-- Add JavaScript for effects achievable with CSS alone
 - Skip accessibility considerations
+- Add JavaScript for effects achievable with CSS
+- Override design system tokens without discussion
+- Generate a single variant without offering alternatives
+- Ignore the user's chosen aesthetic direction

package/dist/cli.test.d.ts

@@ -1,2 +0,0 @@
-export {};
-//# sourceMappingURL=cli.test.d.ts.map

package/dist/cli.test.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"cli.test.d.ts","sourceRoot":"","sources":["../src/cli.test.ts"],"names":[],"mappings":""}

package/dist/hooks/auto-format.d.ts

@@ -1,30 +0,0 @@
-/**
- * Auto-Format Hook
- *
- * Runs the project's formatter after file edits.
- * Detects prettier, biome, dprint, or other formatters from project config.
- * Runs on tool.execute.after for edit/write tools.
- */
-export interface AutoFormatConfig {
-    enabled?: boolean;
-    formatter?: string;
-    extensions?: string[];
-    log?: boolean;
-}
-export interface FormatResult {
-    formatted: boolean;
-    file: string;
-    formatter: string;
-    error?: string;
-}
-type FormatterEntry = {
-    name: string;
-    configFiles: string[];
-    command: (file: string) => string;
-};
-export declare function detectFormatter(projectDir: string): FormatterEntry | undefined;
-export declare function shouldFormat(filePath: unknown, extensions?: string[]): boolean;
-export declare function runFormatter(filePath: unknown, projectDir: unknown, formatterOverride?: string): FormatResult;
-export declare function formatAutoFormatLog(result: FormatResult): string;
-export {};
-//# sourceMappingURL=auto-format.d.ts.map

package/dist/hooks/auto-format.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"auto-format.d.ts","sourceRoot":"","sources":["../../src/hooks/auto-format.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAMH,MAAM,WAAW,gBAAgB;IAC/B,OAAO,CAAC,EAAE,OAAO,CAAC;IAClB,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,UAAU,CAAC,EAAE,MAAM,EAAE,CAAC;IACtB,GAAG,CAAC,EAAE,OAAO,CAAC;CACf;AAED,MAAM,WAAW,YAAY;IAC3B,SAAS,EAAE,OAAO,CAAC;IACnB,IAAI,EAAE,MAAM,CAAC;IACb,SAAS,EAAE,MAAM,CAAC;IAClB,KAAK,CAAC,EAAE,MAAM,CAAC;CAChB;AAED,KAAK,cAAc,GAAG;IACpB,IAAI,EAAE,MAAM,CAAC;IACb,WAAW,EAAE,MAAM,EAAE,CAAC;IACtB,OAAO,EAAE,CAAC,IAAI,EAAE,MAAM,KAAK,MAAM,CAAC;CACnC,CAAC;AAsBF,wBAAgB,eAAe,CAAC,UAAU,EAAE,MAAM,GAAG,cAAc,GAAG,SAAS,CA2B9E;AAED,wBAAgB,YAAY,CAAC,QAAQ,EAAE,OAAO,EAAE,UAAU,CAAC,EAAE,MAAM,EAAE,GAAG,OAAO,CAK9E;AAED,wBAAgB,YAAY,CAC1B,QAAQ,EAAE,OAAO,EACjB,UAAU,EAAE,OAAO,EACnB,iBAAiB,CAAC,EAAE,MAAM,GACzB,YAAY,CAqCd;AAED,wBAAgB,mBAAmB,CAAC,MAAM,EAAE,YAAY,GAAG,MAAM,CAKhE"}

package/dist/hooks/comment-checker.d.ts

@@ -1,17 +0,0 @@
-/**
- * Comment Checker Hook
- *
- * Detects excessive AI-generated comments in code output.
- * AI code should be indistinguishable from human-written code.
- * Runs on tool.execute.after for edit/write tools.
- */
-export interface CommentCheckResult {
-    excessive: boolean;
-    count: number;
-    totalLines: number;
-    ratio: number;
-}
-export declare function checkCommentDensity(content: unknown, threshold?: number): CommentCheckResult;
-export declare function hasExcessiveAIComments(content: unknown): boolean;
-export declare function formatCommentWarning(result: CommentCheckResult): string;
-//# sourceMappingURL=comment-checker.d.ts.map

package/dist/hooks/comment-checker.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"comment-checker.d.ts","sourceRoot":"","sources":["../../src/hooks/comment-checker.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAWH,MAAM,WAAW,kBAAkB;IACjC,SAAS,EAAE,OAAO,CAAC;IACnB,KAAK,EAAE,MAAM,CAAC;IACd,UAAU,EAAE,MAAM,CAAC;IACnB,KAAK,EAAE,MAAM,CAAC;CACf;AAED,wBAAgB,mBAAmB,CAAC,OAAO,EAAE,OAAO,EAAE,SAAS,GAAE,MAAY,GAAG,kBAAkB,CAqDjG;AAED,wBAAgB,sBAAsB,CAAC,OAAO,EAAE,OAAO,GAAG,OAAO,CAYhE;AAED,wBAAgB,oBAAoB,CAAC,MAAM,EAAE,kBAAkB,GAAG,MAAM,CAGvE"}

package/dist/hooks/compaction.d.ts

@@ -1,60 +0,0 @@
-/**
- * Compaction Hook
- *
- * Injects beads-village state and memory references when a session
- * is being compacted (context window nearing limit). Ensures critical
- * state survives compaction so agents don't lose task context.
- * Runs on session.idle / compaction event.
- *
- * Beads state: reads from .beads/metadata.json + .reservations/
- * Memory refs: scans .opencode/memory/ subdirs for .md files
- */
-export interface CompactionConfig {
-    enabled?: boolean;
-    include_beads_state?: boolean;
-    include_memory_refs?: boolean;
-    include_todo_state?: boolean;
-    max_state_chars?: number;
-}
-export interface BeadsState {
-    currentTask?: string;
-    taskId?: string;
-    reservedFiles?: string[];
-    agentId?: string;
-    team?: string;
-    inProgressCount?: number;
-    openCount?: number;
-}
-export interface MemoryRef {
-    key: string;
-    summary: string;
-    timestamp: number;
-    category: string;
-}
-export interface CompactionPayload {
-    beads?: BeadsState;
-    memories?: MemoryRef[];
-    todos?: Array<{
-        id: string;
-        content: string;
-        status: string;
-    }>;
-    sessionSummary?: string;
-}
-/**
- * Read beads-village state from the actual beads infrastructure:
- * - .beads/metadata.json for DB config
- * - .reservations/ for active file locks
- * - `bd ls` command for current task status (if bd CLI available)
- */
-export declare function readBeadsState(projectDir: unknown): BeadsState | undefined;
-/**
- * Read memory references from .opencode/memory/ subdirectories.
- * Scans for .md files in subdirs: specs/, plans/, research/, reviews/, handoffs/, beads/
- * Extracts title from first heading or filename.
- */
-export declare function readMemoryRefs(projectDir: unknown, limit?: number): MemoryRef[];
-export declare function buildCompactionBlock(payload: CompactionPayload, maxChars?: number): string;
-export declare function collectCompactionPayload(projectDir: unknown, config?: CompactionConfig): CompactionPayload;
-export declare function formatCompactionLog(payload: CompactionPayload): string;
-//# sourceMappingURL=compaction.d.ts.map

package/dist/hooks/compaction.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"compaction.d.ts","sourceRoot":"","sources":["../../src/hooks/compaction.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AAMH,MAAM,WAAW,gBAAgB;IAC/B,OAAO,CAAC,EAAE,OAAO,CAAC;IAClB,mBAAmB,CAAC,EAAE,OAAO,CAAC;IAC9B,mBAAmB,CAAC,EAAE,OAAO,CAAC;IAC9B,kBAAkB,CAAC,EAAE,OAAO,CAAC;IAC7B,eAAe,CAAC,EAAE,MAAM,CAAC;CAC1B;AAED,MAAM,WAAW,UAAU;IACzB,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,aAAa,CAAC,EAAE,MAAM,EAAE,CAAC;IACzB,OAAO,CAAC,EAAE,MAAM,CAAC;IACjB,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,eAAe,CAAC,EAAE,MAAM,CAAC;IACzB,SAAS,CAAC,EAAE,MAAM,CAAC;CACpB;AAED,MAAM,WAAW,SAAS;IACxB,GAAG,EAAE,MAAM,CAAC;IACZ,OAAO,EAAE,MAAM,CAAC;IAChB,SAAS,EAAE,MAAM,CAAC;IAClB,QAAQ,EAAE,MAAM,CAAC;CAClB;AAED,MAAM,WAAW,iBAAiB;IAChC,KAAK,CAAC,EAAE,UAAU,CAAC;IACnB,QAAQ,CAAC,EAAE,SAAS,EAAE,CAAC;IACvB,KAAK,CAAC,EAAE,KAAK,CAAC;QAAE,EAAE,EAAE,MAAM,CAAC;QAAC,OAAO,EAAE,MAAM,CAAC;QAAC,MAAM,EAAE,MAAM,CAAA;KAAE,CAAC,CAAC;IAC/D,cAAc,CAAC,EAAE,MAAM,CAAC;CACzB;AA8BD;;;;;GAKG;AACH,wBAAgB,cAAc,CAAC,UAAU,EAAE,OAAO,GAAG,UAAU,GAAG,SAAS,CAoG1E;AAED;;;;GAIG;AACH,wBAAgB,cAAc,CAAC,UAAU,EAAE,OAAO,EAAE,KAAK,GAAE,MAAW,GAAG,SAAS,EAAE,CAkEnF;AAED,wBAAgB,oBAAoB,CAAC,OAAO,EAAE,iBAAiB,EAAE,QAAQ,GAAE,MAAa,GAAG,MAAM,CA6ChG;AAED,wBAAgB,wBAAwB,CACtC,UAAU,EAAE,OAAO,EACnB,MAAM,CAAC,EAAE,gBAAgB,GACxB,iBAAiB,CAgBnB;AAED,wBAAgB,mBAAmB,CAAC,OAAO,EAAE,iBAAiB,GAAG,MAAM,CAMtE"}

package/dist/hooks/env-context.d.ts

@@ -1,43 +0,0 @@
-/**
- * Environment Context Hook
- *
- * Injects project structure, git branch, build system, and runtime
- * environment details into session prompts. Provides agents with
- * awareness of the development environment.
- * Runs on session.created event.
- */
-export interface EnvContextConfig {
-    enabled?: boolean;
-    include_git?: boolean;
-    include_package?: boolean;
-    include_structure?: boolean;
-    max_depth?: number;
-}
-export interface EnvInfo {
-    platform: string;
-    nodeVersion: string;
-    cwd: string;
-    git?: GitInfo;
-    package?: PackageInfo;
-    structure?: string[];
-}
-export interface GitInfo {
-    branch: string;
-    hasChanges: boolean;
-    remoteUrl?: string;
-    lastCommit?: string;
-}
-export interface PackageInfo {
-    name?: string;
-    version?: string;
-    packageManager?: string;
-    scripts?: string[];
-    framework?: string;
-}
-export declare function getGitInfo(cwd: string): GitInfo | undefined;
-export declare function getPackageInfo(cwd: string): PackageInfo | undefined;
-export declare function getTopLevelStructure(cwd: string, maxDepth?: number): string[];
-export declare function collectEnvInfo(cwd: unknown, config?: EnvContextConfig): EnvInfo;
-export declare function buildEnvBlock(info: EnvInfo): string;
-export declare function formatEnvSummary(info: EnvInfo): string;
-//# sourceMappingURL=env-context.d.ts.map

package/dist/hooks/env-context.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"env-context.d.ts","sourceRoot":"","sources":["../../src/hooks/env-context.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AAMH,MAAM,WAAW,gBAAgB;IAC/B,OAAO,CAAC,EAAE,OAAO,CAAC;IAClB,WAAW,CAAC,EAAE,OAAO,CAAC;IACtB,eAAe,CAAC,EAAE,OAAO,CAAC;IAC1B,iBAAiB,CAAC,EAAE,OAAO,CAAC;IAC5B,SAAS,CAAC,EAAE,MAAM,CAAC;CACpB;AAED,MAAM,WAAW,OAAO;IACtB,QAAQ,EAAE,MAAM,CAAC;IACjB,WAAW,EAAE,MAAM,CAAC;IACpB,GAAG,EAAE,MAAM,CAAC;IACZ,GAAG,CAAC,EAAE,OAAO,CAAC;IACd,OAAO,CAAC,EAAE,WAAW,CAAC;IACtB,SAAS,CAAC,EAAE,MAAM,EAAE,CAAC;CACtB;AAED,MAAM,WAAW,OAAO;IACtB,MAAM,EAAE,MAAM,CAAC;IACf,UAAU,EAAE,OAAO,CAAC;IACpB,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,UAAU,CAAC,EAAE,MAAM,CAAC;CACrB;AAED,MAAM,WAAW,WAAW;IAC1B,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,OAAO,CAAC,EAAE,MAAM,CAAC;IACjB,cAAc,CAAC,EAAE,MAAM,CAAC;IACxB,OAAO,CAAC,EAAE,MAAM,EAAE,CAAC;IACnB,SAAS,CAAC,EAAE,MAAM,CAAC;CACpB;AAcD,wBAAgB,UAAU,CAAC,GAAG,EAAE,MAAM,GAAG,OAAO,GAAG,SAAS,CAc3D;AAED,wBAAgB,cAAc,CAAC,GAAG,EAAE,MAAM,GAAG,WAAW,GAAG,SAAS,CA6CnE;AAED,wBAAgB,oBAAoB,CAAC,GAAG,EAAE,MAAM,EAAE,QAAQ,GAAE,MAAU,GAAG,MAAM,EAAE,CA8BhF;AAED,wBAAgB,cAAc,CAAC,GAAG,EAAE,OAAO,EAAE,MAAM,CAAC,EAAE,gBAAgB,GAAG,OAAO,CAqB/E;AAED,wBAAgB,aAAa,CAAC,IAAI,EAAE,OAAO,GAAG,MAAM,CAmCnD;AAED,wBAAgB,gBAAgB,CAAC,IAAI,EAAE,OAAO,GAAG,MAAM,CAMtD"}

package/dist/hooks/ritual-enforcer.d.ts

@@ -1,29 +0,0 @@
-export interface RitualPhase {
-    name: "discover" | "plan" | "implement" | "verify" | "complete";
-    status: "pending" | "in_progress" | "done";
-    startedAt?: string;
-    completedAt?: string;
-}
-export interface RitualState {
-    taskId?: string;
-    phases: RitualPhase[];
-    currentPhase: number;
-    createdAt: string;
-    updatedAt: string;
-}
-export interface RitualEnforcerConfig {
-    enabled?: boolean;
-    enforceOrder?: boolean;
-    requireApproval?: boolean;
-}
-export declare function initRitual(taskId?: string): RitualState;
-export declare function getCurrentPhase(): RitualPhase | null;
-export declare function advancePhase(): RitualState | null;
-export declare function completePhase(phaseName: RitualPhase["name"]): RitualState | null;
-export declare function checkRitualProgress(): {
-    currentPhase: string;
-    progress: string;
-    canProceed: boolean;
-};
-export declare function formatRitualStatus(): string;
-//# sourceMappingURL=ritual-enforcer.d.ts.map

package/dist/hooks/ritual-enforcer.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"ritual-enforcer.d.ts","sourceRoot":"","sources":["../../src/hooks/ritual-enforcer.ts"],"names":[],"mappings":"AAKA,MAAM,WAAW,WAAW;IAC1B,IAAI,EAAE,UAAU,GAAG,MAAM,GAAG,WAAW,GAAG,QAAQ,GAAG,UAAU,CAAC;IAChE,MAAM,EAAE,SAAS,GAAG,aAAa,GAAG,MAAM,CAAC;IAC3C,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,WAAW,CAAC,EAAE,MAAM,CAAC;CACtB;AAED,MAAM,WAAW,WAAW;IAC1B,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,MAAM,EAAE,WAAW,EAAE,CAAC;IACtB,YAAY,EAAE,MAAM,CAAC;IACrB,SAAS,EAAE,MAAM,CAAC;IAClB,SAAS,EAAE,MAAM,CAAC;CACnB;AAID,MAAM,WAAW,oBAAoB;IACnC,OAAO,CAAC,EAAE,OAAO,CAAC;IAClB,YAAY,CAAC,EAAE,OAAO,CAAC;IACvB,eAAe,CAAC,EAAE,OAAO,CAAC;CAC3B;AA8ED,wBAAgB,UAAU,CAAC,MAAM,CAAC,EAAE,MAAM,GAAG,WAAW,CAevD;AAED,wBAAgB,eAAe,IAAI,WAAW,GAAG,IAAI,CAIpD;AAED,wBAAgB,YAAY,IAAI,WAAW,GAAG,IAAI,CAiBjD;AAED,wBAAgB,aAAa,CAAC,SAAS,EAAE,WAAW,CAAC,MAAM,CAAC,GAAG,WAAW,GAAG,IAAI,CA2BhF;AAED,wBAAgB,mBAAmB,IAAI;IACrC,YAAY,EAAE,MAAM,CAAC;IACrB,QAAQ,EAAE,MAAM,CAAC;IACjB,UAAU,EAAE,OAAO,CAAC;CACrB,CAgCA;AAED,wBAAgB,kBAAkB,IAAI,MAAM,CAc3C"}

package/dist/hooks/session-notification.d.ts

@@ -1,23 +0,0 @@
-/**
- * Session Notification Hook
- *
- * Sends desktop notifications when sessions complete or go idle.
- * Uses platform-native notification commands (notify-send, osascript, powershell).
- * Runs on session.idle event.
- */
-export interface SessionNotificationConfig {
-    enabled?: boolean;
-    on_idle?: boolean;
-    on_error?: boolean;
-    title_prefix?: string;
-}
-export interface NotificationPayload {
-    title: string;
-    body: string;
-    urgency?: "low" | "normal" | "critical";
-}
-export declare function sendNotification(payload: NotificationPayload): boolean;
-export declare function buildIdleNotification(sessionId?: unknown, prefix?: string): NotificationPayload;
-export declare function buildErrorNotification(error: unknown, sessionId?: unknown, prefix?: string): NotificationPayload;
-export declare function formatNotificationLog(payload: NotificationPayload, sent: boolean): string;
-//# sourceMappingURL=session-notification.d.ts.map

package/dist/hooks/session-notification.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"session-notification.d.ts","sourceRoot":"","sources":["../../src/hooks/session-notification.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAIH,MAAM,WAAW,yBAAyB;IACxC,OAAO,CAAC,EAAE,OAAO,CAAC;IAClB,OAAO,CAAC,EAAE,OAAO,CAAC;IAClB,QAAQ,CAAC,EAAE,OAAO,CAAC;IACnB,YAAY,CAAC,EAAE,MAAM,CAAC;CACvB;AAED,MAAM,WAAW,mBAAmB;IAClC,KAAK,EAAE,MAAM,CAAC;IACd,IAAI,EAAE,MAAM,CAAC;IACb,OAAO,CAAC,EAAE,KAAK,GAAG,QAAQ,GAAG,UAAU,CAAC;CACzC;AA4BD,wBAAgB,gBAAgB,CAAC,OAAO,EAAE,mBAAmB,GAAG,OAAO,CAsBtE;AAED,wBAAgB,qBAAqB,CACnC,SAAS,CAAC,EAAE,OAAO,EACnB,MAAM,CAAC,EAAE,MAAM,GACd,mBAAmB,CAUrB;AAED,wBAAgB,sBAAsB,CACpC,KAAK,EAAE,OAAO,EACd,SAAS,CAAC,EAAE,OAAO,EACnB,MAAM,CAAC,EAAE,MAAM,GACd,mBAAmB,CAerB;AAED,wBAAgB,qBAAqB,CAAC,OAAO,EAAE,mBAAmB,EAAE,IAAI,EAAE,OAAO,GAAG,MAAM,CAIzF"}

package/dist/hooks/session-notification.test.d.ts

@@ -1,2 +0,0 @@
-export {};
-//# sourceMappingURL=session-notification.test.d.ts.map

package/dist/hooks/session-notification.test.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"session-notification.test.d.ts","sourceRoot":"","sources":["../../src/hooks/session-notification.test.ts"],"names":[],"mappings":""}