retikz

Use when changing any retikz apps/docs content, route data, i18n, demo, SourceLinks, or schema reference before loading the matching page-type skill.

Use when retikz needs multiple independent LLMs to review the same fixed code, ADR, implementation plan, test contract, commit, or working-tree snapshot before a gate or delivery decision.

Use when an Alpha ADR needs a pre-implementation capability gate, or a Beta milestone needs code-based completeness and package-boundary auditing.

Use when planning a retikz architecture direction, version roadmap, or alpha feature that may need a long-lived ADR before implementation.

Use when retikz work is primarily refactoring, reorganization, renaming cleanup, modularization, or internal simplification and should start from a reviewed implementation plan before code changes.

Use when retikz implementation, adversarial testing, and docs are complete, and an ADR or beta TODO needs changelog, contract consistency review, roadmap status updates, or final human acknowledgement.

Use when retikz alpha-stage work needs to execute an ADR-backed feature through long-lived design, reviewed implementation planning, code, adversarial testing, documentation, and wrapup.

Use when retikz beta-stage roadmap TODO work needs refactoring, renaming, test hardening, error-message, performance, or documentation cleanup after alpha feature work.

Use when retikz work is a large, long-running, batch, multi-commit, or context-compaction-prone task that needs a durable execution reference, staged commit review, and final whole-change review.

Use when 发布或准备发布 retikz npm 包、核对发布版本与 git tag，或执行 alpha、beta、rc、stable 发版

Use when converting a finished retikz blog MDX article into external-platform Markdown plus captured SVG assets.

Use when implementing a retikz alpha ADR or beta TODO after design or roadmap scope is fixed, including schema, public API, compile, adapter, test, and docs-visible behavior changes.

Use when a retikz ADR or beta TODO changes data structures, public interfaces, compile semantics, adapter behavior, renderer output, or docs-visible behavior and needs a traceable behavior-to-test contract before implementation or final acceptance.

Use when retikz release-candidate work needs API-freeze enforcement, bug convergence, docs completion, migration guidance, packaging validation, or rc/stable readiness checks.

Use when explaining how a retikz feature, module, pipeline, runtime, adapter, registry, compiler, or interaction works with a concise implementation logic figure. Always read docs-figure-contract first.

Use when a retikz ComponentPreview has controls, a *.controls.ts contract, usePreviewControls, presets, or a playground that replaces repeated parameter-only demos.

Use when independently reviewing retikz docs pages or docs diffs for page-type structure, reader clarity, source-backed API claims, demo coverage, bilingual parity, and navigation integrity.

Use when drawing or reviewing architecture, flow, concept, schema, API, or implementation-explanation figures in retikz apps/docs; covers dogfood, ComponentPreview hideCode, file shape, visual vocabulary, responsive layout, node/edge conventions, and validation. Specialized figure skills such as docs-figure-logic must read this first.

Use when writing, restructuring, translating, or reviewing an apps/docs component page for an @retikz/standard Tier 2 composite such as Grid, Axes, or Frame.

Use when writing or editing component pages under a module's apps/docs component contents, excluding pages marked as extension guides.

Use when changing retikz Zod/IR schema code, schema-derived public types, schema field ordering, schema validation/refinement, schema JSDoc/describe text, schema registry docs, or tests that assert schema behavior in core, plot, adapters, docs, or tests.

Use when changing retikz shared layer code, dependency-free vocabulary, anchor/side helpers, pure shared utilities, mapping tables, shared ValueOf/AssertEqual-style types, or imports that should route through shared.

Use when changing retikz package file layout, dependency direction, layer placement, common constants/types/utils/index file organization, or deciding which standard layer skill to load.

retikz 交叉测试 / 缺陷挖掘技能。用于基于 packages 下现有实现和已有测试补充边缘场景测试，以找出现有实现缺陷为目标，不能凭空编造需求；同时从真实使用者角度评估 API、错误信息、文档契约、可诊断性与可改进点。适用于 alpha/beta 任意阶段的独立质量审计、回归测试补强、adversarial 测试、用户视角体验评估，以及把发现沉淀为测试、问题报告或 _notes/decisions TODO。

Use when a retikz feature or user-visible behavior needs apps/docs updates, demos, API tables, sidebar or i18n changes after implementation, or when the change itself is documentation-first.

Use when auditing a retikz module or subsystem read-only to find beta cleanup, refactor, correctness, schema, test, or docs consistency findings before deciding which items become roadmap TODOs.

Use when retikz alpha implementation tests have passed but red or yellow changes still need adversarial validation against edge cases, JSON IR stability, and contract robustness before documentation.

Use when auditing an existing retikz test suite, module test directory, or docs tests for stale, duplicate, implementation-coupled, migration-only, or temporary cases; classify which tests remain durable contract or regression coverage and produce evidence-backed cleanup recommendations before refactoring tests.

Use when planning, writing, translating, or reviewing a programmer-facing retikz blog article under apps/docs/src/modules/docs/contents/blog.

Use when writing or editing a leaf apps/docs concept page to explain a module-specific mental model, boundary, or architecture.

Use when writing or editing step-by-step showcase pages under a module's apps/docs examples contents.

Use when documenting a retikz Definition/defineXxx extension path, registry injection, lookup, validation, or built-in/custom shared consumption, either as a standalone guide or an owner-page section.

Use when writing a landing page for a docs data node with children, such as a component family or reference family navigation hub.

Use when changing retikz contract layer code, XxxDefinition types, defineXxx helpers, DefinitionInput/AnyDefinition types, registry discriminators, extension contracts, author-facing capability APIs, or definition context naming.

Use when changing retikz providers layer code, builtin definitions, registry resolvers, BUILTIN_* collections, reserved or removed keys, custom definition merging, provider diagnostics, or implementation of contract capabilities.

Use when changing retikz pipeline or compile code, lowering, registry consumption, compile options, plot expand stages, core compileToScene behavior, ResolvedXxx types, warnings, or IR-to-primitive/Kernel-IR orchestration.

Use when editing apps/docs React components, shared components, layout components, docs UI code, or shadcn-based interface code; covers component shape, props typing, UI library usage, placement, imports, and validation.

retikz docs 站代码与文件结构基础规范。Use when changing apps/docs source organization, module/component folder layout, docs-specific utils/types/constants placement, React context/store/hooks naming, or when deciding whether code belongs in modules/docs, layout, components/shared, store, or lib.