modules
01Agent
These guide provide an overview of how to use our agent classes.
202 tagged framework, measured the same way as everything else here.
Browse within: compliance 56cybersecurity 56ethical-hacking 56best-practices 21coding-standards 21generative-ai 21chatbot 16discord 16hot-module-replacement 16ai-assistant 15typescript 14inkline 11sass 11ui 11
Agent
These guide provide an overview of how to use our agent classes.
Agent
Having proper tool abstractions is at the core of building agentic systems in LlamaIndex. Defining a set of Tools is similar to defining any API interface, with the exception that these Tools are meant for agent rather than human use. We allow users to define both a Tool as well as a ToolSpec containing a series of…
Agent
Turn shot-plan.json into one renderable HyperFrames composition (compositions/index.html). Everything stays in the HF ecosystem — HTML is the source of truth; a single paused GSAP timeline carries all motion; the engine seeks it. Category-specific build rules live in categories/ /module.md; this file is the shared…
Agent
Turn a request into a shot-plan.json for a short (3–30s) design-led motion graphic. You run in two parts around the asset-sourcing step: Part 1 (plan) before sourcing, Part 2 (design) after. You do NOT write composition code — that's the Builder. Schema: references/shot-plan-ir.md.
Agent
Perform snapshot QA and one in-place repair pass. Dispatch only when Step 5 lint, check, or snapshot review reports a defect. The orchestrator owns final approval and render; this agent never renders.
Agent
This project uses the Switchboard protocol for cross-IDE agent collaboration.
Agent Claude Code
Use this agent when the user wants to simplify, refactor, or optimize existing code for better readability, maintainability, and performance. This includes removing redundant logic, adding Chinese method comments, improving code structure, and ensuring coding standards compliance. Examples:\n\n- User…
Agent Claude Code
Use this agent ONLY when explicitly instructed by a skill (e.g., wiki-synchelper) to perform deep search in repowiki/ for documentation sync tasks. Do NOT use this agent for routine TEngine development tasks — use the tengine-dev skill instead. This agent is NOT a general-purpose TEngine reference tool.
Agent
Agents are the core building blocks of the Video Agent system. They are responsible for processing input messages and generating output messages.
Agent
Seat: the design language. Owns: ui/components/ — the single-source component catalog: headless parts, styled compositions, .styleframe.ts styling, colocated tests. (Story files under stories/ are @herald's craft.).
Agent
Seat: verification machinery. Owns: testing/e2e/ (the Playwright visual-parity suite) and tooling/test-utils/ (the cross-target harnesses) — plus a roving audit commission.
Agent
Seat: the shop window. Owns: component stories (ui/components/src/components//stories/), tooling/storybook/ (defineStories + the CSF generator), apps/storybook/ (the :6100 aggregator), the inkline-starter- repos (to be created), examples, benchmark publishing, release-notes drafts.
Agent
Use this agent when making structural decisions: database schema changes, API contract design, service boundaries, dependency choices, or any change that affects the system's fundamental architecture. Also use when evaluating technical debt or refactoring proposals. Context: User wants to add a new domain entity user…
Agent
Use this agent before shipping, merging, or deploying changes. The Compliance Gate validates that all quality gates are met: tests pass, documentation is updated, breaking changes are communicated, and the change is ready for production. Context: User wants to merge a feature branch user: "I think this PR is ready to…
Agent
Use this agent when working on security-sensitive code, handling credentials, modifying authentication/authorization, processing user input, or making changes that could introduce vulnerabilities. Also use for risk assessment of architectural changes. Context: User is implementing payment processing user: "I've added…
Agent Claude Code
The Genblaze Maintainer — autonomous guardian of the Genblaze repo. Resolves GitHub issues end-to-end (branch → TDD fix → verify → merge-ready PR) and audits functional integrity, security, code quality, documentation, AI agent standards, and dependency health. Invoke with an issue number to fix it, with no prompt to…
Agent
AppSec specialist who secures the software development lifecycle through threat modeling, secure code review, SAST/DAST integration, and developer security education that makes secure code the default.
Agent
Senior management consulting specialist for competitive analysis, market entry strategy, business model design, growth planning, organizational strategy, and strategic decision-making — translating complex market dynamics into clear, actionable strategies that create sustainable competitive advantage.
Agent
Expert change management specialist using ADKAR, Kotter, and Prosci frameworks to guide organizations through technology implementations, restructuring, culture transformation, and M&A integration — managing resistance, building adoption, and ensuring changes stick long after go-live.
Agent
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
Agent
Issues and specs for this repo live as GitHub issues. Use the gh CLI for all operations.
Agent
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
Agent Codex
Delivery validation coordinator. Activated at Tier 2+ only (Tier 1 skips Red Team). Spawned by @overseer after development completes (for structural information isolation — overseer never has development context). Independently verifies the delivered product works correctly by dispatching validators…
Agent Codex
Independent quality gate authority. Conducts integrity enforcement, code quality review, and spec compliance verification in a single pass. Read-only — produces verdicts, never code. Its FAIL cannot be overridden by any agent; only the user can override.