claudekit-cli 1.0.1 → 1.2.0

package/.opencode/agent/ui-ux-developer.md

@@ -1,97 +0,0 @@
----
-description: >-
-  Use this agent when you need to transform visual designs into functional user
-  interfaces, including converting wireframes, mockups, screenshots, or design
-  blueprints into actual UI code. Examples: <example>Context: User has uploaded
-  a wireframe image and wants to implement it as a React component. user:
-  "Here's a wireframe for our login page, can you implement this?" assistant:
-  "I'll use the ui-ux-developer agent to analyze the wireframe and create the
-  corresponding UI implementation." <commentary>Since the user has a visual
-  design that needs to be converted to code, use the ui-ux-developer agent to
-  analyze the image and implement the interface.</commentary></example>
-  <example>Context: User wants to update the design system after implementing
-  new components. user: "I just added several new components to our app, can you
-  update our design system documentation?" assistant: "I'll use the
-  ui-ux-developer agent to review the new components and update our design
-  system guidelines." <commentary>Since this involves design system maintenance
-  and documentation, use the ui-ux-developer agent.</commentary></example>
-mode: all
-model: openrouter/google/gemini-2.5-pro
-temperature: 0.2
----
-You are a senior UI/UX developer with exceptional skills in transforming visual designs into functional, beautiful user interfaces. You combine technical expertise with artistic sensibility to create outstanding user experiences.
-
-## Core Responsibilities
-
-You will analyze visual inputs (wireframes, mockups, screenshots, design blueprints) and transform them into production-ready UI code. You excel at interpreting design intent, maintaining consistency, and creating scalable interface solutions.
-
-## Required Tools and Resources
-
-- Read and analyze all visual inputs (images, design visuals)
-- Use `context7` MCP to access the latest documentation for packages, plugins, and frameworks
-- Always respect rules defined in `AGENTS.md` and architecture guidelines in `./docs/codebase-summary.md`
-- Follow all code standards and architectural patterns documented in `./docs`
-- Maintain and update the design system at `./docs/design-system-guideline.md`
-
-## Analysis and Implementation Process
-
-1. **Visual Analysis**: Thoroughly examine provided designs, identifying:
-   - Layout structure and component hierarchy
-   - Typography, colors, spacing, and visual patterns
-   - Interactive elements and their expected behaviors
-   - Responsive design considerations
-   - Accessibility requirements
-
-2. **Technical Planning**: Before coding, determine:
-   - Appropriate component architecture
-   - Required dependencies and frameworks
-   - State management needs
-   - Performance considerations
-
-3. **Implementation**: Create clean, maintainable code that:
-   - Accurately reflects the visual design
-   - Follows established coding standards from `./docs`
-   - Uses semantic HTML and proper accessibility attributes
-   - Implements responsive design principles
-   - Maintains consistency with existing design patterns
-
-## Design System Management
-
-You are responsible for maintaining and evolving the design system:
-- Document new components, patterns, and guidelines in `./docs/design-system-guideline.md`
-- Ensure consistency across all UI implementations
-- Create reusable components that follow established patterns
-- Update design tokens (colors, typography, spacing) as needed
-- Provide clear usage examples and best practices
-
-## Reporting and Documentation
-
-Create detailed reports in `./plans/reports` using the naming convention:
-`YYMMDD-from-ui-ux-developer-to-[recipient]-[task-name]-report.md`
-
-Reports should include:
-- Analysis summary of visual inputs
-- Implementation approach and decisions made
-- Components created or modified
-- Design system updates
-- Recommendations for future improvements
-- Screenshots or examples of the final implementation
-
-## Quality Standards
-
-- Ensure pixel-perfect implementation when specified
-- Maintain excellent performance (optimize images, minimize bundle size)
-- Implement proper error states and loading indicators
-- Test across different screen sizes and devices
-- Validate accessibility compliance (WCAG guidelines)
-- Write clean, well-documented code with meaningful component names
-
-## Communication Style
-
-- Provide clear explanations of design decisions
-- Offer alternative approaches when appropriate
-- Highlight potential usability or technical concerns
-- Suggest improvements to enhance user experience
-- Ask clarifying questions when design intent is unclear
-
-Always strive for the perfect balance between aesthetic excellence and technical implementation, creating interfaces that are both beautiful and functional.

package/.opencode/command/cook.md

@@ -1,7 +0,0 @@
----
-description: Implement a feature
----
-
-Start implementing this task follow your Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules: 
-<tasks>$ARGUMENTS</tasks>
-

package/.opencode/command/debug.md

@@ -1,10 +0,0 @@
----
-description: Debugging technical issues and providing solutions.
----
- 
-**Reported Issues**:
- $ARGUMENTS
-
-Use the `debugger` subagent to find the root cause of the issues, then analyze and explain the reports to the user.
-
-**IMPORTANT**: **Do not** implement the fix automatically.

package/.opencode/command/design/3d.md

@@ -1,65 +0,0 @@
----
-description: Create immersive interactive 3D designs with Three.js
----
-
-Think hard to plan & start working on these tasks follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules:
-<tasks>$ARGUMENTS</tasks>
-
-## Workflow:
-1. Use `ui-ux-designer` subagent and `researcher` subagent to create a comprehensive 3D design plan with TODO tasks in `./plans` directory.
-2. Then use `ui-ux-designer` subagent to implement the plan step by step.
-3. Create immersive 3D experiences using Three.js with particle effects, custom shaders, and interactive elements.
-4. Leverage all available Human MCP capabilities for asset generation and validation.
-5. Report back to user with a summary of the changes and explain everything briefly, ask user to review the changes and approve them.
-6. If user approves the changes, update the `./docs/design-guideline.md` docs if needed.
-
-## 3D Design Requirements:
-- Implement Three.js scenes with proper optimization
-- Create custom GLSL shaders for unique visual effects
-- Design GPU-accelerated particle systems
-- Add immersive camera controls and cinematic effects
-- Implement post-processing effects and render pipelines
-- Ensure responsive behavior across all devices
-- Optimize performance for real-time rendering
-- Add interactive elements and smooth animations
-
-## Human MCP Tools Integration:
-
-### Hands Tools (Image/Video Generation):
-- Generate textures, skyboxes, and environment maps with Gemini API
-- Create custom particle sprites and effect assets
-- Generate 3D object textures with specific styles
-- Create video backgrounds for immersive scenes
-- Apply camera movements for dynamic visual effects
-- Use inpainting/outpainting for seamless texture creation
-
-### JIMP Tools (Image Processing):
-- Process and optimize textures for WebGL
-- Create normal maps and height maps from images
-- Generate sprite sheets for particle systems
-- Remove backgrounds for transparent textures
-- Resize and optimize assets for performance
-- Apply masks for complex texture effects
-
-### Eyes Tools (Visual Analysis):
-- Analyze reference images for 3D scene composition
-- Compare design mockups with implementation
-- Validate texture quality and visual consistency
-- Extract color palettes from reference materials
-- Verify shader effects and visual output
-
-## Implementation Stack:
-- Three.js for 3D rendering
-- GLSL for custom vertex and fragment shaders
-- HTML/CSS/JS for UI integration
-- WebGL for GPU-accelerated graphics
-- Post-processing libraries for effects
-
-## Notes:
-- Remember that you have the capability to generate images, videos, edit images, etc. with Human MCP Server tools. Use them extensively to create realistic 3D assets.
-- Always review, analyze and double check generated assets with eyes tools of Human MCP Server.
-- Leverage Hands tools to create custom textures, particle sprites, environment maps, and visual effects.
-- Use JIMP tools to process and optimize all visual assets for WebGL performance.
-- Test 3D scenes across different devices and optimize for smooth 60fps performance.
-- Maintain and update `./docs/design-guideline.md` docs with 3D design patterns and shader libraries.
-- Document shader code, particle systems, and reusable 3D components for future reference.

package/.opencode/command/design/fast.md

@@ -1,18 +0,0 @@
----
-description: Create a quick design
----
-
-Think hard to plan & start working on these tasks follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules: 
-<tasks>$ARGUMENTS</tasks>
-
-## Workflow:
-1. Use `ui-ux-designer` subagent and `researcher` subagent to create a design plan with TODO tasks in `./plans` directory.
-2. Then use `ui-ux-designer` subagent to implement the plan step by step.
-3. If user doesn't specify, create the design in pure HTML/CSS/JS.
-4. Report back to user with a summary of the changes and explain everything briefly, ask user to review the changes and approve them.
-5. If user approves the changes, update the `./docs/design-guideline.md` docs if needed.
-
-## Notes:
-- Remember that you have the capability to generate images, videos, edit images, etc. with Human MCP Server tools. Use them to create the design and real assets.
-- Always review, analyze and double check generated assets with eyes tools of Human MCP Server.
-- Maintain and update `./docs/design-guideline.md` docs if needed.

package/.opencode/command/design/good.md

@@ -1,21 +0,0 @@
----
-description: Create an immersive design
----
-
-Think hard to plan & start working on these tasks follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules: 
-<tasks>$ARGUMENTS</tasks>
-
-## Workflow:
-1. Use `ui-ux-designer` subagent and multiple `researcher` subagents in parallel to create a design plan with TODO tasks in `./plans` directory.
-2. Then use `ui-ux-designer` subagent to implement the plan step by step.
-3. If user doesn't specify, create the design in pure HTML/CSS/JS.
-4. Report back to user with a summary of the changes and explain everything briefly, ask user to review the changes and approve them.
-5. If user approves the changes, update the `./docs/design-guideline.md` docs if needed.
-
-## Important Notes:
-- **ALWAYS REMEBER that you have the skills of a top-tier UI/UX Designer who won a lot of awards on Dribbble, Behance, Awwwards, Mobbin, TheFWA.**
-- Remember that you have the capability to generate images, videos, edit images, etc. with Human MCP Server tools. Use them to create the design with real assets.
-- Always review, analyze and double check the generated assets with eyes tools of Human MCP Server.
-- Use removal background tools to remove background from generated assets if needed.
-- Create storytelling designs, immersive 3D experiences, micro-interactions, and interactive interfaces.
-- Maintain and update `./docs/design-guideline.md` docs if needed.

package/.opencode/command/design/screenshot.md

@@ -1,22 +0,0 @@
----
-description: Create a design based on screenshot
----
-
-Think hard to plan & start designing follow exactly this screenshot: 
-<screenshot>$ARGUMENTS</screenshot>
-
-## Workflow:
-1. Use `eyes` analyze tool to describe super details of the screenshot.
-2. Use `ui-ux-designer` subagent to create a design plan of creating exactly the same result with the screenshot, break down the plan into TODO tasks in `./plans` directory.
-3. Then implement the plan step by step.
-4. If user doesn't specify, create the design in pure HTML/CSS/JS.
-5. Report back to user with a summary of the changes and explain everything briefly, ask user to review the changes and approve them.
-6. If user approves the changes, update the `./docs/design-guideline.md` docs if needed.
-
-## Important Notes:
-- **ALWAYS REMEBER that you have the skills of a top-tier UI/UX Designer who won a lot of awards on Dribbble, Behance, Awwwards, Mobbin, TheFWA.**
-- Remember that you have the capability to generate images, videos, edit images, etc. with Human MCP Server tools. Use them to create the design with real assets.
-- Always review, analyze and double check the generated assets with eyes tools of Human MCP Server.
-- Use removal background tools to remove background from generated assets if needed.
-- Create storytelling designs, immersive 3D experiences, micro-interactions, and interactive interfaces.
-- Maintain and update `./docs/design-guideline.md` docs if needed.

package/.opencode/command/design/video.md

@@ -1,22 +0,0 @@
----
-description: Create a design based on video
----
-
-Think hard to plan & start designing follow exactly this video: 
-<video>$ARGUMENTS</video>
-
-## Workflow:
-1. Use `eyes` analyze tool to describe super details of the video: be specific about describing every element, every interaction, every animation, every transition, every color, every font, every spacing, every size, every shape, every texture, every material, every light, every shadow, every reflection, every refraction, every blur, every glow, every reflection, every refraction, every blur, every glow, every reflection, every refraction, every blur, every glow, every image.
-2. Use `ui-ux-designer` subagent to create a design plan of creating exactly the same result with the video, break down the plan into TODO tasks in `./plans` directory.
-3. Then implement the plan step by step.
-4. If user doesn't specify, create the design in pure HTML/CSS/JS.
-5. Report back to user with a summary of the changes and explain everything briefly, ask user to review the changes and approve them.
-6. If user approves the changes, update the `./docs/design-guideline.md` docs if needed.
-
-## Important Notes:
-- **ALWAYS REMEBER that you have the skills of a top-tier UI/UX Designer who won a lot of awards on Dribbble, Behance, Awwwards, Mobbin, TheFWA.**
-- Remember that you have the capability to generate images, videos, edit images, etc. with Human MCP Server tools. Use them to create the design with real assets.
-- Always review, analyze and double check the generated assets with eyes tools of Human MCP Server.
-- Use removal background tools to remove background from generated assets if needed.
-- Create storytelling designs, immersive 3D experiences, micro-interactions, and interactive interfaces.
-- Maintain and update `./docs/design-guideline.md` docs if needed.

package/.opencode/command/fix/ci.md

@@ -1,8 +0,0 @@
----
-description: Analyze Github Actions logs and fix issues
----
-## Github Actions URL
- $ARGUMENTS
-
-Use the `planer-researcher` to read the github actions logs, analyze and find the root causes of the issues, then provide a detailed plan for implementing the fixes.
-Then use proper developer agents to implement the plan.

package/.opencode/command/fix/fast.md

@@ -1,11 +0,0 @@
----
-description: Analyze and fix the issue [FAST]
----
-
-Analyze and fix this issue:
-<issue>$ARGUMENTS</issue>
-
-## Development Rules
-
-- Use `tester` agent to test the fix and make sure it works, then report back to main agent.
-- If there are issues or failed tests, ask main agent to fix all of them and repeat the process until all tests pass.

package/.opencode/command/fix/hard.md

@@ -1,15 +0,0 @@
----
-description: Use subagents to plan and fix hard issues
----
-
-Think hard to plan & start fixing these issues follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules: 
-<issues>$ARGUMENTS</issues>
-
-## Workflow:
-1. Use `planner` subagent and `researcher` subagent to create a implementation plan with TODO tasks in `./plans` directory.
-2. Then use general agent (main agent) to implement the plan step by step.
-3. Use `tester` subagent to run the tests, make sure it works, then report back to main agent.
-4. If there are issues or failed tests, use `debugger` subagent to find the root cause of the issues, then ask main agent to fix all of them and 
-5. Repeat the process until all tests pass or no more issues are reported.
-6. After finishing, delegate to `code-reviewer` subagent to review code. If there are critical issues, ask main agent to improve the code and test everything again.
-7. Report back to user with a summary of the changes and explain everything briefly.

package/.opencode/command/fix/logs.md

@@ -1,16 +0,0 @@
----
-description: Analyze logs and fix issues
----
-
-Use `debugger` agent to analyze the `./logs.txt` file, identify root causes of any errors or issues and respond with a report and solution.
-So the main agent can fix them.
-
-## Rules
-
-- Use `debugger` agent to read and analyze the entire `./logs.txt` file
-- Identify all errors, warnings, and potential issues
-- Determine the root causes of each issue
-- Fix all identified problems systematically based on the report
-- Verify fixes by running appropriate commands
-- Re-analyze logs after fixes to ensure issues are resolved
-

package/.opencode/command/fix/test.md

@@ -1,18 +0,0 @@
----
-description: Run test suite and fix issues
----
-
-## Reported Issues:
-<issue>
- $ARGUMENTS
-</issue>
-
-## Workflow:
-1. First use `tester` subagent to compile the code and fix all syntax errors if any.
-2. Then use `tester` subagent to run the tests.
-3. If there are issues or failed tests, use `debugger` subagent to find the root cause of the issues.
-4. Then use `planner` subagent to create a implementation plan with TODO tasks in `./plans` directory.
-5. Then implement the plan step by step.
-6. Use `tester` subagent to run the tests after implementing the plan, make sure it works, then report back to main agent.
-7. After finishing, delegate to `code-reviewer` agent to review code. If there are critical issues, ask main agent to improve the code and test everything again.
-8. Repeat this process until all tests pass and no more errors are reported.

package/.opencode/command/fix/types.md

@@ -1,10 +0,0 @@
----
-description: Fix type errors
----
-
-Run `bun run typecheck` and fix all type errors.
-
-## Rules
-
-- Fix all of type errors and repeat the process until there are no more type errors.
-- Do not use `any` just to pass the type check.

package/.opencode/command/git/cm.md

@@ -1,5 +0,0 @@
----
-description: Stage all files and create a commit.
----
-Use `git-manager` agent to stage all files and create a commit.
-**IMPORTANT: DO NOT push the changes to remote repository**

package/.opencode/command/git/cp.md

@@ -1,4 +0,0 @@
----
-description: Stage, commit and push all code in the current branch
----
-Use `git-manager` agent to stage all files, create a meaningful commit based on the changes and push to remote repository.

package/.opencode/command/plan/ci.md

@@ -1,12 +0,0 @@
----
-description: Analyze Github Actions logs and provide a plan to fix the issues
----
-## Github Actions URL
- $ARGUMENTS
-
-Use the `planer-researcher` to read the github actions logs, analyze and find the root causes of the issues, then provide a detailed plan for implementing the fixes.
-
-**Output:**
-Provide at least 2 implementation approaches with clear trade-offs, and explain the pros and cons of each approach, and provide a recommended approach.
-
-**IMPORTANT:** Ask the user for confirmation before implementing.

package/.opencode/command/plan/two.md

@@ -1,13 +0,0 @@
----
-description: Research & create an implementation plan with 2 approaches
----
-
-Use the `planner` subagent to plan for this task:
-<task>
- $ARGUMENTS
-</task>
-
-**Output:**
-Provide at least 2 implementation approaches with clear trade-offs, and explain the pros and cons of each approach, and provide a recommended approach.
-
-**IMPORTANT**: **Do not** start implementing.

package/.opencode/command/plan.md

@@ -1,10 +0,0 @@
----
-description: Research, analyze, and create an implementation plan
----
-
-Use the `planner` subagent to plan for this task:
-<task>
- $ARGUMENTS
-</task>
-
-**IMPORTANT**: **Do not** start implementing.

package/.opencode/command/test.md

@@ -1,7 +0,0 @@
----
-description: Debugging technical issues and providing solutions.
----
-
-Use the `tester` subagent to run tests locally and analyze the summary report.
-
-**IMPORTANT**: **Do not** start implementing.

package/.opencode/command/watzup.md

@@ -1,8 +0,0 @@
----
-description: Review recent changes and wrap up the work
----
-Review my current branch and the most recent commits. 
-Provide a detailed summary of all changes, including what was modified, added, or removed. 
-Analyze the overall impact and quality of the changes.
-
-**IMPORTANT**: **Do not** start implementing.