Skip to content

feat: Workspace improvements for agents#2761

Open
matthewlipski wants to merge 2 commits into
vite-plusfrom
agent-markdown
Open

feat: Workspace improvements for agents#2761
matthewlipski wants to merge 2 commits into
vite-plusfrom
agent-markdown

Conversation

@matthewlipski
Copy link
Copy Markdown
Collaborator

Summary

This PR makes the repo more friendly for AI agents, and should make them more effective.

Rationale

Our workflow is very agent driven these days, so this should streamline things further.

Changes

  • AGENTS.md updated: Now also contains some general context about the project and information about writing/running/updating tests.
  • Added Claude skills:
    • create-example: Describes how to create a new example.
    • debug-skill: Describes how Claude should go about debugging in a loop of write->test in browser->verify results. Also includes details about how to navigate the playground and editor.
    • playwright-cli: Instructions for using the Playwright CLI. This is meant to support debug-skill.
  • E2E test scripts cleaned up: This was needed for a long time and made it difficult to write about testing in AGENTS.md.

Impact

N/A

Testing

N/A

Screenshots/Video

N/A

Checklist

  • Code follows the project's coding standards.
  • Unit tests covering the new feature have been added.
  • All existing tests pass.
  • The documentation has been updated to reflect the new feature

Additional Notes

N/A

@vercel
Copy link
Copy Markdown

vercel Bot commented May 20, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
blocknote Error Error May 20, 2026 10:12am
blocknote-website Error Error May 20, 2026 10:12am

Request Review

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 20, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: ff4da499-5410-461e-b05b-1e63592d080c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch agent-markdown

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@pkg-pr-new
Copy link
Copy Markdown

pkg-pr-new Bot commented May 20, 2026

Open in StackBlitz

@blocknote/ariakit

npm i https://pkg.pr.new/@blocknote/ariakit@2761

@blocknote/code-block

npm i https://pkg.pr.new/@blocknote/code-block@2761

@blocknote/core

npm i https://pkg.pr.new/@blocknote/core@2761

@blocknote/mantine

npm i https://pkg.pr.new/@blocknote/mantine@2761

@blocknote/react

npm i https://pkg.pr.new/@blocknote/react@2761

@blocknote/server-util

npm i https://pkg.pr.new/@blocknote/server-util@2761

@blocknote/shadcn

npm i https://pkg.pr.new/@blocknote/shadcn@2761

@blocknote/xl-ai

npm i https://pkg.pr.new/@blocknote/xl-ai@2761

@blocknote/xl-docx-exporter

npm i https://pkg.pr.new/@blocknote/xl-docx-exporter@2761

@blocknote/xl-email-exporter

npm i https://pkg.pr.new/@blocknote/xl-email-exporter@2761

@blocknote/xl-multi-column

npm i https://pkg.pr.new/@blocknote/xl-multi-column@2761

@blocknote/xl-odt-exporter

npm i https://pkg.pr.new/@blocknote/xl-odt-exporter@2761

@blocknote/xl-pdf-exporter

npm i https://pkg.pr.new/@blocknote/xl-pdf-exporter@2761

commit: 54806c5

When fixing a bug, the following feedback loop should be used.

1. Apply a code change that you think will fix the issue.
2. Test the change in a browser environment.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it doesn't always have to be a browser env (I think it is good to clarify the "most minimal test" rule). Like if it can solve it with a unit test that is fine & better


Before starting up a browser environment, you need to ensure the dev server is running. This can be done by checking if port 5173 is in use. If it isn't, running `vp dev` at the project root will start the server.

The Playwright CLI should be used for the browser environment. It can be used to navigate to the dev server and programmatically issue mouse clicks/keyboard inputs. If not installed, stop what you're doing and notify the user to install it.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ideally we'd link to it's docs so it can discover commands & stuff it can do

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was thinking since I added the playwright-cli skill it would be able to reference that. Though I'm not 100% sure if skills referencing other skills works.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The agent should see the frontmatter of each skill as part of the initial system prompt. So I guess it might be able to figure it out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants