CATLASS Operator Design

Core Workflow

Requirement Analysis → Read catlass Repository → Component Selection → Output Design Document

Prerequisites

Check Item	Description
catlass Repository	Must be able to access `catlass/` (including `include/` and `examples/` ) under OPS_PROJECT_ROOT
Mandatory References	Must read the `references/` files of this skill before design

Mandatory References

File	Purpose
design-document.md	Design document template
matmul-templates.md	Template list and selection guide
epilogue-components.md	Epilogue component classification and combination mode
custom-epilogue.md	Custom Epilogue contract

Operator Naming (Mandatory)

op_name
(snake_case) must contain the substring
catlass
, e.g.:

catlass_matmul_add

catlass_fused_gemm_bias

Prohibited to use short names that easily conflict with frameworks or other vendors' operators alone (such as
```
matmul_add
```
,
```
gemm_add
```
)
OpDef / Class Name (CamelCase) must map consistently with the directory name, e.g.:
```
CatlassMatmulAdd
```
,
```
ops/catlass_matmul_add/
```

Selection and Adaptation Principles

Determine the template to use from catlass example and include, do not copy the entire example into the operator project
Most operator projects are based on msopgen small projects, and the Host call code in examples needs to be rewritten into the op_host/op_kernel separation structure in the project
Only output selection decisions during the design phase; code is generated by code-gen

NEVER / ALWAYS

NEVER: Finalize the design with an operator name that does not contain

catlass

; copy the entire example verbatim; write large code blocks in the design document; speculate on requirements when information is insufficient

ALWAYS: The operator name contains

catlass

, and the directory name maps consistently with the class name; ask questions if conditions are unclear; ensure the catlass repository exists and read its documents and code before design; use selection tables to describe components in the design document

Requirement Input

Users may state their requirements directly or not. When executing this skill: If you believe information is insufficient, continue to ask questions.

Information to confirm:

op_name

(must contain catlass), functional key points, I/O and dtype, layout, target SoC, reference example (if any), constraints.

Requirement Analysis

Confirm op_name
: must contain
catlass
Extract: operator function, mathematical formula, I/O, dtype, layout, target SoC, constraints

Read catlass and Select Components

Read the catlass repository: documents and code under
```
examples/
```
and
```
include/
```
Find similar examples by function in
```
examples/
```
, and specify in the design document: the path of the selected example and the reason for selection
If there is no exact match: based on matmul-templates.md and existing samples in the repository, explain the workaround
Epilogue: Search in epilogue-components.md and
```
catlass/include/catlass/epilogue/tile/
```
; when there is no existing Tile, write the design contract first according to custom-epilogue.md

Component Selection

Record the selection results in the design document using a concept table, do not write code.

The design document must explicitly include the selection table: ArchTag, BlockMmad (L1/L0 TileShape, data type), BlockEpilogue (Tile/Block components for each link), BlockScheduler, Kernel type.

Output Design Document

Document Chapter Requirements

Overview: Function, scenario, mathematical formula
Input/Output Information Table: Variable name, data type, Shape, layout, description
Core Component Selection: Describe components at each layer using the selection table
Reference Example and Template Selection: Selected example, reason for selection
TilingKey Branch Design: Conditions corresponding to each key and content of Kernel branches
Workspace: Source of size calculation logic
Interface and Usage: aclnn interface, Host Tiling process, Kernel entry concept
Scalability: Replaceable components
Implementation Outline: Key points on Host side and Kernel side

Output Format

The design document must be an independent Markdown file, recommended to be named

design_<op_name>.md

, and stored in USER_OP_PROJECT or the path specified by the user.

Quality Verification

Design Document Checklist

The operator name contains
```
catlass
```
, and the snake_case directory name matches the CamelCase class name
Contains a complete input/output information table
Core component selection is clear: ArchTag, BlockMmad, BlockEpilogue, BlockScheduler, Kernel
Reference example is specified, and the reason for selection is clear
TilingKey branch design is listed
Delivery path USER_OP_PROJECT is clear

Reference Materials

File	Purpose
design-document.md	Design document template and chapter specifications
matmul-templates.md	Template list and selection guide
epilogue-components.md	Epilogue component classification and selection
custom-epilogue.md	Design contract for custom Tile Epilogue
catlass/examples/	Development forms and references for various templates
catlass/docs/3_API/gemm_api.md	Gemm API layered model, component comparison table

catlass-operator-design

NPX Install

Tags

SKILL.md Content (Chinese)