npm - @cubis/foundry - Versions diffs - 0.3.71 → 0.3.72 - Mend

@cubis/foundry 0.3.71 → 0.3.72

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 (270) hide show

package/workflows/powers/game-development/POWER.md CHANGED Viewed

@@ -2,169 +2,86 @@
 ---
 inclusion: manual
 name: game-development
-description: Game development orchestrator. Routes to platform-specific skills based on project needs.
-allowed-tools: Read, Write, Edit, Glob, Grep, Bash
+description: "Use when implementing game mechanics, game loops, physics, AI, collision detection, or performance optimization for web, mobile, PC, or VR/AR games."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0"
+compatibility: Claude Code, Codex, GitHub Copilot
 ---
 # Game Development
-> **Orchestrator skill** that provides core principles and routes to specialized sub-skills.
+## Purpose
----
-## When to Use This Skill
-You are working on a game development project. This skill teaches the PRINCIPLES of game development and directs you to the right sub-skill based on context.
----
-## Sub-Skill Routing
-### Platform Selection
-| If the game targets... | Use Sub-Skill |
-|------------------------|---------------|
-| Web browsers (HTML5, WebGL) | `game-development/web-games` |
-| Mobile (iOS, Android) | `game-development/mobile-games` |
-| PC (Steam, Desktop) | `game-development/pc-games` |
-| VR/AR headsets | `game-development/vr-ar` |
-### Dimension Selection
-| If the game is... | Use Sub-Skill |
-|-------------------|---------------|
-| 2D (sprites, tilemaps) | `game-development/2d-games` |
-| 3D (meshes, shaders) | `game-development/3d-games` |
-### Specialty Areas
-| If you need... | Use Sub-Skill |
-|----------------|---------------|
-| GDD, balancing, player psychology | `game-development/game-design` |
-| Multiplayer, networking | `game-development/multiplayer` |
-| Visual style, asset pipeline, animation | `game-development/game-art` |
-| Sound design, music, adaptive audio | `game-development/game-audio` |
----
-## Core Principles (All Platforms)
-### 1. The Game Loop
-Every game, regardless of platform, follows this pattern:
-```
-INPUT  → Read player actions
-UPDATE → Process game logic (fixed timestep)
-RENDER → Draw the frame (interpolated)
-```
+Use when implementing game mechanics, game loops, physics, AI, collision detection, or performance optimization for web, mobile, PC, or VR/AR games.
-**Fixed Timestep Rule:**
-- Physics/logic: Fixed rate (e.g., 50Hz)
-- Rendering: As fast as possible
-- Interpolate between states for smooth visuals
+## When to Use
----
-### 2. Pattern Selection Matrix
-| Pattern | Use When | Example |
-|---------|----------|---------|
-| **State Machine** | 3-5 discrete states | Player: Idle→Walk→Jump |
-| **Object Pooling** | Frequent spawn/destroy | Bullets, particles |
-| **Observer/Events** | Cross-system communication | Health→UI updates |
-| **ECS** | Thousands of similar entities | RTS units, particles |
-| **Command** | Undo, replay, networking | Input recording |
-| **Behavior Tree** | Complex AI decisions | Enemy AI |
-**Decision Rule:** Start with State Machine. Add ECS only when performance demands.
----
-### 3. Input Abstraction
-Abstract input into ACTIONS, not raw keys:
-```
-"jump"  → Space, Gamepad A, Touch tap
-"move"  → WASD, Left stick, Virtual joystick
-```
+- Implementing core game loops (input, update, render) for any platform.
+- Choosing game architecture patterns (ECS, state machine, object pooling).
+- Implementing collision detection, physics, or spatial partitioning.
+- Designing game AI (FSM, behavior trees, utility AI, GOAP).
+- Optimizing game performance to hit 60 FPS budgets.
+- Platform-specific game delivery (web, mobile, desktop, VR/AR).
-**Why:** Enables multi-platform, rebindable controls.
+## Instructions
----
+1. Determine target platform and rendering approach.
+2. Implement the core game loop with fixed timestep for physics and variable timestep for rendering.
+3. Choose architecture patterns based on entity count and complexity.
+4. Implement game systems in priority order: input, physics/collision, game logic, rendering, audio.
+5. Profile early and continuously against the performance budget.
-### 4. Performance Budget (60 FPS = 16.67ms)
+### Baseline standards
-| System | Budget |
-|--------|--------|
-| Input | 1ms |
-| Physics | 3ms |
-| AI | 2ms |
-| Game Logic | 4ms |
-| Rendering | 5ms |
-| Buffer | 1.67ms |
+- Performance budget: 60 FPS = 16.67ms per frame (input 1ms, physics 3ms, game logic 4ms, render 6ms, audio 1ms, overhead 1.67ms).
+- Use object pooling for frequently created/destroyed entities.
+- Separate game logic from rendering for testability.
+- Use spatial partitioning for collision detection at scale.
+- Implement deterministic physics with fixed timestep.
-**Optimization Priority:**
-1. Algorithm (O(n²) → O(n log n))
-2. Batching (reduce draw calls)
-3. Pooling (avoid GC spikes)
-4. LOD (detail by distance)
-5. Culling (skip invisible)
+### Pattern selection
----
+| Pattern         | When to Use                                     |
+| --------------- | ----------------------------------------------- |
+| State Machine   | Character states, UI flow, game phases          |
+| ECS             | Large entity counts, data-driven composition    |
+| Object Pooling  | Bullets, particles, frequently spawned entities |
+| Command Pattern | Input handling, replay, undo                    |
+| Observer        | Events, achievements, UI updates                |
-### 5. AI Selection by Complexity
+### AI selection by complexity
-| AI Type | Complexity | Use When |
-|---------|------------|----------|
-| **FSM** | Simple | 3-5 states, predictable behavior |
-| **Behavior Tree** | Medium | Modular, designer-friendly |
-| **GOAP** | High | Emergent, planning-based |
-| **Utility AI** | High | Scoring-based decisions |
+| Complexity | Approach                                   |
+| ---------- | ------------------------------------------ |
+| Simple     | Finite State Machine (FSM)                 |
+| Medium     | Behavior Tree                              |
+| Complex    | GOAP or Utility AI                         |
+| Adaptive   | Machine learning (rare in real-time games) |
----
+### Constraints
-### 6. Collision Strategy
+- Never allocate memory in the hot path (game loop).
+- Never use floating point equality for physics comparisons.
+- Never couple game logic directly to frame rate.
+- Always handle edge cases in collision detection (tunneling, resting contact).
-| Type | Best For |
-|------|----------|
-| **AABB** | Rectangles, fast checks |
-| **Circle** | Round objects, cheap |
-| **Spatial Hash** | Many similar-sized objects |
-| **Quadtree** | Large worlds, varying sizes |
+## Output Format
----
+Provide implementation guidance, code examples, architecture diagrams, and performance budgets as appropriate.
-## Anti-Patterns (Universal)
+## References
-| Don't | Do |
-|-------|-----|
-| Update everything every frame | Use events, dirty flags |
-| Create objects in hot loops | Object pooling |
-| Cache nothing | Cache references |
-| Optimize without profiling | Profile first |
-| Mix input with logic | Abstract input layer |
+No reference files for this skill right now.
----
+## Scripts
-## Routing Examples
+No helper scripts are required for this skill right now.
-### Example 1: "I want to make a browser-based 2D platformer"
-→ Start with `game-development/web-games` for framework selection
-→ Then `game-development/2d-games` for sprite/tilemap patterns
-→ Reference `game-development/game-design` for level design
-### Example 2: "Mobile puzzle game for iOS and Android"
-→ Start with `game-development/mobile-games` for touch input and stores
-→ Use `game-development/game-design` for puzzle balancing
-### Example 3: "Multiplayer VR shooter"
-→ `game-development/vr-ar` for comfort and immersion
-→ `game-development/3d-games` for rendering
-→ `game-development/multiplayer` for networking
----
+## Examples
-> **Remember:** Great games come from iteration, not perfection. Prototype fast, then polish.
+- "Help me implement a game loop with fixed timestep physics"
+- "Choose the right collision detection strategy for my 2D platformer"
+- "Design an entity component system for my RTS game"
 ````

package/workflows/powers/game-development/SKILL.md CHANGED Viewed

@@ -1,167 +1,84 @@
 ---
 name: game-development
-description: Game development orchestrator. Routes to platform-specific skills based on project needs.
-allowed-tools: Read, Write, Edit, Glob, Grep, Bash
+description: "Use when implementing game mechanics, game loops, physics, AI, collision detection, or performance optimization for web, mobile, PC, or VR/AR games."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0"
+compatibility: Claude Code, Codex, GitHub Copilot
 ---
 # Game Development
-> **Orchestrator skill** that provides core principles and routes to specialized sub-skills.
+## Purpose
----
-## When to Use This Skill
-You are working on a game development project. This skill teaches the PRINCIPLES of game development and directs you to the right sub-skill based on context.
----
-## Sub-Skill Routing
-### Platform Selection
-| If the game targets... | Use Sub-Skill |
-|------------------------|---------------|
-| Web browsers (HTML5, WebGL) | `game-development/web-games` |
-| Mobile (iOS, Android) | `game-development/mobile-games` |
-| PC (Steam, Desktop) | `game-development/pc-games` |
-| VR/AR headsets | `game-development/vr-ar` |
-### Dimension Selection
-| If the game is... | Use Sub-Skill |
-|-------------------|---------------|
-| 2D (sprites, tilemaps) | `game-development/2d-games` |
-| 3D (meshes, shaders) | `game-development/3d-games` |
-### Specialty Areas
-| If you need... | Use Sub-Skill |
-|----------------|---------------|
-| GDD, balancing, player psychology | `game-development/game-design` |
-| Multiplayer, networking | `game-development/multiplayer` |
-| Visual style, asset pipeline, animation | `game-development/game-art` |
-| Sound design, music, adaptive audio | `game-development/game-audio` |
----
-## Core Principles (All Platforms)
-### 1. The Game Loop
-Every game, regardless of platform, follows this pattern:
-```
-INPUT  → Read player actions
-UPDATE → Process game logic (fixed timestep)
-RENDER → Draw the frame (interpolated)
-```
+Use when implementing game mechanics, game loops, physics, AI, collision detection, or performance optimization for web, mobile, PC, or VR/AR games.
-**Fixed Timestep Rule:**
-- Physics/logic: Fixed rate (e.g., 50Hz)
-- Rendering: As fast as possible
-- Interpolate between states for smooth visuals
+## When to Use
----
-### 2. Pattern Selection Matrix
-| Pattern | Use When | Example |
-|---------|----------|---------|
-| **State Machine** | 3-5 discrete states | Player: Idle→Walk→Jump |
-| **Object Pooling** | Frequent spawn/destroy | Bullets, particles |
-| **Observer/Events** | Cross-system communication | Health→UI updates |
-| **ECS** | Thousands of similar entities | RTS units, particles |
-| **Command** | Undo, replay, networking | Input recording |
-| **Behavior Tree** | Complex AI decisions | Enemy AI |
-**Decision Rule:** Start with State Machine. Add ECS only when performance demands.
----
-### 3. Input Abstraction
-Abstract input into ACTIONS, not raw keys:
-```
-"jump"  → Space, Gamepad A, Touch tap
-"move"  → WASD, Left stick, Virtual joystick
-```
+- Implementing core game loops (input, update, render) for any platform.
+- Choosing game architecture patterns (ECS, state machine, object pooling).
+- Implementing collision detection, physics, or spatial partitioning.
+- Designing game AI (FSM, behavior trees, utility AI, GOAP).
+- Optimizing game performance to hit 60 FPS budgets.
+- Platform-specific game delivery (web, mobile, desktop, VR/AR).
-**Why:** Enables multi-platform, rebindable controls.
+## Instructions
----
+1. Determine target platform and rendering approach.
+2. Implement the core game loop with fixed timestep for physics and variable timestep for rendering.
+3. Choose architecture patterns based on entity count and complexity.
+4. Implement game systems in priority order: input, physics/collision, game logic, rendering, audio.
+5. Profile early and continuously against the performance budget.
-### 4. Performance Budget (60 FPS = 16.67ms)
+### Baseline standards
-| System | Budget |
-|--------|--------|
-| Input | 1ms |
-| Physics | 3ms |
-| AI | 2ms |
-| Game Logic | 4ms |
-| Rendering | 5ms |
-| Buffer | 1.67ms |
+- Performance budget: 60 FPS = 16.67ms per frame (input 1ms, physics 3ms, game logic 4ms, render 6ms, audio 1ms, overhead 1.67ms).
+- Use object pooling for frequently created/destroyed entities.
+- Separate game logic from rendering for testability.
+- Use spatial partitioning for collision detection at scale.
+- Implement deterministic physics with fixed timestep.
-**Optimization Priority:**
-1. Algorithm (O(n²) → O(n log n))
-2. Batching (reduce draw calls)
-3. Pooling (avoid GC spikes)
-4. LOD (detail by distance)
-5. Culling (skip invisible)
+### Pattern selection
----
+| Pattern         | When to Use                                     |
+| --------------- | ----------------------------------------------- |
+| State Machine   | Character states, UI flow, game phases          |
+| ECS             | Large entity counts, data-driven composition    |
+| Object Pooling  | Bullets, particles, frequently spawned entities |
+| Command Pattern | Input handling, replay, undo                    |
+| Observer        | Events, achievements, UI updates                |
-### 5. AI Selection by Complexity
+### AI selection by complexity
-| AI Type | Complexity | Use When |
-|---------|------------|----------|
-| **FSM** | Simple | 3-5 states, predictable behavior |
-| **Behavior Tree** | Medium | Modular, designer-friendly |
-| **GOAP** | High | Emergent, planning-based |
-| **Utility AI** | High | Scoring-based decisions |
+| Complexity | Approach                                   |
+| ---------- | ------------------------------------------ |
+| Simple     | Finite State Machine (FSM)                 |
+| Medium     | Behavior Tree                              |
+| Complex    | GOAP or Utility AI                         |
+| Adaptive   | Machine learning (rare in real-time games) |
----
+### Constraints
-### 6. Collision Strategy
+- Never allocate memory in the hot path (game loop).
+- Never use floating point equality for physics comparisons.
+- Never couple game logic directly to frame rate.
+- Always handle edge cases in collision detection (tunneling, resting contact).
-| Type | Best For |
-|------|----------|
-| **AABB** | Rectangles, fast checks |
-| **Circle** | Round objects, cheap |
-| **Spatial Hash** | Many similar-sized objects |
-| **Quadtree** | Large worlds, varying sizes |
+## Output Format
----
+Provide implementation guidance, code examples, architecture diagrams, and performance budgets as appropriate.
-## Anti-Patterns (Universal)
+## References
-| Don't | Do |
-|-------|-----|
-| Update everything every frame | Use events, dirty flags |
-| Create objects in hot loops | Object pooling |
-| Cache nothing | Cache references |
-| Optimize without profiling | Profile first |
-| Mix input with logic | Abstract input layer |
+No reference files for this skill right now.
----
+## Scripts
-## Routing Examples
+No helper scripts are required for this skill right now.
-### Example 1: "I want to make a browser-based 2D platformer"
-→ Start with `game-development/web-games` for framework selection
-→ Then `game-development/2d-games` for sprite/tilemap patterns
-→ Reference `game-development/game-design` for level design
-### Example 2: "Mobile puzzle game for iOS and Android"
-→ Start with `game-development/mobile-games` for touch input and stores
-→ Use `game-development/game-design` for puzzle balancing
-### Example 3: "Multiplayer VR shooter"
-→ `game-development/vr-ar` for comfort and immersion
-→ `game-development/3d-games` for rendering
-→ `game-development/multiplayer` for networking
----
+## Examples
-> **Remember:** Great games come from iteration, not perfection. Prototype fast, then polish.
+- "Help me implement a game loop with fixed timestep physics"
+- "Choose the right collision detection strategy for my 2D platformer"
+- "Design an entity component system for my RTS game"

package/workflows/powers/geo-fundamentals/POWER.md CHANGED Viewed

@@ -2,157 +2,95 @@
 ---
 inclusion: manual
 name: geo-fundamentals
-description: Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).
-allowed-tools: Read, Glob, Grep
+description: "Use when optimizing content for AI search engines (ChatGPT, Claude, Perplexity) using Generative Engine Optimization techniques and citation-worthy content patterns."
+license: MIT
+metadata:
+  author: cubis-foundry
+  version: "1.0"
+compatibility: Claude Code, Codex, GitHub Copilot
 ---
 # GEO Fundamentals
-> Optimization for AI-powered search engines.
+## Purpose
----
-## 1. What is GEO?
-**GEO** = Generative Engine Optimization
-| Goal | Platform |
-|------|----------|
-| Be cited in AI responses | ChatGPT, Claude, Perplexity, Gemini |
-### SEO vs GEO
-| Aspect | SEO | GEO |
-|--------|-----|-----|
-| Goal | #1 ranking | AI citations |
-| Platform | Google | AI engines |
-| Metrics | Rankings, CTR | Citation rate |
-| Focus | Keywords | Entities, data |
----
-## 2. AI Engine Landscape
-| Engine | Citation Style | Opportunity |
-|--------|----------------|-------------|
-| **Perplexity** | Numbered [1][2] | Highest citation rate |
-| **ChatGPT** | Inline/footnotes | Custom GPTs |
-| **Claude** | Contextual | Long-form content |
-| **Gemini** | Sources section | SEO crossover |
----
-## 3. RAG Retrieval Factors
-How AI engines select content to cite:
-| Factor | Weight |
-|--------|--------|
-| Semantic relevance | ~40% |
-| Keyword match | ~20% |
-| Authority signals | ~15% |
-| Freshness | ~10% |
-| Source diversity | ~15% |
+Use when optimizing content for AI search engines (ChatGPT, Claude, Perplexity) using Generative Engine Optimization techniques and citation-worthy content patterns.
----
-## 4. Content That Gets Cited
+## When to Use
-| Element | Why It Works |
-|---------|--------------|
-| **Original statistics** | Unique, citable data |
-| **Expert quotes** | Authority transfer |
-| **Clear definitions** | Easy to extract |
-| **Step-by-step guides** | Actionable value |
-| **Comparison tables** | Structured info |
-| **FAQ sections** | Direct answers |
----
+- Optimizing content to be cited by AI search engines and LLM-powered tools.
+- Understanding the differences between traditional SEO and Generative Engine Optimization.
+- Creating content that performs well in RAG retrieval pipelines.
+- Configuring AI crawler access and structured data for LLM consumption.
+- Designing content strategies that work across both traditional and AI-powered search.
-## 5. GEO Content Checklist
+## Instructions
-### Content Elements
+1. Understand the AI search landscape — how Perplexity, ChatGPT, and Claude cite sources differently.
+2. Optimize for RAG retrieval factors — semantic relevance (~40%), keyword match (~20%), authority (~15%), freshness (~10%), diversity (~15%).
+3. Create citation-worthy content — original statistics, expert quotes, clear definitions, step-by-step guides, comparison tables.
+4. Implement technical GEO — schema markup, author credentials, AI crawler access, FAQ sections.
+5. Measure and iterate — track AI citation frequency and adapt content strategy.
-- [ ] Question-based titles
-- [ ] Summary/TL;DR at top
-- [ ] Original data with sources
-- [ ] Expert quotes (name, title)
-- [ ] FAQ section (3-5 Q&A)
-- [ ] Clear definitions
-- [ ] "Last updated" timestamp
-- [ ] Author with credentials
+### SEO vs GEO comparison
-### Technical Elements
+| Aspect  | Traditional SEO            | Generative Engine Optimization      |
+| ------- | -------------------------- | ----------------------------------- |
+| Target  | Search engine results page | AI-generated answers                |
+| Goal    | Click-through from SERP    | Citation in AI response             |
+| Content | Keyword-optimized pages    | Citation-worthy, structured content |
+| Links   | Backlink building          | Authority signals for RAG           |
+| Schema  | For rich snippets          | For LLM understanding               |
-- [ ] Article schema with dates
-- [ ] Person schema for author
-- [ ] FAQPage schema
-- [ ] Fast loading (< 2.5s)
-- [ ] Clean HTML structure
+### Content patterns that get cited
----
+- Original statistics and data points
+- Expert quotes with credentials
+- Clear, concise definitions
+- Step-by-step guides with numbered steps
+- Comparison tables with concrete data
+- Unique frameworks or methodologies
-## 6. Entity Building
+### AI crawler user agents
-| Action | Purpose |
-|--------|---------|
-| Google Knowledge Panel | Entity recognition |
-| Wikipedia (if notable) | Authority source |
-| Consistent info across web | Entity consolidation |
-| Industry mentions | Authority signals |
+| Crawler         | Engine             |
+| --------------- | ------------------ |
+| GPTBot          | ChatGPT / OpenAI   |
+| Claude-Web      | Claude / Anthropic |
+| PerplexityBot   | Perplexity         |
+| Google-Extended | Google AI features |
----
+### GEO content checklist
-## 7. AI Crawler Access
+- Question-based titles and headings
+- Author credentials and expertise signals
+- FAQ sections with structured data
+- Article and FAQPage schema markup
+- Clear, quotable sentences in the first paragraph
+- Data-backed claims with sources
-### Key AI User-Agents
+### Constraints
-| Crawler | Engine |
-|---------|--------|
-| GPTBot | ChatGPT/OpenAI |
-| Claude-Web | Claude |
-| PerplexityBot | Perplexity |
-| Googlebot | Gemini (shared) |
+- Never block AI crawlers unless there's a specific business reason.
+- Never create content solely for AI citation without user value.
+- Always maintain content accuracy — AI engines amplify both good and bad information.
+- Always include proper attribution for data and quotes.
-### Access Decision
+## Output Format
-| Strategy | When |
-|----------|------|
-| Allow all | Want AI citations |
-| Block GPTBot | Don't want OpenAI training |
-| Selective | Allow some, block others |
+Provide GEO audit findings, content optimization recommendations, schema markup, and crawler configuration guidance.
----
+## References
-## 8. Measurement
+No reference files for this skill right now.
-| Metric | How to Track |
-|--------|--------------|
-| AI citations | Manual monitoring |
-| "According to [Brand]" mentions | Search in AI |
-| Competitor citations | Compare share |
-| AI-referred traffic | UTM parameters |
+## Scripts
----
-## 9. Anti-Patterns
-| ❌ Don't | ✅ Do |
-|----------|-------|
-| Publish without dates | Add timestamps |
-| Vague attributions | Name sources |
-| Skip author info | Show credentials |
-| Thin content | Comprehensive coverage |
----
-> **Remember:** AI cites content that's clear, authoritative, and easy to extract. Be the best answer.
----
+No helper scripts are required for this skill right now.
-## Script
+## Examples
-| Script | Purpose | Command |
-|--------|---------|---------|
-| `scripts/geo_checker.py` | GEO audit (AI citation readiness) | `python scripts/geo_checker.py <project_path>` |
+- "Optimize our documentation to be cited by AI search engines"
+- "Create a GEO content strategy for our developer blog"
+- "Configure AI crawler access and structured data for our site"
 ````