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…
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.
Documentation drift detection and sync specialist. Use to update docs//.md after code changes, verify broken refs, and apply patches reflecting recent diffs.
Cross-source research specialist. Freely traverses web/docs/code search, community/market signals, and academic literature to answer open questions with cited, trust-labeled, triangulated findings.
Documentation drift detection and sync specialist. Use to update docs//.md after code changes, verify broken refs, and apply patches reflecting recent diffs.
Cross-source research specialist. Freely traverses web/docs/code search, community/market signals, and academic literature to answer open questions with cited, trust-labeled, triangulated findings.
Self-sufficient analyzer of ABAP sources for the L1 step of the abapwiki knowledge base. Operates raw-only: reads the files in raw/system-library/ without MCP. Receives sapname, saptype, devclass, rawsourcepath and an artifactpath; WRITES to file a structured YAML report with narrativesections, classified dependencies…
Independent adversarial judge that verifies the L1 analysis of an ABAP object. For each claim it checks whether the cited EVIDENCE lines really prove the SENTENCE; for each dependency it applies 4 checks (line exists, active statement, type, namespace). Runs in a separate session from the author, with a different…
L2 functional researcher of the abapwiki knowledge base. For a slice (business process) it reads the members' L1 pages and the dependency graph, identifies the functional GAPS (why it exists, who launches it, semantics of the Z fields and of the magic numbers, standard integration, data lifecycle), classifies them and…
Use when building complete frontend applications across React, Vue, and Angular frameworks requiring multi-framework expertise and full-stack integration.
Review from the protocol-facing SDK contract: does this diff still model Morpho exactly? Authoritative rules live in AGENTS.md §1 (single source of truth per ABI/address and Action/Entity layering), §5 (security invariants as tests), §7 (pin ABIs and addresses in-package), and package/nested AGENTS.md files such as…
The boundary between the SDK and the chain. Authoritative rules live in AGENTS.md §1 (the Action layer is pure encode-only, no state reads), §2 (typed errors), and §5 (security invariants — chainId validation, authorization, accounting, LLTV buffer, inflation-attack guard, deposit routing). The Action-layer rule and…
Use when creating or modifying backend code: API routes, use cases, domain models, repositories, infrastructure services, or dependency injection configuration. Follows Hexagonal Architecture, DDD, and DIOD conventions.