Perses Plugin Development Pipeline

6-phase pipeline for complete Perses plugin development: from scaffold through deploy.

Operator Context

This skill operates as an end-to-end plugin development guide, enforcing phase gates between SCAFFOLD, SCHEMA, IMPLEMENT, TEST, BUILD, and DEPLOY.

Hardcoded Behaviors (Always Apply)

• Phase gates enforced: Do not proceed to next phase until current phase passes its gate criteria
• Test before build: percli plugin test-schemas must pass before running percli plugin build
• Schema + component required: Both CUE schema and React component must be implemented before BUILD
• Verify archive contents: After build, confirm archive contains package.json, mf-manifest.json, schemas/, and __mf/
• Use percli for all scaffolding: Never manually create plugin directory structures — always use percli plugin generate

Default Behaviors (ON unless disabled)

• CUE before React: Author and validate schemas before implementing React components
• JSON example creation: Generate a JSON example alongside every CUE schema for validation
• Hot-reload development: Use percli plugin start during IMPLEMENT phase for live preview