mirror of
https://github.com/CopilotKit/CopilotKit.git
synced 2026-09-14 16:26:20 +08:00
Benjamin Taylor
b77ebb435f
The repo migrated off @changesets/* to conventional-commit-driven releases (scripts/release/ reads commit subjects from git log <lastTag>..HEAD), but .changeset/ has been removed twice already (5afa55f067,1e5ba689e0) and five open PRs currently carry changeset files again. Two mechanisms keep feeding it: contributor forks whose default branch still has the pre-cleanup .changeset/ debris, and plain convention inference — the repo reads as a Changesets repo (pnpm monorepo, Changesets-formatted CHANGELOG.md files, "chore: release" PRs) and nothing anywhere said otherwise. - CONTRIBUTING.md: explain that we used Changesets, what replaced it, and what to do instead (a good conventional commit subject). - AGENTS.md / CLAUDE.md: same rule for coding agents, which author most of these PRs and don't read CONTRIBUTING.md. - static / check binaries: fail on added .changeset/* files, so this stops depending on review catching it. Filters on added/modified only, so a PR that deletes stale changesets still passes. - .oxfmtrc.json: drop the ignore entry for the long-gone vendored .github/actions/changesets-action, a stale "we use changesets" signal. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
38 lines
3.5 KiB
Markdown
38 lines
3.5 KiB
Markdown
<!-- nx configuration start-->
|
|
<!-- Leave the start & end comments to automatically receive updates. -->
|
|
|
|
# General Guidelines for working with Nx
|
|
|
|
- When running tasks (for example build, lint, test, e2e, etc.), always prefer running the task through `nx` (i.e. `nx run`, `nx run-many`, `nx affected`) instead of using the underlying tooling directly
|
|
- You have access to the Nx MCP server and its tools, use them to help the user
|
|
- When answering questions about the repository, use the `nx_workspace` tool first to gain an understanding of the workspace architecture where applicable.
|
|
- When working in individual projects, use the `nx_project_details` mcp tool to analyze and understand the specific project structure and dependencies
|
|
- For questions around nx configuration, best practices or if you're unsure, use the `nx_docs` tool to get relevant, up-to-date docs. Always use this instead of assuming things about nx configuration
|
|
- If the user needs help with an Nx configuration or project graph error, use the `nx_workspace` tool to get any errors
|
|
- For Nx plugin best practices, check `node_modules/@nx/<plugin>/PLUGIN.md`. Not all plugins have this file - proceed without it if unavailable.
|
|
|
|
<!-- nx configuration end-->
|
|
|
|
> Working under `showcase/`? Read `showcase/AGENTS.md` FIRST — it defines the non-negotiable iron rules for showcase cells.
|
|
|
|
# CopilotKit
|
|
|
|
AI agent framework with three layers: **Frontend** (React/Angular/Vanilla) → **Runtime** (Express/Hono) → **Agent** (LangGraph/CrewAI/BuiltIn/Custom), communicating via the AG-UI protocol (event-based SSE).
|
|
|
|
## Essentials
|
|
|
|
- **Nx monorepo** — always run tasks through `nx` (`nx run`, `nx run-many`, `nx affected`), never the underlying tooling directly.
|
|
- **Flat package structure** — all packages live directly under `packages/` (no `v1/` or `v2/` subdirectories). Every package uses the `@copilotkit/` scope.
|
|
- **Simplicity** — prefer the simplest correct solution. For non-trivial changes, consider if there's a cleaner approach before committing.
|
|
- **No changesets** — releases are conventional-commit-driven (`scripts/release/` reads commit subjects). This repo migrated off Changesets; never create `.changeset/*` files — nothing consumes them and CI fails on them. Describe the change in the commit subject instead, and leave `package.json` versions and `CHANGELOG.md` files to the release tooling.
|
|
- **Worktrees** — always work in a git worktree for isolation. See [Git & PRs](.claude/docs/git.md) for the full workflow.
|
|
- **Documentation lives in shell-docs** — author all CopilotKit docs in `showcase/shell-docs/src/content/`. The top-level `docs/` path is only a symlink to `showcase/shell-docs/`; never recreate the old `docs/content/docs/` tree. AG-UI protocol docs are authored upstream in `ag-ui-protocol/ag-ui`, not here. See [Documentation](.claude/docs/documentation.md).
|
|
|
|
## Reference (read when relevant to your task)
|
|
|
|
- [Architecture & Packages](.claude/docs/architecture.md) — package roles, request lifecycle, core concepts (AG-UI, ProxiedAgent, AgentRunner, tools, context, multi-agent)
|
|
- [Hook Development](.claude/docs/hooks.md) — checklist for creating new hooks (docs, tests, JSDoc)
|
|
- [Workflow & Process](.claude/docs/workflow.md) — when to plan, when to fix autonomously, verification, self-improvement loop, this should be your default mindset when working on any task
|
|
- [Git & PRs](.claude/docs/git.md) — worktree workflow, branching, creating PRs
|
|
- [Documentation](.claude/docs/documentation.md) — where to author docs (CopilotKit → shell-docs; AG-UI → upstream); `docs/` is retired
|