verify

Verifies and debugs web-editor sandbox apps in a Next.js monorepo.

Updated Mar 26, 2024
One-click install
npx skills add https://github.com/84000/84000-apps --skill verify-84000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/84000/84000-apps/tree/main/apps/web-editor/.claude/skills/verify
Command: npx skills add https://github.com/84000/84000-apps --skill verify-84000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the difficulty of verifying complex editor changes in a local development environment by providing a structured workflow for launching, testing, and debugging the web-editor sandbox.

Core Features & Use Cases

  • Sandbox Orchestration: Provides commands to launch the web-editor with proper environment variable configuration and logging.
  • Runtime Assertion: Offers guidance on using Playwright and internal controller objects to verify editor state and performance metrics.
  • Deployment Safety: Includes pre-push checklists to ensure type safety and prevent SSR module evaluation crashes in the main application.

Quick Start

Run the verify skill to launch the web-editor development server and prepare the environment for testing your editor changes.

Frequently Asked Questions about verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify TipTap editor changes in a Next.js monorepo?

You can verify TipTap editor changes by launching the web-editor sandbox within your Next.js monorepo, using automated browser-based assertions to validate component state and performance metrics.

What's the best way to debug web-editor sandbox interactions?

Debugging web-editor sandbox interactions is best achieved by using Playwright alongside internal controller objects to assert editor state and monitor performance during local development.

How do I test SSR compatibility for TipTap components before deployment?

Testing SSR compatibility involves running pre-push checklists that validate type integrity and prevent module evaluation crashes in the main Next.js application before production deployment.

Can I use Playwright to monitor passage stack performance in a web editor?

Yes, you can use Playwright to perform runtime assertions and monitor passage stack interactions, ensuring performance metrics meet expected thresholds within the sandbox environment.

Why does my web-editor sandbox crash during Next.js SSR module evaluation?

Sandbox crashes during SSR module evaluation often occur due to type integrity issues or missing environment variables, which pre-push deployment safety checklists are designed to catch and prevent.

What environment setup is needed to launch a Next.js web-editor sandbox?

Launching the web-editor sandbox requires proper environment variable configuration and logging setup within the Next.js monorepo to successfully orchestrate the development server for testing.