@techwavedev/agi-agent-kit 1.3.5 → 1.4.2

package/templates/skills/extended/frontend/discord-bot-architect/SKILL.md

@@ -1,313 +0,0 @@
----
-name: discord-bot-architect
-description: "Specialized skill for building production-ready Discord bots. Covers Discord.js (JavaScript) and Pycord (Python), gateway intents, slash commands, interactive components, rate limiting, and sharding."
-source: vibeship-spawner-skills (Apache 2.0)
----
-
-# Discord Bot Architect
-
-## Patterns
-
-### Discord.js v14 Foundation
-
-Modern Discord bot setup with Discord.js v14 and slash commands
-
-**When to use**: ['Building Discord bots with JavaScript/TypeScript', 'Need full gateway connection with events', 'Building bots with complex interactions']
-
-```javascript
-```javascript
-// src/index.js
-const { Client, Collection, GatewayIntentBits, Events } = require('discord.js');
-const fs = require('node:fs');
-const path = require('node:path');
-require('dotenv').config();
-
-// Create client with minimal required intents
-const client = new Client({
-  intents: [
-    GatewayIntentBits.Guilds,
-    // Add only what you need:
-    // GatewayIntentBits.GuildMessages,
-    // GatewayIntentBits.MessageContent,  // PRIVILEGED - avoid if possible
-  ]
-});
-
-// Load commands
-client.commands = new Collection();
-const commandsPath = path.join(__dirname, 'commands');
-const commandFiles = fs.readdirSync(commandsPath).filter(f => f.endsWith('.js'));
-
-for (const file of commandFiles) {
-  const filePath = path.join(commandsPath, file);
-  const command = require(filePath);
-  if ('data' in command && 'execute' in command) {
-    client.commands.set(command.data.name, command);
-  }
-}
-
-// Load events
-const eventsPath = path.join(__dirname, 'events');
-const eventFiles = fs.readdirSync(eventsPath).filter(f => f.endsWith('.js'));
-
-for (const file of eventFiles) {
-  const filePath = path.join(eventsPath, file);
-  const event = require(filePath);
-  if (event.once) {
-    client.once(event.name, (...args) => event.execute(...args));
-  } else {
-    client.on(event.name, (...args) => event.execute(...args));
-  }
-}
-
-client.login(process.env.DISCORD_TOKEN);
-```
-
-```javascript
-// src/commands/ping.js
-const { SlashCommandBuilder } = require('discord.js');
-
-module.exports = {
-  data: new SlashCommandBuilder()
-    .setName('ping')
-    .setDescription('Replies with Pong!'),
-
-  async execute(interaction) {
-    const sent = await interaction.reply({
-      content: 'Pinging...',
-      fetchReply: true
-    });
-
-    const latency = sent.createdTimestamp - interaction.createdTimestamp;
-    await interaction.editReply(`Pong! Latency: ${latency}ms`);
-  }
-};
-```
-
-```javascript
-// src/events/interactionCreate.js
-const { Events } = require('discord.js');
-
-module.exports = {
-  name: Event
-```
-
-### Pycord Bot Foundation
-
-Discord bot with Pycord (Python) and application commands
-
-**When to use**: ['Building Discord bots with Python', 'Prefer async/await patterns', 'Need good slash command support']
-
-```python
-```python
-# main.py
-import os
-import discord
-from discord.ext import commands
-from dotenv import load_dotenv
-
-load_dotenv()
-
-# Configure intents - only enable what you need
-intents = discord.Intents.default()
-# intents.message_content = True  # PRIVILEGED - avoid if possible
-# intents.members = True          # PRIVILEGED
-
-bot = commands.Bot(
-    command_prefix="!",  # Legacy, prefer slash commands
-    intents=intents
-)
-
-@bot.event
-async def on_ready():
-    print(f"Logged in as {bot.user}")
-    # Sync commands (do this carefully - see sharp edges)
-    # await bot.sync_commands()
-
-# Slash command
-@bot.slash_command(name="ping", description="Check bot latency")
-async def ping(ctx: discord.ApplicationContext):
-    latency = round(bot.latency * 1000)
-    await ctx.respond(f"Pong! Latency: {latency}ms")
-
-# Slash command with options
-@bot.slash_command(name="greet", description="Greet a user")
-async def greet(
-    ctx: discord.ApplicationContext,
-    user: discord.Option(discord.Member, "User to greet"),
-    message: discord.Option(str, "Custom message", required=False)
-):
-    msg = message or "Hello!"
-    await ctx.respond(f"{user.mention}, {msg}")
-
-# Load cogs
-for filename in os.listdir("./cogs"):
-    if filename.endswith(".py"):
-        bot.load_extension(f"cogs.{filename[:-3]}")
-
-bot.run(os.environ["DISCORD_TOKEN"])
-```
-
-```python
-# cogs/general.py
-import discord
-from discord.ext import commands
-
-class General(commands.Cog):
-    def __init__(self, bot):
-        self.bot = bot
-
-    @commands.slash_command(name="info", description="Bot information")
-    async def info(self, ctx: discord.ApplicationContext):
-        embed = discord.Embed(
-            title="Bot Info",
-            description="A helpful Discord bot",
-            color=discord.Color.blue()
-        )
-        embed.add_field(name="Servers", value=len(self.bot.guilds))
-        embed.add_field(name="Latency", value=f"{round(self.bot.latency * 1000)}ms")
-        await ctx.respond(embed=embed)
-
-    @commands.Cog.
-```
-
-### Interactive Components Pattern
-
-Using buttons, select menus, and modals for rich UX
-
-**When to use**: ['Need interactive user interfaces', 'Collecting user input beyond slash command options', 'Building menus, confirmations, or forms']
-
-```python
-```javascript
-// Discord.js - Buttons and Select Menus
-const {
-  SlashCommandBuilder,
-  ActionRowBuilder,
-  ButtonBuilder,
-  ButtonStyle,
-  StringSelectMenuBuilder,
-  ModalBuilder,
-  TextInputBuilder,
-  TextInputStyle
-} = require('discord.js');
-
-module.exports = {
-  data: new SlashCommandBuilder()
-    .setName('menu')
-    .setDescription('Shows an interactive menu'),
-
-  async execute(interaction) {
-    // Button row
-    const buttonRow = new ActionRowBuilder()
-      .addComponents(
-        new ButtonBuilder()
-          .setCustomId('confirm')
-          .setLabel('Confirm')
-          .setStyle(ButtonStyle.Primary),
-        new ButtonBuilder()
-          .setCustomId('cancel')
-          .setLabel('Cancel')
-          .setStyle(ButtonStyle.Danger),
-        new ButtonBuilder()
-          .setLabel('Documentation')
-          .setURL('https://discord.js.org')
-          .setStyle(ButtonStyle.Link)  // Link buttons don't emit events
-      );
-
-    // Select menu row (one per row, takes all 5 slots)
-    const selectRow = new ActionRowBuilder()
-      .addComponents(
-        new StringSelectMenuBuilder()
-          .setCustomId('select-role')
-          .setPlaceholder('Select a role')
-          .setMinValues(1)
-          .setMaxValues(3)
-          .addOptions([
-            { label: 'Developer', value: 'dev', emoji: '💻' },
-            { label: 'Designer', value: 'design', emoji: '🎨' },
-            { label: 'Community', value: 'community', emoji: '🎉' }
-          ])
-      );
-
-    await interaction.reply({
-      content: 'Choose an option:',
-      components: [buttonRow, selectRow]
-    });
-
-    // Collect responses
-    const collector = interaction.channel.createMessageComponentCollector({
-      filter: i => i.user.id === interaction.user.id,
-      time: 60_000  // 60 seconds timeout
-    });
-
-    collector.on('collect', async i => {
-      if (i.customId === 'confirm') {
-        await i.update({ content: 'Confirmed!', components: [] });
-        collector.stop();
-      } else if (i.custo
-```
-
-## Anti-Patterns
-
-### ❌ Message Content for Commands
-
-**Why bad**: Message Content Intent is privileged and deprecated for bot commands.
-Slash commands are the intended approach.
-
-### ❌ Syncing Commands on Every Start
-
-**Why bad**: Command registration is rate limited. Global commands take up to 1 hour
-to propagate. Syncing on every start wastes API calls and can hit limits.
-
-### ❌ Blocking the Event Loop
-
-**Why bad**: Discord gateway requires regular heartbeats. Blocking operations
-cause missed heartbeats and disconnections.
-
-## ⚠️ Sharp Edges
-
-| Issue | Severity | Solution |
-|-------|----------|----------|
-| Issue | critical | ## Acknowledge immediately, process later |
-| Issue | critical | ## Step 1: Enable in Developer Portal |
-| Issue | high | ## Use a separate deploy script (not on startup) |
-| Issue | critical | ## Never hardcode tokens |
-| Issue | high | ## Generate correct invite URL |
-| Issue | medium | ## Development: Use guild commands |
-| Issue | medium | ## Never block the event loop |
-| Issue | medium | ## Show modal immediately |
-
-
----
-
-## 🧠 AGI Framework Integration
-
-> **Adapted for [@techwavedev/agi-agent-kit](https://www.npmjs.com/package/@techwavedev/agi-agent-kit)**
-> Original source: [antigravity-awesome-skills](https://github.com/sickn33/antigravity-awesome-skills)
-
-### Qdrant Memory Integration
-
-Before executing complex tasks with this skill:
-```bash
-python3 execution/memory_manager.py auto --query "<task summary>"
-```
-- **Cache hit?** Use cached response directly — no need to re-process.
-- **Memory match?** Inject `context_chunks` into your reasoning.
-- **No match?** Proceed normally, then store results:
-```bash
-python3 execution/memory_manager.py store \
-  --content "Description of what was decided/solved" \
-  --type decision \
-  --tags discord-bot-architect <relevant-tags>
-```
-
-### Agent Team Collaboration
-
-- This skill can be invoked by the `orchestrator` agent via intelligent routing.
-- In **Agent Teams mode**, results are shared via Qdrant shared memory for cross-agent context.
-- In **Subagent mode**, this skill runs in isolation with its own memory namespace.
-
-### Local LLM Support
-
-When available, use local Ollama models for embedding and lightweight inference:
-- Embeddings: `nomic-embed-text` via Qdrant memory system
-- Lightweight analysis: Local models reduce API costs for repetitive patterns

package/templates/skills/extended/frontend/event-sourcing-architect/SKILL.md

@@ -1,94 +0,0 @@
----
-name: event-sourcing-architect
-description: "Expert in event sourcing, CQRS, and event-driven architecture patterns. Masters event store design, projection building, saga orchestration, and eventual consistency patterns. Use PROACTIVELY for event-sourced systems, audit trails, or temporal queries."
----
-
-# Event Sourcing Architect
-
-Expert in event sourcing, CQRS, and event-driven architecture patterns. Masters event store design, projection building, saga orchestration, and eventual consistency patterns. Use PROACTIVELY for event-sourced systems, audit trail requirements, or complex domain modeling with temporal queries.
-
-## Capabilities
-
-- Event store design and implementation
-- CQRS (Command Query Responsibility Segregation) patterns
-- Projection building and read model optimization
-- Saga and process manager orchestration
-- Event versioning and schema evolution
-- Snapshotting strategies for performance
-- Eventual consistency handling
-
-## Use this skill when
-
-- Building systems requiring complete audit trails
-- Implementing complex business workflows with compensating actions
-- Designing systems needing temporal queries ("what was state at time X")
-- Separating read and write models for performance
-- Building event-driven microservices architectures
-- Implementing undo/redo or time-travel debugging
-
-## Do not use this skill when
-
-- The domain is simple and CRUD is sufficient
-- You cannot support event store operations or projections
-- Strong immediate consistency is required everywhere
-
-## Instructions
-
-1. Identify aggregate boundaries and event streams
-2. Design events as immutable facts
-3. Implement command handlers and event application
-4. Build projections for query requirements
-5. Design saga/process managers for cross-aggregate workflows
-6. Implement snapshotting for long-lived aggregates
-7. Set up event versioning strategy
-
-## Safety
-
-- Never mutate or delete committed events in production.
-- Rebuild projections in staging before running in production.
-
-## Best Practices
-
-- Events are facts - never delete or modify them
-- Keep events small and focused
-- Version events from day one
-- Design for eventual consistency
-- Use correlation IDs for tracing
-- Implement idempotent event handlers
-- Plan for projection rebuilding
-
-
----
-
-## 🧠 AGI Framework Integration
-
-> **Adapted for [@techwavedev/agi-agent-kit](https://www.npmjs.com/package/@techwavedev/agi-agent-kit)**
-> Original source: [antigravity-awesome-skills](https://github.com/sickn33/antigravity-awesome-skills)
-
-### Qdrant Memory Integration
-
-Before executing complex tasks with this skill:
-```bash
-python3 execution/memory_manager.py auto --query "<task summary>"
-```
-- **Cache hit?** Use cached response directly — no need to re-process.
-- **Memory match?** Inject `context_chunks` into your reasoning.
-- **No match?** Proceed normally, then store results:
-```bash
-python3 execution/memory_manager.py store \
-  --content "Description of what was decided/solved" \
-  --type decision \
-  --tags event-sourcing-architect <relevant-tags>
-```
-
-### Agent Team Collaboration
-
-- This skill can be invoked by the `orchestrator` agent via intelligent routing.
-- In **Agent Teams mode**, results are shared via Qdrant shared memory for cross-agent context.
-- In **Subagent mode**, this skill runs in isolation with its own memory namespace.
-
-### Local LLM Support
-
-When available, use local Ollama models for embedding and lightweight inference:
-- Embeddings: `nomic-embed-text` via Qdrant memory system
-- Lightweight analysis: Local models reduce API costs for repetitive patterns