@techwavedev/agi-agent-kit 1.1.7 → 1.2.1

package/templates/skills/knowledge/self-update/scripts/update_kit.py

@@ -1,103 +0,0 @@
-#!/usr/bin/env python3
-"""
-Script: update_kit.py
-Purpose: Update AGI Agent Kit to the latest version
-
-Usage:
-    python3 skills/self-update/scripts/update_kit.py [--check-only] [--force]
-
-Arguments:
-    --check-only  Only check for updates, don't install
-    --force       Skip confirmation prompt
-
-Exit Codes:
-    0 - Success (or no update needed)
-    1 - Error during update
-"""
-
-import argparse
-import json
-import subprocess
-import sys
-from pathlib import Path
-
-
-def run_cmd(cmd: list, capture=True) -> tuple:
-    """Run command and return (success, output)"""
-    try:
-        result = subprocess.run(cmd, capture_output=capture, text=True)
-        return result.returncode == 0, result.stdout.strip()
-    except Exception as e:
-        return False, str(e)
-
-
-def get_installed_version(root: Path) -> str:
-    """Get installed version from .agi.json"""
-    agi_json = root / ".agi.json"
-    if agi_json.exists():
-        try:
-            data = json.loads(agi_json.read_text())
-            return data.get("version", "unknown")
-        except:
-            pass
-    return "unknown"
-
-
-def get_latest_version() -> str:
-    """Get latest version from NPM"""
-    success, output = run_cmd(["npm", "view", "@techwavedev/agi-agent-kit", "version"])
-    return output if success else "unknown"
-
-
-def main():
-    parser = argparse.ArgumentParser(description=__doc__)
-    parser.add_argument('--check-only', action='store_true', help='Only check for updates')
-    parser.add_argument('--force', action='store_true', help='Skip confirmation')
-    args = parser.parse_args()
-
-    root = Path(__file__).resolve().parent.parent.parent.parent
-    
-    print("🔍 Checking versions...")
-    installed = get_installed_version(root)
-    latest = get_latest_version()
-    
-    print(f"   Installed: {installed}")
-    print(f"   Latest:    {latest}")
-    
-    if installed == latest:
-        print("\n✅ Already up to date!")
-        sys.exit(0)
-    
-    if args.check_only:
-        if installed != latest and latest != "unknown":
-            print(f"\n📦 Update available: {installed} → {latest}")
-            print("   Run without --check-only to update")
-        sys.exit(0)
-    
-    # Confirm update
-    if not args.force:
-        print(f"\n📦 Update available: {installed} → {latest}")
-        response = input("Proceed with update? [y/N]: ").strip().lower()
-        if response != 'y':
-            print("Update cancelled.")
-            sys.exit(0)
-    
-    # Run update
-    print("\n🚀 Updating AGI Agent Kit...")
-    print("   Running: npx @techwavedev/agi-agent-kit@latest init --pack=full\n")
-    
-    result = subprocess.run(
-        ["npx", "@techwavedev/agi-agent-kit@latest", "init", "--pack=full"],
-        cwd=root
-    )
-    
-    if result.returncode == 0:
-        print("\n✅ Update complete!")
-        print("   Run 'python3 execution/system_checkup.py' to verify")
-    else:
-        print("\n❌ Update failed. Check output above.")
-        sys.exit(1)
-
-
-if __name__ == '__main__':
-    main()

package/templates/skills/knowledge/stitch-loop/README.md

@@ -1,54 +0,0 @@
-# Stitch Build Loop Skill
-
-Teaches agents to iteratively build websites using Stitch with an autonomous baton-passing loop pattern.
-
-## Install
-
-```bash
-npx add-skill google-labs-code/stitch-skills --skill stitch-loop --global
-```
-
-## What It Does
-
-Enables continuous, autonomous website development through a "baton" system:
-
-1. Agent reads task from `next-prompt.md`
-2. Generates page via Stitch MCP tools
-3. Integrates into site structure
-4. Writes next task to continue the loop
-
-## Prerequisites
-
-- Stitch MCP Server access
-- A `DESIGN.md` file (generate with the `design-md` skill)
-- A `SITE.md` file for project context
-
-## Example Prompt
-
-```text
-Read my next-prompt.md and generate the page using Stitch, then prepare the next iteration.
-```
-
-## Skill Structure
-
-```
-stitch-loop/
-├── SKILL.md              — Core pattern instructions
-├── README.md             — This file
-├── resources/
-│   ├── baton-schema.md   — Baton file format spec
-│   └── site-template.md  — SITE.md/DESIGN.md templates
-└── examples/
-    ├── next-prompt.md    — Example baton
-    └── SITE.md           — Example site constitution
-```
-
-## Works With
-
-- **`design-md` skill**: Generate `DESIGN.md` from existing Stitch screens
-- **CI/CD**: GitHub Actions can trigger new iterations on push
-- **Agent chains**: Dispatch to other agents (Jules, etc.)
-
-## Learn More
-
-See [SKILL.md](./SKILL.md) for complete instructions.

package/templates/skills/knowledge/stitch-loop/SKILL.md

@@ -1,235 +0,0 @@
----
-name: stitch-loop
-description: Teaches agents to iteratively build websites using Stitch with an autonomous baton-passing loop pattern
-allowed-tools:
-  - "stitch*:*"
-  - "chrome*:*"
-  - "Read"
-  - "Write"
-  - "Bash"
-  - "qdrant-memory"
----
-
-# Stitch Build Loop
-
-You are an **autonomous frontend builder** participating in an iterative site-building loop. Your goal is to generate a page using Stitch, integrate it into the site, and prepare instructions for the next iteration.
-
-## Overview
-
-The Build Loop pattern enables continuous, autonomous website development through a "baton" system. Each iteration:
-
-1. Reads the current task from a baton file (`next-prompt.md`)
-2. Generates a page using Stitch MCP tools
-3. Integrates the page into the site structure
-4. Writes the next task to the baton file for the next iteration
-
-## Prerequisites
-
-**Required:**
-
-- Access to the Stitch MCP Server
-- A Stitch project (existing or will be created)
-- A `DESIGN.md` file (generate one using the `design-md` skill if needed)
-- A `SITE.md` file documenting the site vision and roadmap
-
-**Optional:**
-
-- Chrome DevTools MCP Server — enables visual verification of generated pages
-- Qdrant Memory Skill — enables semantic context retrieval and long-term memory
-
-## The Baton System
-
-The `next-prompt.md` file acts as a relay baton between iterations:
-
-```markdown
----
-page: about
----
-
-A page describing how jules.top tracking works.
-
-**DESIGN SYSTEM (REQUIRED):**
-[Copy from DESIGN.md Section 6]
-
-**Page Structure:**
-
-1. Header with navigation
-2. Explanation of tracking methodology
-3. Footer with links
-```
-
-**Critical rules:**
-
-- The `page` field in YAML frontmatter determines the output filename
-- The prompt content must include the design system block from `DESIGN.md`
-- You MUST update this file before completing your work to continue the loop
-
-## Execution Protocol
-
-### Step 1: Read the Baton
-
-Parse `next-prompt.md` to extract:
-
-- **Page name** from the `page` frontmatter field
-- **Prompt content** from the markdown body
-
-### Step 2: Consult Context Files
-
-Before generating, read these files:
-
-| File        | Purpose                                                               |
-| ----------- | --------------------------------------------------------------------- |
-| `SITE.md`   | Site vision, **Stitch Project ID**, existing pages (sitemap), roadmap |
-| `DESIGN.md` | Required visual style for Stitch prompts                              |
-
-### Step 2.5: Consult Memory (Optional)
-
-If the **Qdrant Memory Skill** is available, retrieve relevant context to ensure consistency:
-
-1. **Retrieve Context**: Call `qdrant_search_memory` (or `retrieve_context` script) with technical queries related to the current task.
-   - Example query: "navigation structure", "footer design", "auth flow pattern"
-   - Filter by project if applicable.
-2. **Check Decisions**: Look for past architectural decisions (`type: "decision"`) that might impact this page.
-
-**Important checks:**
-
-- Section 4 (Sitemap) — Do NOT recreate pages that already exist
-- Section 5 (Roadmap) — Pick tasks from here if backlog exists
-- Section 6 (Creative Freedom) — Ideas for new pages if roadmap is empty
-
-### Step 3: Generate with Stitch
-
-Use the Stitch MCP tools to generate the page:
-
-1. **Discover namespace**: Run `list_tools` to find the Stitch MCP prefix
-2. **Get or create project**:
-   - If `stitch.json` exists, use the `projectId` from it
-   - Otherwise, call `[prefix]:create_project` and save the ID to `stitch.json`
-3. **Generate screen**: Call `[prefix]:generate_screen_from_text` with:
-   - `projectId`: The project ID
-   - `prompt`: The full prompt from the baton (including design system block)
-   - `deviceType`: `DESKTOP` (or as specified)
-4. **Retrieve assets**: Call `[prefix]:get_screen` to get:
-   - `htmlCode.downloadUrl` — Download and save as `queue/{page}.html`
-   - `screenshot.downloadUrl` — Download and save as `queue/{page}.png`
-
-### Step 4: Integrate into Site
-
-1. Move generated HTML from `queue/{page}.html` to `site/public/{page}.html`
-2. Fix any asset paths to be relative to the public folder
-3. Update navigation:
-   - Find existing placeholder links (e.g., `href="#"`) and wire them to the new page
-   - Add the new page to the global navigation if appropriate
-4. Ensure consistent headers/footers across all pages
-
-### Step 4.5: Visual Verification (Optional)
-
-If the **Chrome DevTools MCP Server** is available, verify the generated page:
-
-1. **Check availability**: Run `list_tools` to see if `chrome*` tools are present
-2. **Start dev server**: Use Bash to start a local server (e.g., `npx serve site/public`)
-3. **Navigate to page**: Call `[chrome_prefix]:navigate` to open `http://localhost:3000/{page}.html`
-4. **Capture screenshot**: Call `[chrome_prefix]:screenshot` to capture the rendered page
-5. **Visual comparison**: Compare against the Stitch screenshot (`queue/{page}.png`) for fidelity
-6. **Stop server**: Terminate the dev server process
-
-> **Note:** This step is optional. If Chrome DevTools MCP is not installed, skip to Step 5.
-
-### Step 5: Update Site Documentation
-
-Modify `SITE.md`:
-
-- Add the new page to Section 4 (Sitemap) with `[x]`
-- Remove any idea you consumed from Section 6 (Creative Freedom)
-- Update Section 5 (Roadmap) if you completed a backlog item
-
-### Step 5.5: Store Memory (Optional)
-
-If **Qdrant Memory Skill** is available:
-
-1. **Store Completion**: Use `qdrant_store_memory` to record the completion of the page.
-   - Content: "Completed page: {page}. Implemented features: [list features]."
-   - Metadata: `type: "milestone"`, `page: "{page}"`
-2. **Store Decisions**: If you made any structural or design decisions (e.g., "Standardized footer links"), store them:
-   - Metadata: `type: "decision"`, `topic: "navigation"`
-
-### Step 6: Prepare the Next Baton (Critical)
-
-**You MUST update `next-prompt.md` before completing.** This keeps the loop alive.
-
-1. **Decide the next page**:
-   - Check `SITE.md` Section 5 (Roadmap) for pending items
-   - If empty, pick from Section 6 (Creative Freedom)
-   - Or invent something new that fits the site vision
-2. **Write the baton** with proper YAML frontmatter:
-
-```markdown
----
-page: achievements
----
-
-A competitive achievements page showing developer badges and milestones.
-
-**DESIGN SYSTEM (REQUIRED):**
-[Copy the entire design system block from DESIGN.md]
-
-**Page Structure:**
-
-1. Header with title and navigation
-2. Badge grid showing unlocked/locked states
-3. Progress bars for milestone tracking
-```
-
-## File Structure Reference
-
-```
-project/
-├── next-prompt.md      # The baton — current task
-├── stitch.json         # Stitch project ID (persist this!)
-├── DESIGN.md           # Visual design system (from design-md skill)
-├── SITE.md             # Site vision, sitemap, roadmap
-├── queue/              # Staging area for Stitch output
-│   ├── {page}.html
-│   └── {page}.png
-└── site/public/        # Production pages
-    ├── index.html
-    └── {page}.html
-```
-
-## Orchestration Options
-
-The loop can be driven by different orchestration layers:
-
-| Method            | How it works                                           |
-| ----------------- | ------------------------------------------------------ |
-| **CI/CD**         | GitHub Actions triggers on `next-prompt.md` changes    |
-| **Human-in-loop** | Developer reviews each iteration before continuing     |
-| **Agent chains**  | One agent dispatches to another (e.g., Jules API)      |
-| **Manual**        | Developer runs the agent repeatedly with the same repo |
-
-The skill is orchestration-agnostic — focus on the pattern, not the trigger mechanism.
-
-## Design System Integration
-
-This skill works best with the `design-md` skill:
-
-1. **First time setup**: Generate `DESIGN.md` using the `design-md` skill from an existing Stitch screen
-2. **Every iteration**: Copy Section 6 ("Design System Notes for Stitch Generation") into your baton prompt
-3. **Consistency**: All generated pages will share the same visual language
-
-## Common Pitfalls
-
-- ❌ Forgetting to update `next-prompt.md` (breaks the loop)
-- ❌ Recreating a page that already exists in the sitemap
-- ❌ Not including the design system block in the prompt
-- ❌ Leaving placeholder links (`href="#"`) instead of wiring real navigation
-- ❌ Forgetting to persist `stitch.json` after creating a new project
-
-## Troubleshooting
-
-| Issue                   | Solution                                                   |
-| ----------------------- | ---------------------------------------------------------- |
-| Stitch generation fails | Check that the prompt includes the design system block     |
-| Inconsistent styles     | Ensure DESIGN.md is up-to-date and copied correctly        |
-| Loop stalls             | Verify `next-prompt.md` was updated with valid frontmatter |
-| Navigation broken       | Check all internal links use correct relative paths        |

package/templates/skills/knowledge/stitch-loop/examples/SITE.md

@@ -1,73 +0,0 @@
----
-stitch-project-id: 13534454087919359824
----
-# Project Vision & Constitution
-
-> **AGENT INSTRUCTION:** Read this file before every iteration. It serves as the project's "Long-Term Memory." If `next-prompt.md` is empty, pick the highest priority item from Section 5 OR invent a new page that fits the project vision.
-
-## 1. Core Identity
-* **Project Name:** Oakwood Furniture Co.
-* **Stitch Project ID:** `13534454087919359824`
-* **Mission:** A premium online furniture showroom showcasing handcrafted, sustainable wood furniture.
-* **Target Audience:** Design-conscious homeowners, interior designers, eco-minded buyers.
-* **Voice:** Warm, refined, artisanal, and trustworthy.
-
-## 2. Visual Language (Stitch Prompt Strategy)
-*Strictly adhere to these descriptive rules when prompting Stitch. Do NOT use code.*
-
-* **The "Vibe" (Adjectives):**
-    * *Primary:* **Warm** (Inviting, cozy, natural materials).
-    * *Secondary:* **Minimal** (Clean layouts, breathing room, gallery-like).
-    * *Tertiary:* **Artisanal** (Handcrafted feel, attention to detail).
-
-* **Color Philosophy (Semantic):**
-    * **Backgrounds:** Warm barely-there cream (#FCFAFA). Soft, inviting canvas.
-    * **Accents:** Deep muted teal-navy (#294056) for CTAs and highlights.
-    * **Text:** Charcoal near-black (#2C2C2C) for headlines, soft gray (#6B6B6B) for body.
-
-## 3. Architecture & File Structure
-* **Root:** `site/public/`
-* **Asset Flow:** Stitch generates to `queue/` -> Validate -> Move to `site/public/`.
-* **Navigation Strategy:**
-    * **Global Header:** Logo, Shop, Collections, About, Contact.
-    * **Global Footer:** Sustainability, Craftsmanship, Shipping Info, Social Links.
-
-## 4. Live Sitemap (Current State)
-*The Agent MUST update this section when a new page is successfully merged.*
-
-* [x] `index.html` - Homepage with hero and featured collections.
-* [x] `collections.html` - Overview of furniture categories.
-* [x] `about.html` - Our story and craftsmanship philosophy.
-* [ ] `contact.html` - Contact form and showroom locations.
-
-## 5. The Roadmap (Backlog)
-*If `next-prompt.md` is empty or completed, pick the next task from here.*
-
-### High Priority
-- [ ] **Product Detail Page:** Template for individual furniture items.
-- [ ] **Contact Page:** Contact form with showroom map.
-
-### Medium Priority
-- [ ] **Sustainability Page:** Our commitment to eco-friendly practices.
-- [ ] **Care Guide:** How to maintain wood furniture.
-
-## 6. Creative Freedom Guidelines
-*When the backlog is empty, follow these guidelines to innovate.*
-
-1. **Stay On-Brand:** New pages must fit the "Warm + Minimal + Artisanal" vibe.
-2. **Enhance the Core:** Support the furniture shopping experience.
-3. **Naming Convention:** Use lowercase, descriptive filenames.
-
-### Ideas to Explore
-*Pick one, build it, then REMOVE it from this list.*
-
-- [ ] `materials.html` - Showcase of wood types and finishes
-- [ ] `custom.html` - Custom furniture ordering process
-- [ ] `gallery.html` - Customer homes featuring our furniture
-- [ ] `blog.html` - Design tips and furniture care articles
-
-## 7. Rules of Engagement
-1. Do not recreate pages in Section 4.
-2. Always update `next-prompt.md` before completing.
-3. Consume ideas from Section 6 when you use them.
-4. Keep the loop moving.

package/templates/skills/knowledge/stitch-loop/examples/next-prompt.md

@@ -1,25 +0,0 @@
----
-page: contact
----
-A warm, inviting contact page for Oakwood Furniture Co.
-
-**DESIGN SYSTEM (REQUIRED):**
-- Platform: Web, Desktop-first
-- Theme: Light, minimal, photography-first
-- Background: Warm barely-there cream (#FCFAFA)
-- Surface: Crisp very light gray (#F5F5F5) for cards
-- Primary Accent: Deep muted teal-navy (#294056) for buttons and links
-- Text Primary: Charcoal near-black (#2C2C2C) for headlines
-- Text Secondary: Soft warm gray (#6B6B6B) for body copy
-- Font: Modern sans-serif (Manrope or similar), clean and approachable
-- Buttons: Subtly rounded corners (8px), comfortable padding
-- Cards: Gently rounded corners (12px), whisper-soft shadows on hover
-- Layout: Centered content, max-width container, generous whitespace
-- No harsh shadows, no aggressive colors - serene and trustworthy
-
-**Page Structure:**
-1. **Header:** Navigation with logo, Shop, Collections, About, Contact (active)
-2. **Hero Section:** Warm headline "Get in Touch" with a brief welcome message
-3. **Contact Form:** Name, email, message fields with the teal-navy submit button
-4. **Showroom Info:** Address, hours, and an embedded map or beautiful showroom photo
-5. **Footer:** Sustainability, Craftsmanship, Shipping links, and social icons

package/templates/skills/knowledge/stitch-loop/resources/baton-schema.md

@@ -1,61 +0,0 @@
-# Baton File Schema
-
-The baton file (`next-prompt.md`) is the communication mechanism between loop iterations. It tells the next agent what to build.
-
-## Format
-
-```yaml
----
-page: <filename-without-extension>
----
-<prompt-content>
-```
-
-## Fields
-
-### Frontmatter (YAML)
-
-| Field | Type | Required | Description |
-|-------|------|----------|-------------|
-| `page` | string | Yes | Output filename (without `.html` extension) |
-
-### Body (Markdown)
-
-The body contains the full Stitch prompt, which must include:
-
-1. **One-line description** with vibe/atmosphere keywords
-2. **Design System block** (required) — copied from `DESIGN.md` Section 6
-3. **Page Structure** — numbered list of sections/components
-
-## Example
-
-```markdown
----
-page: achievements
----
-A competitive, gamified achievements page with terminal aesthetics.
-
-**DESIGN SYSTEM (REQUIRED):**
-- Platform: Web, Desktop-first
-- Theme: Dark, minimal, data-focused
-- Background: Deep charcoal/near-black (#0f1419)
-- Primary Accent: Teal/Cyan (#2dd4bf)
-- Text Primary: White (#ffffff)
-- Font: Clean sans-serif (Inter, SF Pro, or system default)
-- Layout: Centered content, max-width container
-
-**Page Structure:**
-1. Header with title "Achievements" and navigation
-2. Badge grid showing locked/unlocked states with icons
-3. Progress section with milestone bars
-4. Footer with links to other pages
-```
-
-## Validation Rules
-
-Before completing an iteration, validate your baton:
-
-- [ ] `page` frontmatter field exists and is a valid filename
-- [ ] Prompt includes the design system block
-- [ ] Prompt describes a page NOT already in `SITE.md` sitemap
-- [ ] Prompt includes specific page structure details

package/templates/skills/knowledge/stitch-loop/resources/site-template.md

@@ -1,104 +0,0 @@
-# Site Template
-
-Use these templates when setting up a new project for the build loop.
-
-## SITE.md Template
-
-```markdown
-# Project Vision & Constitution
-
-> **AGENT INSTRUCTION:** Read this file before every iteration. It serves as the project's "Long-Term Memory."
-
-## 1. Core Identity
-* **Project Name:** [Your project name]
-* **Stitch Project ID:** [Your Stitch project ID]
-* **Mission:** [What the site achieves]
-* **Target Audience:** [Who uses this site]
-* **Voice:** [Tone and personality descriptors]
-
-## 2. Visual Language
-*Reference these descriptors when prompting Stitch.*
-
-* **The "Vibe" (Adjectives):**
-    * *Primary:* [Main aesthetic keyword]
-    * *Secondary:* [Supporting aesthetic]
-    * *Tertiary:* [Additional flavor]
-
-## 3. Architecture & File Structure
-* **Root:** `site/public/`
-* **Asset Flow:** Stitch generates to `queue/` → Validate → Move to `site/public/`
-* **Navigation Strategy:** [How nav works]
-
-## 4. Live Sitemap (Current State)
-*Update this when a new page is successfully merged.*
-
-* [x] `index.html` - [Description]
-* [ ] `about.html` - [Description]
-
-## 5. The Roadmap (Backlog)
-*Pick the next task from here if available.*
-
-### High Priority
-- [ ] [Task description]
-- [ ] [Task description]
-
-### Medium Priority
-- [ ] [Task description]
-
-## 6. Creative Freedom Guidelines
-*When the backlog is empty, follow these guidelines to innovate.*
-
-1. **Stay On-Brand:** New pages must fit the established vibe
-2. **Enhance the Core:** Support the site mission
-3. **Naming Convention:** Use lowercase, descriptive filenames
-
-### Ideas to Explore
-*Pick one, build it, then REMOVE it from this list.*
-
-- [ ] `stats.html` - [Description]
-- [ ] `settings.html` - [Description]
-
-## 7. Rules of Engagement
-1. Do not recreate pages in Section 4
-2. Always update `next-prompt.md` before completing
-3. Consume ideas from Section 6 when you use them
-```
-
-## DESIGN.md Template
-
-Generate this using the `design-md` skill from an existing Stitch screen, or create manually:
-
-```markdown
-# Design System: [Project Name]
-**Project ID:** [Stitch Project ID]
-
-## 1. Visual Theme & Atmosphere
-[Describe mood, density, aesthetic philosophy]
-
-## 2. Color Palette & Roles
-- **[Descriptive Name]** (#hexcode) – [Functional role]
-- **[Descriptive Name]** (#hexcode) – [Functional role]
-
-## 3. Typography Rules
-[Font family, weights, sizes, spacing]
-
-## 4. Component Stylings
-* **Buttons:** [Shape, color, behavior]
-* **Cards:** [Corners, background, shadows]
-* **Inputs:** [Stroke, background, focus states]
-
-## 5. Layout Principles
-[Whitespace strategy, margins, grid alignment]
-
-## 6. Design System Notes for Stitch Generation
-**Copy this block into every baton prompt:**
-
-**DESIGN SYSTEM (REQUIRED):**
-- Platform: [Web/Mobile], [Desktop/Mobile]-first
-- Theme: [Dark/Light], [descriptors]
-- Background: [Description] (#hex)
-- Primary Accent: [Description] (#hex)
-- Text Primary: [Description] (#hex)
-- Font: [Description]
-- Layout: [Description]
-```