npm - codehava-agent-kit - Versions diffs - 1.0.1 → 3.0.0 - Mend

codehava-agent-kit 1.0.1 → 3.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (1164) hide show

package/templates/.agent/skills/3d-web-experience/SKILL.md ADDED Viewed

@@ -0,0 +1,259 @@
+---
+name: 3d-web-experience
+description: "You bring the third dimension to the web. You know when 3D enhances and when it's just showing off. You balance visual impact with performance. You make 3D accessible to users who've never touched a 3D app. You create moments of wonder without sacrificing usability."
+risk: unknown
+source: "vibeship-spawner-skills (Apache 2.0)"
+date_added: "2026-02-27"
+---
+# 3D Web Experience
+**Role**: 3D Web Experience Architect
+You bring the third dimension to the web. You know when 3D enhances
+and when it's just showing off. You balance visual impact with
+performance. You make 3D accessible to users who've never touched
+a 3D app. You create moments of wonder without sacrificing usability.
+## Capabilities
+- Three.js implementation
+- React Three Fiber
+- WebGL optimization
+- 3D model integration
+- Spline workflows
+- 3D product configurators
+- Interactive 3D scenes
+- 3D performance optimization
+## Patterns
+### 3D Stack Selection
+Choosing the right 3D approach
+**When to use**: When starting a 3D web project
+```python
+## 3D Stack Selection
+### Options Comparison
+| Tool | Best For | Learning Curve | Control |
+|------|----------|----------------|---------|
+| Spline | Quick prototypes, designers | Low | Medium |
+| React Three Fiber | React apps, complex scenes | Medium | High |
+| Three.js vanilla | Max control, non-React | High | Maximum |
+| Babylon.js | Games, heavy 3D | High | Maximum |
+### Decision Tree
+```
+Need quick 3D element?
+└── Yes → Spline
+└── No → Continue
+Using React?
+└── Yes → React Three Fiber
+└── No → Continue
+Need max performance/control?
+└── Yes → Three.js vanilla
+└── No → Spline or R3F
+```
+### Spline (Fastest Start)
+```jsx
+import Spline from '@splinetool/react-spline';
+export default function Scene() {
+  return (
+    <Spline scene="https://prod.spline.design/xxx/scene.splinecode" />
+  );
+}
+```
+### React Three Fiber
+```jsx
+import { Canvas } from '@react-three/fiber';
+import { OrbitControls, useGLTF } from '@react-three/drei';
+function Model() {
+  const { scene } = useGLTF('/model.glb');
+  return <primitive object={scene} />;
+}
+export default function Scene() {
+  return (
+    <Canvas>
+      <ambientLight />
+      <Model />
+      <OrbitControls />
+    </Canvas>
+  );
+}
+```
+```
+### 3D Model Pipeline
+Getting models web-ready
+**When to use**: When preparing 3D assets
+```python
+## 3D Model Pipeline
+### Format Selection
+| Format | Use Case | Size |
+|--------|----------|------|
+| GLB/GLTF | Standard web 3D | Smallest |
+| FBX | From 3D software | Large |
+| OBJ | Simple meshes | Medium |
+| USDZ | Apple AR | Medium |
+### Optimization Pipeline
+```
+1. Model in Blender/etc
+2. Reduce poly count (< 100K for web)
+3. Bake textures (combine materials)
+4. Export as GLB
+5. Compress with gltf-transform
+6. Test file size (< 5MB ideal)
+```
+### GLTF Compression
+```bash
+# Install gltf-transform
+npm install -g @gltf-transform/cli
+# Compress model
+gltf-transform optimize input.glb output.glb \
+  --compress draco \
+  --texture-compress webp
+```
+### Loading in R3F
+```jsx
+import { useGLTF, useProgress, Html } from '@react-three/drei';
+import { Suspense } from 'react';
+function Loader() {
+  const { progress } = useProgress();
+  return <Html center>{progress.toFixed(0)}%</Html>;
+}
+export default function Scene() {
+  return (
+    <Canvas>
+      <Suspense fallback={<Loader />}>
+        <Model />
+      </Suspense>
+    </Canvas>
+  );
+}
+```
+```
+### Scroll-Driven 3D
+3D that responds to scroll
+**When to use**: When integrating 3D with scroll
+```python
+## Scroll-Driven 3D
+### R3F + Scroll Controls
+```jsx
+import { ScrollControls, useScroll } from '@react-three/drei';
+import { useFrame } from '@react-three/fiber';
+function RotatingModel() {
+  const scroll = useScroll();
+  const ref = useRef();
+  useFrame(() => {
+    // Rotate based on scroll position
+    ref.current.rotation.y = scroll.offset * Math.PI * 2;
+  });
+  return <mesh ref={ref}>...</mesh>;
+}
+export default function Scene() {
+  return (
+    <Canvas>
+      <ScrollControls pages={3}>
+        <RotatingModel />
+      </ScrollControls>
+    </Canvas>
+  );
+}
+```
+### GSAP + Three.js
+```javascript
+import gsap from 'gsap';
+import ScrollTrigger from 'gsap/ScrollTrigger';
+gsap.to(camera.position, {
+  scrollTrigger: {
+    trigger: '.section',
+    scrub: true,
+  },
+  z: 5,
+  y: 2,
+});
+```
+### Common Scroll Effects
+- Camera movement through scene
+- Model rotation on scroll
+- Reveal/hide elements
+- Color/material changes
+- Exploded view animations
+```
+## Anti-Patterns
+### ❌ 3D For 3D's Sake
+**Why bad**: Slows down the site.
+Confuses users.
+Battery drain on mobile.
+Doesn't help conversion.
+**Instead**: 3D should serve a purpose.
+Product visualization = good.
+Random floating shapes = probably not.
+Ask: would an image work?
+### ❌ Desktop-Only 3D
+**Why bad**: Most traffic is mobile.
+Kills battery.
+Crashes on low-end devices.
+Frustrated users.
+**Instead**: Test on real mobile devices.
+Reduce quality on mobile.
+Provide static fallback.
+Consider disabling 3D on low-end.
+### ❌ No Loading State
+**Why bad**: Users think it's broken.
+High bounce rate.
+3D takes time to load.
+Bad first impression.
+**Instead**: Loading progress indicator.
+Skeleton/placeholder.
+Load 3D after page is interactive.
+Optimize model size.
+## Related Skills
+Works well with: `scroll-experience`, `interactive-portfolio`, `frontend`, `landing-page-design`
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/templates/.agent/skills/acceptance-orchestrator/SKILL.md ADDED Viewed

@@ -0,0 +1,106 @@
+---
+name: acceptance-orchestrator
+description: Use when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.
+risk: safe
+source: community
+date_added: "2026-03-12"
+---
+# Acceptance Orchestrator
+## Overview
+Orchestrate coding work as a state machine that ends only when acceptance criteria are verified with evidence or the task is explicitly escalated.
+Core rule: **do not optimize for "code changed"; optimize for "DoD proven".**
+## Required Sub-Skills
+- `create-issue-gate`
+- `closed-loop-delivery`
+- `verification-before-completion`
+Optional supporting skills:
+- `deploy-dev`
+- `pr-watch`
+- `pr-review-autopilot`
+- `git-ship`
+## Inputs
+Require these inputs:
+- issue id or issue body
+- issue status
+- acceptance criteria (DoD)
+- target environment (`dev` default)
+Fixed defaults:
+- max iteration rounds = `2`
+- PR review polling = `3m -> 6m -> 10m`
+## State Machine
+- `intake`
+- `issue-gated`
+- `executing`
+- `review-loop`
+- `deploy-verify`
+- `accepted`
+- `escalated`
+## Workflow
+1. **Intake**
+   - Read issue and extract task goal + DoD.
+2. **Issue gate**
+   - Use `create-issue-gate` logic.
+   - If issue is not `ready` or execution gate is not `allowed`, stop immediately.
+   - Do not implement anything while issue remains `draft`.
+3. **Execute**
+   - Hand off to `closed-loop-delivery` for implementation and local verification.
+4. **Review loop**
+   - If PR feedback is relevant, batch polling windows as:
+     - wait `3m`
+     - then `6m`
+     - then `10m`
+   - After the `10m` round, stop waiting and process all visible comments together.
+5. **Deploy and runtime verification**
+   - If DoD depends on runtime behavior, deploy only to `dev` by default.
+   - Verify with real logs/API/Lambda behavior, not assumptions.
+6. **Completion gate**
+   - Before any claim of completion, require `verification-before-completion`.
+   - No success claim without fresh evidence.
+## Stop Conditions
+Move to `accepted` only when every acceptance criterion has matching evidence.
+Move to `escalated` when any of these happen:
+- DoD still fails after `2` full rounds
+- missing secrets/permissions/external dependency blocks progress
+- task needs production action or destructive operation approval
+- review instructions conflict and cannot both be satisfied
+## Human Gates
+Always stop for human confirmation on:
+- prod/stage deploys beyond agreed scope
+- destructive git/data operations
+- billing or security posture changes
+- missing user-provided acceptance criteria
+## Output Contract
+When reporting status, always include:
+- `Status`: intake / executing / accepted / escalated
+- `Acceptance Criteria`: pass/fail checklist
+- `Evidence`: commands, logs, API results, or runtime proof
+- `Open Risks`: anything still uncertain
+- `Need Human Input`: smallest next decision, if blocked
+Do not report "done" unless status is `accepted`.

package/templates/.agent/skills/address-github-comments/SKILL.md ADDED Viewed

@@ -0,0 +1,61 @@
+---
+name: address-github-comments
+description: "Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI."
+risk: unknown
+source: community
+date_added: "2026-02-27"
+---
+# Address GitHub Comments
+## Overview
+Efficiently address PR review comments or issue feedback using the GitHub CLI (`gh`). This skill ensures all feedback is addressed systematically.
+## Prerequisites
+Ensure `gh` is authenticated.
+```bash
+gh auth status
+```
+If not logged in, run `gh auth login`.
+## Workflow
+### 1. Inspect Comments
+Fetch the comments for the current branch's PR.
+```bash
+gh pr view --comments
+```
+Or use a custom script if available to list threads.
+### 2. Categorize and Plan
+- List the comments and review threads.
+- Propose a fix for each.
+- **Wait for user confirmation** on which comments to address first if there are many.
+### 3. Apply Fixes
+Apply the code changes for the selected comments.
+### 4. Respond to Comments
+Once fixed, respond to the threads as resolved.
+```bash
+gh pr comment <PR_NUMBER> --body "Addressed in latest commit."
+```
+## Common Mistakes
+- **Applying fixes without understanding context**: Always read the surrounding code of a comment.
+- **Not verifying auth**: Check `gh auth status` before starting.
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.