@hiai-gg/hiai-opencode 0.2.1 → 0.2.2

package/skills/design-templates/html-ppt-zhangzara-grove/template.json

@@ -0,0 +1,51 @@
+{
+  "slug": "zhangzara-grove",
+  "name": "Grove",
+  "tagline": "Forest-green canvas with cream type, classical Playfair serifs, and a single rust accent.",
+  "mood": [
+    "organic",
+    "considered",
+    "warm",
+    "literary",
+    "natural"
+  ],
+  "occasion": [
+    "sustainability brand",
+    "wellness brand",
+    "outdoor / nature product",
+    "winery or restaurant",
+    "literary or arts deck",
+    "advisory deliverable",
+    "bilingual EN/CN deck"
+  ],
+  "tone": [
+    "classical",
+    "warm",
+    "considered",
+    "patient"
+  ],
+  "formality": "medium-high",
+  "density": "medium",
+  "palette": {
+    "bg": "#192b1b",
+    "bg_alt": "#1e3221",
+    "fg": "#d4cfbf",
+    "accent": "#c8524a",
+    "bg_light": "#e8e4d6",
+    "description": "deep forest green canvas with warm bone type and a single rust-red accent; alternate cream-paper mode for breathing room"
+  },
+  "typography": {
+    "display": "Playfair Display",
+    "body": "Jost",
+    "mono": "JetBrains Mono",
+    "serif_cn": "Noto Serif SC",
+    "sans_cn": "Noto Sans SC",
+    "style": "transitional serif headlines + clean geometric sans body + technical mono; full Chinese serif/sans support"
+  },
+  "scheme": "mixed",
+  "best_for": "Anything that should feel organic, considered, and grown-up: sustainability and wellness brands, outdoor / nature products, wineries and restaurants, literary or arts decks, advisory deliverables, bilingual EN/CN reports. Also a calm, distinctive choice for tech, research, or business decks that want patience over urgency.",
+  "avoid_for": "Decks that need neon energy or rapid-fire pop — the forest-green canvas and Playfair serif commit to a slow, classical voice.",
+  "slide_count": 12,
+  "navigation": "inline keyboard handler",
+  "source": "https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/grove"
+}

package/skills/figma-code-connect-components/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: figma-code-connect-components
+description: |
+  Connect Figma design components to code components using Code Connect so design-system updates flow into the codebase automatically.
+triggers:
+  - "figma code connect"
+  - "design to code"
+  - "figma components"
+  - "code connect"
+od:
+  mode: design-system
+  category: figma
+  upstream: "https://github.com/figma/skills"
+---
+
+# figma-code-connect-components
+
+> Curated from Figma's MCP server guide.
+
+## What it does
+
+Connect Figma design components to code components using Code Connect so design-system updates flow into the codebase automatically.
+
+## Source
+
+- Upstream: https://github.com/figma/skills
+- Category: `figma`
+
+## How to use
+
+This catalogue entry advertises the skill in Open Design so the agent
+discovers it during planning. To run the full upstream workflow with
+its original assets, scripts, and references, install the upstream
+bundle into your active agent's skills directory:
+
+```bash
+# Inspect the upstream README for exact paths
+open https://github.com/figma/skills
+```
+
+Then ask the agent to invoke this skill by name (`figma-code-connect-components`) or with
+one of the trigger phrases listed in this skill's frontmatter.

package/skills/figma-create-design-system-rules/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: figma-create-design-system-rules
+description: |
+  Generate project-specific design system rules for Figma-to-code workflows. Useful for capturing tokens, naming, and lint rules in one source.
+triggers:
+  - "figma rules"
+  - "design system rules"
+  - "figma to code rules"
+  - "figma tokens"
+od:
+  mode: design-system
+  category: figma
+  upstream: "https://github.com/figma/skills"
+---
+
+# figma-create-design-system-rules
+
+> Curated from Figma's MCP server guide.
+
+## What it does
+
+Generate project-specific design system rules for Figma-to-code workflows. Useful for capturing tokens, naming, and lint rules in one source.
+
+## Source
+
+- Upstream: https://github.com/figma/skills
+- Category: `figma`
+
+## How to use
+
+This catalogue entry advertises the skill in Open Design so the agent
+discovers it during planning. To run the full upstream workflow with
+its original assets, scripts, and references, install the upstream
+bundle into your active agent's skills directory:
+
+```bash
+# Inspect the upstream README for exact paths
+open https://github.com/figma/skills
+```
+
+Then ask the agent to invoke this skill by name (`figma-create-design-system-rules`) or with
+one of the trigger phrases listed in this skill's frontmatter.

package/skills/figma-create-new-file/SKILL.md

@@ -0,0 +1,41 @@
+---
+name: figma-create-new-file
+description: |
+  Create a new blank Figma Design or FigJam file. Useful as the first step in scripted design-system or workshop workflows.
+triggers:
+  - "figma new file"
+  - "figjam new"
+  - "create figma file"
+od:
+  mode: design-system
+  category: figma
+  upstream: "https://github.com/figma/skills"
+---
+
+# figma-create-new-file
+
+> Curated from Figma's MCP server guide.
+
+## What it does
+
+Create a new blank Figma Design or FigJam file. Useful as the first step in scripted design-system or workshop workflows.
+
+## Source
+
+- Upstream: https://github.com/figma/skills
+- Category: `figma`
+
+## How to use
+
+This catalogue entry advertises the skill in Open Design so the agent
+discovers it during planning. To run the full upstream workflow with
+its original assets, scripts, and references, install the upstream
+bundle into your active agent's skills directory:
+
+```bash
+# Inspect the upstream README for exact paths
+open https://github.com/figma/skills
+```
+
+Then ask the agent to invoke this skill by name (`figma-create-new-file`) or with
+one of the trigger phrases listed in this skill's frontmatter.

package/skills/figma-generate-design/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: figma-generate-design
+description: |
+  Build or update screens in Figma from code or description using design system components. Translate app pages into Figma using design tokens.
+triggers:
+  - "figma generate design"
+  - "code to figma"
+  - "screen generation"
+  - "figma from code"
+od:
+  mode: design-system
+  category: figma
+  upstream: "https://github.com/figma/skills"
+---
+
+# figma-generate-design
+
+> Curated from Figma's MCP server guide.
+
+## What it does
+
+Build or update screens in Figma from code or description using design system components. Translate app pages into Figma using design tokens.
+
+## Source
+
+- Upstream: https://github.com/figma/skills
+- Category: `figma`
+
+## How to use
+
+This catalogue entry advertises the skill in Open Design so the agent
+discovers it during planning. To run the full upstream workflow with
+its original assets, scripts, and references, install the upstream
+bundle into your active agent's skills directory:
+
+```bash
+# Inspect the upstream README for exact paths
+open https://github.com/figma/skills
+```
+
+Then ask the agent to invoke this skill by name (`figma-generate-design`) or with
+one of the trigger phrases listed in this skill's frontmatter.

package/skills/figma-generate-library/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: figma-generate-library
+description: |
+  Build or update a professional-grade design system library in Figma from a codebase. Useful for keeping the Figma source of truth in sync with shipped components.
+triggers:
+  - "figma library"
+  - "design system library"
+  - "figma from codebase"
+  - "sync figma"
+od:
+  mode: design-system
+  category: figma
+  upstream: "https://github.com/figma/skills"
+---
+
+# figma-generate-library
+
+> Curated from Figma's MCP server guide.
+
+## What it does
+
+Build or update a professional-grade design system library in Figma from a codebase. Useful for keeping the Figma source of truth in sync with shipped components.
+
+## Source
+
+- Upstream: https://github.com/figma/skills
+- Category: `figma`
+
+## How to use
+
+This catalogue entry advertises the skill in Open Design so the agent
+discovers it during planning. To run the full upstream workflow with
+its original assets, scripts, and references, install the upstream
+bundle into your active agent's skills directory:
+
+```bash
+# Inspect the upstream README for exact paths
+open https://github.com/figma/skills
+```
+
+Then ask the agent to invoke this skill by name (`figma-generate-library`) or with
+one of the trigger phrases listed in this skill's frontmatter.

package/skills/figma-implement-design/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: figma-implement-design
+description: |
+  Translate Figma designs into production-ready code with 1:1 visual fidelity. Useful for handing off Figma frames straight to a frontend agent.
+triggers:
+  - "figma to code"
+  - "implement figma"
+  - "figma fidelity"
+  - "1:1 figma"
+od:
+  mode: design-system
+  category: figma
+  upstream: "https://github.com/figma/skills"
+---
+
+# figma-implement-design
+
+> Curated from Figma's MCP server guide.
+
+## What it does
+
+Translate Figma designs into production-ready code with 1:1 visual fidelity. Useful for handing off Figma frames straight to a frontend agent.
+
+## Source
+
+- Upstream: https://github.com/figma/skills
+- Category: `figma`
+
+## How to use
+
+This catalogue entry advertises the skill in Open Design so the agent
+discovers it during planning. To run the full upstream workflow with
+its original assets, scripts, and references, install the upstream
+bundle into your active agent's skills directory:
+
+```bash
+# Inspect the upstream README for exact paths
+open https://github.com/figma/skills
+```
+
+Then ask the agent to invoke this skill by name (`figma-implement-design`) or with
+one of the trigger phrases listed in this skill's frontmatter.

package/skills/figma-use/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: figma-use
+description: |
+  Run Figma Plugin API scripts for canvas writes, inspections, variables, and design-system work. Prerequisite for every other Figma skill in this catalogue.
+triggers:
+  - "figma use"
+  - "figma plugin api"
+  - "figma canvas"
+  - "figma scripts"
+od:
+  mode: design-system
+  category: figma
+  upstream: "https://github.com/figma/skills"
+---
+
+# figma-use
+
+> Curated from Figma's MCP server guide.
+
+## What it does
+
+Run Figma Plugin API scripts for canvas writes, inspections, variables, and design-system work. Prerequisite for every other Figma skill in this catalogue.
+
+## Source
+
+- Upstream: https://github.com/figma/skills
+- Category: `figma`
+
+## How to use
+
+This catalogue entry advertises the skill in Open Design so the agent
+discovers it during planning. To run the full upstream workflow with
+its original assets, scripts, and references, install the upstream
+bundle into your active agent's skills directory:
+
+```bash
+# Inspect the upstream README for exact paths
+open https://github.com/figma/skills
+```
+
+Then ask the agent to invoke this skill by name (`figma-use`) or with
+one of the trigger phrases listed in this skill's frontmatter.

package/skills/full-page-screenshot/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: full-page-screenshot
+description: |
+  Capture full-page screenshots of web pages via Chrome DevTools Protocol with zero dependencies. Useful for portfolios, case studies, and audit reports.
+triggers:
+  - "full page screenshot"
+  - "long screenshot"
+  - "devtools screenshot"
+  - "web capture"
+od:
+  mode: image
+  category: screenshots
+  upstream: "https://github.com/LewisLiu007/full-page-screenshot"
+---
+
+# full-page-screenshot
+
+> Curated from @LewisLiu007.
+
+## What it does
+
+Capture full-page screenshots of web pages via Chrome DevTools Protocol with zero dependencies. Useful for portfolios, case studies, and audit reports.
+
+## Source
+
+- Upstream: https://github.com/LewisLiu007/full-page-screenshot
+- Category: `screenshots`
+
+## How to use
+
+This catalogue entry advertises the skill in Open Design so the agent
+discovers it during planning. To run the full upstream workflow with
+its original assets, scripts, and references, install the upstream
+bundle into your active agent's skills directory:
+
+```bash
+# Inspect the upstream README for exact paths
+open https://github.com/LewisLiu007/full-page-screenshot
+```
+
+Then ask the agent to invoke this skill by name (`full-page-screenshot`) or with
+one of the trigger phrases listed in this skill's frontmatter.

package/skills/interview-me/SKILL.md

@@ -0,0 +1,64 @@
+---
+name: interview-me
+description: Use when requirements are underspecified or the user's stated goal differs from what they actually need. Extracts true intent through one-question-at-a-time dialogue. Critical for the Define phase when users have a vague idea but not a concrete spec.
+---
+
+# Interview Me
+
+## Overview
+
+Users often know what they feel without knowing what they need. This skill extracts what users actually want vs. what they think they should want. It is critical for the Define phase when requirements are underspecified or the user's stated goal differs from the real problem.
+
+**Core principle:** One question at a time. Let the user think. Don't rush to solutions.
+
+## When to Use
+
+- User says "build something" without concrete details
+- Requirements are vague, ambiguous, or contradictory
+- The stated goal feels like a solution rather than a problem
+- User says "just do X" when X seems unusual or risky
+- You suspect the user wants Y but keeps asking about Z
+- Early in Define phase before any planning or building
+
+**Don't use when:**
+- Requirements are already clear and specific
+- User explicitly says "don't ask questions, just do X"
+- This is a follow-up conversation with existing context
+
+## The Interview Flow
+
+### Step 1: Acknowledge and Set Expectations
+
+```
+"Understood — [restate what you heard]. Before I plan or build anything,
+I need to understand the problem better. I'll ask a few questions.
+If any feel off, tell me — that helps me understand the real issue."
+```
+
+### Step 2: Surface the Problem, Not the Solution
+
+Ask about the problem, not the proposed solution.
+
+```
+❌ "You want me to add a dark mode toggle, right?"
+✅ "What's the current experience that needs improving?"
+```
+
+### Step 3: One Question Per Exchange
+
+**One question. Wait for answer. Then next.**
+
+### Step 4: Identify the Real Goal
+
+The conversation is done when you can fill this template:
+
+```
+"[User] needs to [action] so that [outcome].
+Currently they [existing workaround or pain].
+The constraint is [resources, time, technology]."
+```
+
+## Related Skills
+
+- **`brainstorming`** — After interview, when user has a clear goal to explore
+- **`spec-driven-development`** — After interview, when user has a clear goal to formalize

package/skills/planning-and-task-breakdown/SKILL.md

@@ -0,0 +1,52 @@
+---
+name: planning-and-task-breakdown
+description: Use when a spec or requirements exist and need to be broken into verifiable tasks with acceptance criteria. Explicit decomposition into tasks with clear definitions of done. Distinct from writing-plans which is output-focused.
+---
+
+# Planning and Task Breakdown
+
+## Overview
+
+Explicit task decomposition into verifiable units with acceptance criteria. This skill is distinct from `writing-plans` which is output-focused (produces a plan document). This skill focuses on decomposition process — turning a spec into a sequence of implementable, testable tasks.
+
+**Core principle:** A task isn't done until it's verifiable. Every task needs a clear "done" criterion before it starts.
+
+## When to Use
+
+- A spec or requirements document exists
+- Need to break work into manageable pieces
+- Planning a multi-step implementation
+- Before `subagent-driven-development` begins
+- When "I have a plan" but the plan has no verifiable tasks
+
+**Don't use when:**
+- Requirements are still unclear → use `interview-me` first
+- No spec exists → use `spec-driven-development` first
+- Task is simple single-step → just do it, don't over-plan
+
+## The Decomposition Process
+
+### Step 1: Parse the Spec
+
+Read the spec completely before breaking it down.
+
+### Step 2: Identify Task Boundaries
+
+**Rule: One task = one responsible party = one verification point**
+
+### Step 3: Write Verifiable Tasks
+
+Each task must answer:
+- **What** is being built/modified
+- **Where** it lives (file, module, component)
+- **How to verify** it's done
+
+### Step 4: Order by Dependency
+
+Sequential, parallel, or conditional.
+
+## Relationship to Other Skills
+
+- **`interview-me`** — Used BEFORE this skill when requirements are unclear
+- **`spec-driven-development`** — Used BEFORE this skill when no spec exists
+- **`subagent-driven-development`** — Uses tasks from this skill for execution

package/skills/sora/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: sora
+description: |
+  Generate, remix, and manage short video clips via OpenAI's Sora API. Useful for cinematic shots, b-roll, and rapid concept video iteration.
+triggers:
+  - "sora"
+  - "openai video"
+  - "short video"
+  - "b roll"
+  - "cinematic clip"
+od:
+  mode: video
+  category: video-generation
+  upstream: "https://github.com/openai/skills"
+---
+
+# sora
+
+> Curated from OpenAI's skills repository.
+
+## What it does
+
+Generate, remix, and manage short video clips via OpenAI's Sora API. Useful for cinematic shots, b-roll, and rapid concept video iteration.
+
+## Source
+
+- Upstream: https://github.com/openai/skills
+- Category: `video-generation`
+
+## How to use
+
+This catalogue entry advertises the skill in Open Design so the agent
+discovers it during planning. To run the full upstream workflow with
+its original assets, scripts, and references, install the upstream
+bundle into your active agent's skills directory:
+
+```bash
+# Inspect the upstream README for exact paths
+open https://github.com/openai/skills
+```
+
+Then ask the agent to invoke this skill by name (`sora`) or with
+one of the trigger phrases listed in this skill's frontmatter.

package/skills/theme-factory/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: theme-factory
+description: |
+  Apply professional font and color themes to artifacts including slides, docs, reports, and HTML landing pages. Ships 10 pre-set themes.
+triggers:
+  - "theme factory"
+  - "apply theme"
+  - "design theme"
+  - "theme generator"
+  - "preset theme"
+od:
+  mode: design-system
+  category: design-systems
+  upstream: "https://github.com/anthropics/skills/tree/main/theme-factory"
+---
+
+# theme-factory
+
+> Curated from Anthropic's official skills repository.
+
+## What it does
+
+Apply professional font and color themes to artifacts including slides, docs, reports, and HTML landing pages. Ships 10 pre-set themes.
+
+## Source
+
+- Upstream: https://github.com/anthropics/skills/tree/main/theme-factory
+- Category: `design-systems`
+
+## How to use
+
+This catalogue entry advertises the skill in Open Design so the agent
+discovers it during planning. To run the full upstream workflow with
+its original assets, scripts, and references, install the upstream
+bundle into your active agent's skills directory:
+
+```bash
+# Inspect the upstream README for exact paths
+open https://github.com/anthropics/skills/tree/main/theme-factory
+```
+
+Then ask the agent to invoke this skill by name (`theme-factory`) or with
+one of the trigger phrases listed in this skill's frontmatter.

package/skills/web-design-guidelines/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: web-design-guidelines
+description: |
+  Web design guidelines and standards by the Vercel engineering team. Covers layout, typography, color, motion, and accessibility for product UI.
+triggers:
+  - "web design guidelines"
+  - "vercel design"
+  - "product ui standards"
+  - "design checklist"
+od:
+  mode: design-system
+  category: design-systems
+  upstream: "https://github.com/vercel-labs/skills"
+---
+
+# web-design-guidelines
+
+> Curated from the Vercel engineering team.
+
+## What it does
+
+Web design guidelines and standards by the Vercel engineering team. Covers layout, typography, color, motion, and accessibility for product UI.
+
+## Source
+
+- Upstream: https://github.com/vercel-labs/skills
+- Category: `design-systems`
+
+## How to use
+
+This catalogue entry advertises the skill in Open Design so the agent
+discovers it during planning. To run the full upstream workflow with
+its original assets, scripts, and references, install the upstream
+bundle into your active agent's skills directory:
+
+```bash
+# Inspect the upstream README for exact paths
+open https://github.com/vercel-labs/skills
+```
+
+Then ask the agent to invoke this skill by name (`web-design-guidelines`) or with
+one of the trigger phrases listed in this skill's frontmatter.

package/dist/agents/prompt-library/orchestration.d.ts

@@ -1,4 +0,0 @@
-import type { AvailableAgent, AvailableTool } from "../dynamic-agent-prompt-types";
-export declare function buildKeyTriggersSection(agents: AvailableAgent[]): string;
-export declare function buildToolSelectionTable(agents: AvailableAgent[], tools?: AvailableTool[]): string;
-export declare function buildDelegationTable(agents: AvailableAgent[]): string;