axure-export-workflow

Axure Export Fix Workflow

This Skill only handles Export Axure scenarios for code fixes and compliance refactoring, and does not handle third-party exports (such as Figma).

Applicable Scenarios

• The user triggers a code-review failure before "Export to Axure"
• The code needs to quickly pass the current specification check
• The Axure mode header annotation marker needs to be added

Goals

1. Fix error issues first, then handle warning
2. Complete the refactoring without changing business functionality
3. Make the target file pass the existing detection pipeline

Fixed Execution Process (Low Freedom)

Step 1: Lock the modification scope

• Only modify the target file that reported errors (usually src/components/<name>/index.tsx or src/prototypes/<name>/index.tsx）
• Do not proactively refactor unrelated code
• Do not modify code related to third-party exports

Step 2: Fix check items by priority

• First fix all error(must pass)
• Then handle warning(recommended to fix)
• Every fix must keep the original functionality and interaction behavior consistent

Step 3: Complete the header annotations (Axure mode)

If the file is used for Axure export refactoring, the header annotations must include:

• @name
• @mode axure
• Skill path in the reference materials:/skills/axure-export-workflow/SKILL.md
• The default export name must be Component(use export default Component）

The following template can be used:

/**
 * @name 组件或页面名称
 * @mode axure
 *
 * 参考资料：
 * - /rules/development-guide.md
 * - /skills/axure-export-workflow/SKILL.md
 * - /rules/axure-api-guide.md (如需集成 Axure API)
 */

Step 4: Axure API handling strategy

• The Axure API is optional
• Do not forcibly introduce forwardRef<AxureHandle, AxureProps>
• Only integrate according to axure-api-guide.md when the requirements explicitly demand Axure interaction capabilities

Step 5: Self-check before delivery

• All errors have been fixed
• Warnings have been evaluated and fixed as much as possible
• The header annotations already include @mode axure and the Skill path
• The file can pass the current pre-export check logic

Non-goals (Do not do)

• Do not extend to Figma or other third-party export pipelines
• Do not change the build plugin and check rule strategy
• Do not perform large-scale style rewrites or architectural refactoring