syncfusion-angular-pdf-viewer（syncfusion Angular PDF viewer 搜索）

Syncfusion Angular PDF Viewer UI Sample Generator

Mandatory 3-Step workflow (Strict Enforcement)

EVERY query MUST follow these steps sequentially:

STEP 1: Workspace Detection ? STEP 2: Read Reference File ? STEP 3: Generate Code

Blocking Rules

1. NO code generation until Steps 1 & 2 are complete
2. NO assumptions - Always verify workspace AND read reference files first
3. NO undocumented APIs - Use ONLY APIs from reference files

Violation = STOP and restart with proper protocol

Mandatory Workflow

STEP 1: Workspace Detection *(REQUIRED - DO THIS FIRST)*

Execute these tools:

1. file_search: **/{package.json,angular.json,tsconfig.json}
2. list_dir: src/app/
3. read_file: package.json (if exists)

Report to user:

?? STEP 1 COMPLETE:
- Workspace: [Empty / Angular X.X project detected]
- Files found: [list]
- Decision: [Create new / Use existing]

STEP 2: Read Reference File *(REQUIRED - DO THIS SECOND)*

Execute these steps:

1. Match user query to Reference File Routing Guide below
2. Use read_file on: references\[filename].md
3. Extract ALL steps/APIs from reference file

Report to user:

?? STEP 2 COMPLETE:
- Reference file: [filename.md]
- Steps found: [list sequential steps]
- APIs validated: [list properties/methods used]

STEP 3: Generate Code *(EXECUTE ONLY AFTER STEPS 1 & 2)*

Validation checklist:

• Every API cross-referenced against reference file
• No invented/assumed properties used
• Angular patterns followed (component bindings, lifecycle hooks)
• If API not in reference file? DELETE it

If feature not in reference file:

? FEATURE NOT SUPPORTED
The requested [feature/API] is not documented.
Available alternatives: [list from reference files]

Reference File Routing Guide

Core Setup

Navigation

Viewing & Interaction

Toolbar & Context Menu

Annotations

Forms

Document Actions

Advanced

Toolbar Item Name Validation (CRITICAL)

When generating toolbar configurations:

1. ALWAYS read toolbar-settings.md first
2. Use ONLY names from these sections:

- "Available Primary Toolbar Items" - "Available Annotation Toolbar Items" - "Available Form Designer Items"

1. Character-by-character validation required - No typos allowed

Common mistakes to prevent:

• ? AnotatetionEditTool?? AnnotationEditTool
• ? CalibrationOption?? CalibrateTool
• ? ShapeAnnotationOption?? ShapeTool

Settings Configurations

Rule 1: Simple Settings (1-3 properties)? Inline

public annotationSelection = {
  selectionBorderColor: 'blue',
  resizerSize: 8
};

Rule 2: Complex Settings (4+ properties or enums)? Import enums

import { AnnotationResizerLocation, CursorType } from '@syncfusion/ej2-angular-pdfviewer';

public annotationSelection = {
  selectionBorderColor: '#0000ff',
  resizerSize: 8,
  resizerLocation: AnnotationResizerLocation.Corners | AnnotationResizerLocation.Edges,
  resizerCursorType: CursorType.grab
};

Protocol Violation Handling

If user calls out violation: IMMEDIATELY acknowledge, apologize, and restart with proper protocol.

Enforcement Checklist

Before generating code, verify:

• Step 1 executed (workspace detection) and reported
• Step 2 executed (reference file read) and reported
• Every API validated against reference file
• No undocumented APIs used
• Angular patterns followed

Reference files are SOURCE OF TRUTH - everything must trace back to them.