@ivannxbt/ai-config 0.1.0

package/.agents/skills/deep-agents-orchestration/SKILL.md

@@ -0,0 +1,471 @@
+---
+name: deep-agents-orchestration
+description: "INVOKE THIS SKILL when using subagents, task planning, or human approval in Deep Agents. Covers SubAgentMiddleware, TodoList for planning, and HITL interrupts."
+---
+
+<overview>
+Deep Agents include three orchestration capabilities:
+
+1. **SubAgentMiddleware**: Delegate work via `task` tool to specialized agents
+2. **TodoListMiddleware**: Plan and track tasks via `write_todos` tool
+3. **HumanInTheLoopMiddleware**: Require approval before sensitive operations
+
+All three are automatically included in `create_deep_agent()`.
+</overview>
+
+---
+
+## Subagents (Task Delegation)
+
+<when-to-use-subagents>
+
+| Use Subagents When | Use Main Agent When |
+|-------------------|-------------------|
+| Task needs specialized tools | General-purpose tools sufficient |
+| Want to isolate complex work | Single-step operation |
+| Need clean context for main agent | Context bloat acceptable |
+
+</when-to-use-subagents>
+
+<how-subagents-work>
+Main agent has `task` tool -> creates fresh subagent -> subagent executes autonomously -> returns final report.
+
+**Default subagent**: "general-purpose" - automatically available with same tools/config as main agent.
+</how-subagents-work>
+
+<ex-custom-subagents>
+<python>
+Create a custom "researcher" subagent with specialized tools for academic paper search.
+```python
+from deepagents import create_deep_agent
+from langchain.tools import tool
+
+@tool
+def search_papers(query: str) -> str:
+    """Search academic papers."""
+    return f"Found 10 papers about {query}"
+
+agent = create_deep_agent(
+    subagents=[
+        {
+            "name": "researcher",
+            "description": "Conduct web research and compile findings",
+            "system_prompt": "Search thoroughly, return concise summary",
+            "tools": [search_papers],
+        }
+    ]
+)
+
+# Main agent delegates: task(agent="researcher", instruction="Research AI trends")
+```
+</python>
+<typescript>
+Create a custom "researcher" subagent with specialized tools for academic paper search.
+```typescript
+import { createDeepAgent } from "deepagents";
+import { tool } from "@langchain/core/tools";
+import { z } from "zod";
+
+const searchPapers = tool(
+  async ({ query }) => `Found 10 papers about ${query}`,
+  { name: "search_papers", description: "Search papers", schema: z.object({ query: z.string() }) }
+);
+
+const agent = await createDeepAgent({
+  subagents: [
+    {
+      name: "researcher",
+      description: "Conduct web research and compile findings",
+      systemPrompt: "Search thoroughly, return concise summary",
+      tools: [searchPapers],
+    }
+  ]
+});
+
+// Main agent delegates: task(agent="researcher", instruction="Research AI trends")
+```
+</typescript>
+</ex-custom-subagents>
+
+<ex-subagent-with-hitl>
+<python>
+Configure a subagent with HITL approval for sensitive operations.
+```python
+from deepagents import create_deep_agent
+from langgraph.checkpoint.memory import MemorySaver
+
+agent = create_deep_agent(
+    subagents=[
+        {
+            "name": "code-deployer",
+            "description": "Deploy code to production",
+            "system_prompt": "You deploy code after tests pass.",
+            "tools": [run_tests, deploy_to_prod],
+            "interrupt_on": {"deploy_to_prod": True},  # Require approval
+        }
+    ],
+    checkpointer=MemorySaver()  # Required for interrupts
+)
+```
+</python>
+</ex-subagent-with-hitl>
+
+<fix-subagents-are-stateless>
+<python>
+Subagents are stateless - provide complete instructions in a single call.
+```python
+# WRONG: Subagents don't remember previous calls
+# task(agent='research', instruction='Find data')
+# task(agent='research', instruction='What did you find?')  # Starts fresh!
+
+# CORRECT: Complete instructions upfront
+# task(agent='research', instruction='Find data on AI, save to /research/, return summary')
+```
+</python>
+<typescript>
+Subagents are stateless - provide complete instructions in a single call.
+```typescript
+// WRONG: Subagents don't remember previous calls
+// task research: Find data
+// task research: What did you find?  // Starts fresh!
+
+// CORRECT: Complete instructions upfront
+// task research: Find data on AI, save to /research/, return summary
+```
+</typescript>
+</fix-subagents-are-stateless>
+
+<fix-custom-subagents-dont-inherit-skills>
+<python>
+Custom subagents don't inherit skills from the main agent.
+```python
+# WRONG: Custom subagent won't have main agent's skills
+agent = create_deep_agent(
+    skills=["/main-skills/"],
+    subagents=[{"name": "helper", ...}]  # No skills inherited
+)
+
+# CORRECT: Provide skills explicitly (general-purpose subagent DOES inherit)
+agent = create_deep_agent(
+    skills=["/main-skills/"],
+    subagents=[{"name": "helper", "skills": ["/helper-skills/"], ...}]
+)
+```
+</python>
+</fix-custom-subagents-dont-inherit-skills>
+
+---
+
+## TodoList (Task Planning)
+
+<when-to-use-todolist>
+
+| Use TodoList When | Skip TodoList When |
+|------------------|-------------------|
+| Complex multi-step tasks | Simple single-action tasks |
+| Long-running operations | Quick operations (< 3 steps) |
+
+</when-to-use-todolist>
+
+<todolist-tool>
+```
+write_todos(todos: list[dict]) -> None
+```
+
+Each todo item has:
+- `content`: Description of the task
+- `status`: One of `"pending"`, `"in_progress"`, `"completed"`
+</todolist-tool>
+
+<ex-todolist-usage>
+<python>
+Invoke an agent that automatically creates a todo list for a multi-step task.
+```python
+from deepagents import create_deep_agent
+
+agent = create_deep_agent()  # TodoListMiddleware included by default
+
+result = agent.invoke({
+    "messages": [{"role": "user", "content": "Create a REST API: design models, implement CRUD, add auth, write tests"}]
+}, config={"configurable": {"thread_id": "session-1"}})
+
+# Agent's planning via write_todos:
+# [
+#   {"content": "Design data models", "status": "in_progress"},
+#   {"content": "Implement CRUD endpoints", "status": "pending"},
+#   {"content": "Add authentication", "status": "pending"},
+#   {"content": "Write tests", "status": "pending"}
+# ]
+```
+</python>
+<typescript>
+Invoke an agent that automatically creates a todo list for a multi-step task.
+```typescript
+import { createDeepAgent } from "deepagents";
+
+const agent = await createDeepAgent();  // TodoListMiddleware included
+
+const result = await agent.invoke({
+  messages: [{ role: "user", content: "Create a REST API: design models, implement CRUD, add auth, write tests" }]
+}, { configurable: { thread_id: "session-1" } });
+```
+</typescript>
+</ex-todolist-usage>
+
+<ex-access-todo-state>
+<python>
+Access the todo list from the agent's final state after invocation.
+```python
+result = agent.invoke({...}, config={"configurable": {"thread_id": "session-1"}})
+
+# Access todo list from final state
+todos = result.get("todos", [])
+for todo in todos:
+    print(f"[{todo['status']}] {todo['content']}")
+```
+</python>
+</ex-access-todo-state>
+
+<fix-todolist-requires-thread-id>
+<python>
+Todo list state requires a thread_id for persistence across invocations.
+```python
+# WRONG: Fresh state each time without thread_id
+agent.invoke({"messages": [...]})
+
+# CORRECT: Use thread_id
+config = {"configurable": {"thread_id": "user-session"}}
+agent.invoke({"messages": [...]}, config=config)  # Todos preserved
+```
+</python>
+</fix-todolist-requires-thread-id>
+
+---
+
+## Human-in-the-Loop (Approval Workflows)
+
+<when-to-use-hitl>
+
+| Use HITL When | Skip HITL When |
+|--------------|---------------|
+| High-stakes operations (DB writes, deployments) | Read-only operations |
+| Compliance requires human oversight | Fully automated workflows |
+
+</when-to-use-hitl>
+
+<ex-hitl-setup>
+<python>
+Configure which tools require human approval before execution.
+```python
+from deepagents import create_deep_agent
+from langgraph.checkpoint.memory import MemorySaver
+
+agent = create_deep_agent(
+    interrupt_on={
+        "write_file": True,  # All decisions allowed
+        "execute_sql": {"allowed_decisions": ["approve", "reject"]},
+        "read_file": False,  # No interrupts
+    },
+    checkpointer=MemorySaver()  # REQUIRED for interrupts
+)
+```
+</python>
+<typescript>
+Configure which tools require human approval before execution.
+```typescript
+import { createDeepAgent } from "deepagents";
+import { MemorySaver } from "@langchain/langgraph";
+
+const agent = await createDeepAgent({
+  interruptOn: {
+    write_file: true,
+    execute_sql: { allowedDecisions: ["approve", "reject"] },
+    read_file: false,
+  },
+  checkpointer: new MemorySaver()  // REQUIRED
+});
+```
+</typescript>
+</ex-hitl-setup>
+
+<ex-approval-workflow>
+<python>
+Complete workflow: trigger an interrupt, check state, approve action, and resume execution.
+```python
+from deepagents import create_deep_agent
+from langgraph.checkpoint.memory import MemorySaver
+from langgraph.types import Command
+
+agent = create_deep_agent(
+    interrupt_on={"write_file": True},
+    checkpointer=MemorySaver()
+)
+
+config = {"configurable": {"thread_id": "session-1"}}
+
+# Step 1: Agent proposes write_file - execution pauses
+result = agent.invoke({
+    "messages": [{"role": "user", "content": "Write config to /prod.yaml"}]
+}, config=config)
+
+# Step 2: Check for interrupts
+state = agent.get_state(config)
+if state.next:
+    print(f"Pending action")
+
+# Step 3: Approve and resume
+result = agent.invoke(Command(resume={"decisions": [{"type": "approve"}]}), config=config)
+```
+</python>
+<typescript>
+Complete workflow: trigger an interrupt, check state, approve action, and resume execution.
+```typescript
+import { createDeepAgent } from "deepagents";
+import { MemorySaver, Command } from "@langchain/langgraph";
+
+const agent = await createDeepAgent({
+  interruptOn: { write_file: true },
+  checkpointer: new MemorySaver()
+});
+
+const config = { configurable: { thread_id: "session-1" } };
+
+// Step 1: Agent proposes write_file - execution pauses
+let result = await agent.invoke({
+  messages: [{ role: "user", content: "Write config to /prod.yaml" }]
+}, config);
+
+// Step 2: Check for interrupts
+const state = await agent.getState(config);
+if (state.next) {
+  console.log("Pending action");
+}
+
+// Step 3: Approve and resume
+result = await agent.invoke(
+  new Command({ resume: { decisions: [{ type: "approve" }] } }), config
+);
+```
+</typescript>
+</ex-approval-workflow>
+
+<ex-reject-with-feedback>
+<python>
+Reject a pending action with feedback, prompting the agent to try a different approach.
+```python
+result = agent.invoke(
+    Command(resume={"decisions": [{"type": "reject", "message": "Run tests first"}]}),
+    config=config,
+)
+```
+</python>
+<typescript>
+Reject a pending action with feedback, prompting the agent to try a different approach.
+```typescript
+const result = await agent.invoke(
+  new Command({ resume: { decisions: [{ type: "reject", message: "Run tests first" }] } }),
+  config,
+);
+```
+</typescript>
+</ex-reject-with-feedback>
+
+<ex-edit-before-execution>
+<python>
+Edit the proposed action arguments before allowing execution.
+```python
+result = agent.invoke(
+    Command(resume={"decisions": [{
+        "type": "edit",
+        "edited_action": {
+            "name": "execute_sql",
+            "args": {"query": "DELETE FROM users WHERE last_login < '2020-01-01' LIMIT 100"},
+        },
+    }]}),
+    config=config,
+)
+```
+</python>
+</ex-edit-before-execution>
+
+<boundaries>
+### What Agents CAN Configure
+
+- Subagent names, tools, models, system prompts
+- Which tools require approval
+- Allowed decision types per tool
+- TodoList content and structure
+
+### What Agents CANNOT Configure
+
+- Tool names (`task`, `write_todos`)
+- HITL protocol (approve/edit/reject structure)
+- Skip checkpointer requirement for interrupts
+- Make subagents stateful (they're ephemeral)
+</boundaries>
+
+<fix-checkpointer-required>
+<python>
+Checkpointer is required when using interrupt_on for HITL workflows.
+```python
+# WRONG
+agent = create_deep_agent(interrupt_on={"write_file": True})
+
+# CORRECT
+agent = create_deep_agent(interrupt_on={"write_file": True}, checkpointer=MemorySaver())
+```
+</python>
+<typescript>
+Checkpointer is required when using interruptOn for HITL workflows.
+```typescript
+// WRONG
+const agent = await createDeepAgent({ interruptOn: { write_file: true } });
+
+// CORRECT
+const agent = await createDeepAgent({ interruptOn: { write_file: true }, checkpointer: new MemorySaver() });
+```
+</typescript>
+</fix-checkpointer-required>
+
+<fix-thread-id-required-for-resumption>
+<python>
+A consistent thread_id is required to resume interrupted workflows.
+```python
+# WRONG: Can't resume without thread_id
+agent.invoke({"messages": [...]})
+
+# CORRECT
+config = {"configurable": {"thread_id": "session-1"}}
+agent.invoke({...}, config=config)
+# Resume with Command using same config
+agent.invoke(Command(resume={"decisions": [{"type": "approve"}]}), config=config)
+```
+</python>
+<typescript>
+A consistent thread_id is required to resume interrupted workflows.
+```typescript
+// WRONG: Can't resume without thread_id
+await agent.invoke({ messages: [...] });
+
+// CORRECT
+const config = { configurable: { thread_id: "session-1" } };
+await agent.invoke({ messages: [...] }, config);
+// Resume with Command using same config
+await agent.invoke(new Command({ resume: { decisions: [{ type: "approve" }] } }), config);
+```
+</typescript>
+</fix-thread-id-required-for-resumption>
+
+<fix-interrupt-checks-between-invocations>
+<python>
+Interrupts happen BETWEEN invoke() calls, not mid-execution.
+```python
+result = agent.invoke({...}, config=config)       # Step 1: triggers interrupt
+if "__interrupt__" in result:                      # Step 2: check for interrupt
+    result = agent.invoke(                         # Step 3: resume
+        Command(resume={"decisions": [{"type": "approve"}]}),
+        config=config,
+    )
+```
+</python>
+</fix-interrupt-checks-between-invocations>

package/.agents/skills/design-md/SKILL.md

@@ -0,0 +1,172 @@
+---
+name: design-md
+description: Analyze Stitch projects and synthesize a semantic design system into DESIGN.md files
+allowed-tools:
+  - "stitch*:*"
+  - "Read"
+  - "Write"
+  - "web_fetch"
+---
+
+# Stitch DESIGN.md Skill
+
+You are an expert Design Systems Lead. Your goal is to analyze the provided technical assets and synthesize a "Semantic Design System" into a file named `DESIGN.md`.
+
+## Overview
+
+This skill helps you create `DESIGN.md` files that serve as the "source of truth" for prompting Stitch to generate new screens that align perfectly with existing design language. Stitch interprets design through "Visual Descriptions" supported by specific color values.
+
+## Prerequisites
+
+- Access to the Stitch MCP Server
+- A Stitch project with at least one designed screen
+- Access to the Stitch Effective Prompting Guide: https://stitch.withgoogle.com/docs/learn/prompting/
+
+## The Goal
+
+The `DESIGN.md` file will serve as the "source of truth" for prompting Stitch to generate new screens that align perfectly with the existing design language. Stitch interprets design through "Visual Descriptions" supported by specific color values.
+
+## Retrieval and Networking
+
+To analyze a Stitch project, you must retrieve screen metadata and design assets using the Stitch MCP Server tools:
+
+1. **Namespace discovery**: Run `list_tools` to find the Stitch MCP prefix. Use this prefix (e.g., `mcp_stitch:`) for all subsequent calls.
+
+2. **Project lookup** (if Project ID is not provided):
+   - Call `[prefix]:list_projects` with `filter: "view=owned"` to retrieve all user projects
+   - Identify the target project by title or URL pattern
+   - Extract the Project ID from the `name` field (e.g., `projects/13534454087919359824`)
+
+3. **Screen lookup** (if Screen ID is not provided):
+   - Call `[prefix]:list_screens` with the `projectId` (just the numeric ID, not the full path)
+   - Review screen titles to identify the target screen (e.g., "Home", "Landing Page")
+   - Extract the Screen ID from the screen's `name` field
+
+4. **Metadata fetch**: 
+   - Call `[prefix]:get_screen` with both `projectId` and `screenId` (both as numeric IDs only)
+   - This returns the complete screen object including:
+     - `screenshot.downloadUrl` - Visual reference of the design
+     - `htmlCode.downloadUrl` - Full HTML/CSS source code
+     - `width`, `height`, `deviceType` - Screen dimensions and target platform
+     - Project metadata including `designTheme` with color and style information
+
+5. **Asset download**:
+   - Use `web_fetch` or `read_url_content` to download the HTML code from `htmlCode.downloadUrl`
+   - Optionally download the screenshot from `screenshot.downloadUrl` for visual reference
+   - Parse the HTML to extract Tailwind classes, custom CSS, and component patterns
+
+6. **Project metadata extraction**:
+   - Call `[prefix]:get_project` with the project `name` (full path: `projects/{id}`) to get:
+     - `designTheme` object with color mode, fonts, roundness, custom colors
+     - Project-level design guidelines and descriptions
+     - Device type preferences and layout principles
+
+## Analysis & Synthesis Instructions
+
+### 1. Extract Project Identity (JSON)
+- Locate the Project Title
+- Locate the specific Project ID (e.g., from the `name` field in the JSON)
+
+### 2. Define the Atmosphere (Image/HTML)
+Evaluate the screenshot and HTML structure to capture the overall "vibe." Use evocative adjectives to describe the mood (e.g., "Airy," "Dense," "Minimalist," "Utilitarian").
+
+### 3. Map the Color Palette (Tailwind Config/JSON)
+Identify the key colors in the system. For each color, provide:
+- A descriptive, natural language name that conveys its character (e.g., "Deep Muted Teal-Navy")
+- The specific hex code in parentheses for precision (e.g., "#294056")
+- Its specific functional role (e.g., "Used for primary actions")
+
+### 4. Translate Geometry & Shape (CSS/Tailwind)
+Convert technical `border-radius` and layout values into physical descriptions:
+- Describe `rounded-full` as "Pill-shaped"
+- Describe `rounded-lg` as "Subtly rounded corners"
+- Describe `rounded-none` as "Sharp, squared-off edges"
+
+### 5. Describe Depth & Elevation
+Explain how the UI handles layers. Describe the presence and quality of shadows (e.g., "Flat," "Whisper-soft diffused shadows," or "Heavy, high-contrast drop shadows").
+
+## Output Guidelines
+
+- **Language:** Use descriptive design terminology and natural language exclusively
+- **Format:** Generate a clean Markdown file following the structure below
+- **Precision:** Include exact hex codes for colors while using descriptive names
+- **Context:** Explain the "why" behind design decisions, not just the "what"
+
+## Output Format (DESIGN.md Structure)
+
+```markdown
+# Design System: [Project Title]
+**Project ID:** [Insert Project ID Here]
+
+## 1. Visual Theme & Atmosphere
+(Description of the mood, density, and aesthetic philosophy.)
+
+## 2. Color Palette & Roles
+(List colors by Descriptive Name + Hex Code + Functional Role.)
+
+## 3. Typography Rules
+(Description of font family, weight usage for headers vs. body, and letter-spacing character.)
+
+## 4. Component Stylings
+* **Buttons:** (Shape description, color assignment, behavior).
+* **Cards/Containers:** (Corner roundness description, background color, shadow depth).
+* **Inputs/Forms:** (Stroke style, background).
+
+## 5. Layout Principles
+(Description of whitespace strategy, margins, and grid alignment.)
+```
+
+## Usage Example
+
+To use this skill for the Furniture Collection project:
+
+1. **Retrieve project information:**
+   ```
+   Use the Stitch MCP Server to get the Furniture Collection project
+   ```
+
+2. **Get the Home page screen details:**
+   ```
+   Retrieve the Home page screen's code, image, and screen object information
+   ```
+
+3. **Reference best practices:**
+   ```
+   Review the Stitch Effective Prompting Guide at:
+   https://stitch.withgoogle.com/docs/learn/prompting/
+   ```
+
+4. **Analyze and synthesize:**
+   - Extract all relevant design tokens from the screen
+   - Translate technical values into descriptive language
+   - Organize information according to the DESIGN.md structure
+
+5. **Generate the file:**
+   - Create `DESIGN.md` in the project directory
+   - Follow the prescribed format exactly
+   - Ensure all color codes are accurate
+   - Use evocative, designer-friendly language
+
+## Best Practices
+
+- **Be Descriptive:** Avoid generic terms like "blue" or "rounded." Use "Ocean-deep Cerulean (#0077B6)" or "Gently curved edges"
+- **Be Functional:** Always explain what each design element is used for
+- **Be Consistent:** Use the same terminology throughout the document
+- **Be Visual:** Help readers visualize the design through your descriptions
+- **Be Precise:** Include exact values (hex codes, pixel values) in parentheses after natural language descriptions
+
+## Tips for Success
+
+1. **Start with the big picture:** Understand the overall aesthetic before diving into details
+2. **Look for patterns:** Identify consistent spacing, sizing, and styling patterns
+3. **Think semantically:** Name colors by their purpose, not just their appearance
+4. **Consider hierarchy:** Document how visual weight and importance are communicated
+5. **Reference the guide:** Use language and patterns from the Stitch Effective Prompting Guide
+
+## Common Pitfalls to Avoid
+
+- ❌ Using technical jargon without translation (e.g., "rounded-xl" instead of "generously rounded corners")
+- ❌ Omitting color codes or using only descriptive names
+- ❌ Forgetting to explain functional roles of design elements
+- ❌ Being too vague in atmosphere descriptions
+- ❌ Ignoring subtle design details like shadows or spacing patterns