fine_d

Use when a synced FineReport change must be opened in browser and checked against the expected data and layout, especially when preview URLs, login flow, and browser evidence should follow a fixed FineReport review routine instead of rediscovering the page each time.

Use when editing FineReport `.cpt` files after the datasource, target path, and creation or pull prerequisites are clear. Trigger for CPT layout, dataset XML, parameters, table headers, and cell-level report edits.

Use when a new FineReport CPT or FVS file must be created, when same-name collisions must be checked before writing, or when a template must be selected before local editing begins.

Use when FineReport datasource connections, SQL previews, field scans, or dataset XML snippets are needed before editing CPT or FVS files. Trigger whenever the request involves connection names, columns, parameters, or data validation.

Use when a remote reportlet must be pulled into the local project before comparison or editing. Trigger whenever the latest remote CPT or FVS content is required as the editing baseline.

Use when editing FineReport `.fvs` files after datasource, target path, and creation or pull prerequisites are clear. Trigger for FVS tree structure, view definitions, and grouping or aggregation changes.

Use when starting or reinitializing a FineReport project and `.codex/fr-config.json` is missing, incomplete, stale, or the user explicitly asks to regenerate the project config.

Deprecated FineReport skill kept only for compatibility. Use when reading older conversations or files that still mention fr-requirements, then immediately redirect to fr-init or fr-workflow.

Use when the current FineReport project configuration, Designer runtime, bridge package, Decision login, remote directory sample, or datasource availability must be checked before editing or syncing reportlets.

Deprecated FineReport skill kept only for compatibility. Use when older notes mention fr-template-write, then redirect to fr-create, fr-cpt, or fr-fvs instead of continuing with this mixed workflow.

Use when local FineReport reportlet changes must be pushed back to the remote runtime and verified before browser review. Trigger after CPT or FVS edits are complete and saved.

Use when starting or resuming a FineReport task in this repository and deciding which FineReport workflow skill should run next. Trigger whenever the request involves reportlets, CPT or FVS editing, FineReport sync, datasource scans, browser preview review, or project initialization.

Use when browser automation, page snapshots, screenshots, form input, console or network inspection, or FineReport preview review in this repository should run through Chrome DevTools MCP instead of ad-hoc browser exploration.