## Description
- Add docs styleguides
- Add AGENTS.md files and point CLAUDE.md file to it
- Add mastra-docs claude skill
- Improve prompts on writing docs
## Related Issue(s)
Fixes DEVED-110
## Type of Change
- [ ] Bug fix (non-breaking change that fixes an issue)
- [ ] New feature (non-breaking change that adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [X] Documentation update
- [ ] Code refactoring
- [ ] Performance improvement
- [ ] Test update
## Checklist
- [ ] I have made corresponding changes to the documentation (if
applicable)
- [ ] I have added tests that prove my fix is effective or that my
feature works
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
* **Documentation**
* Added comprehensive docs and styleguides (DOC, STYLEGUIDE, GUIDE_* ,
REFERENCE) and new AGENTS.md; reorganized docs content and contributor
workflow.
* Replaced extensive CLAUDE.md content with pointer to AGENTS.md;
cleared docs changelog and removed some legacy guideline files.
* Updated CLI/pr/changeset prompts and guidance to require multiple
changesets for multi-package changes and warn against very long
changesets.
* **Community**
* Updated Code of Conduct with expanded scope and clearer enforcement
guidance.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
---------
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
CLAUDE.md has not been updated in 7 months. There was a lot of
repetitive/outdated information in there
<!-- CURSOR_SUMMARY -->
---
> [!NOTE]
> **Low Risk**
> Low risk documentation-only change; no runtime code or build logic is
modified, but inaccurate instructions could mislead contributors if
wrong.
>
> **Overview**
> Updates `CLAUDE.md` to be shorter and more current: streamlines scope
guidance around `examples/`, refreshes build/test/lint command listings,
and removes large, repetitive documentation sections.
>
> Reworks the architecture/repo overview to reflect current package
layout (adds sections like `server-adapters/`, `e2e-tests/`,
`templates/`) and clarifies guidelines for docs, changesets, and
monorepo tooling (pnpm/Turborepo/Vitest).
>
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
2423a619be. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
* **Documentation**
* Updated and reorganized internal developer guidelines and build/test
instructions to improve clarity and completeness.
* Enhanced architecture documentation for better developer reference.
<sub>✏️ Tip: You can customize this high-level summary in your review
settings.</sub>
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Description
<!-- Provide a brief description of the changes in this PR -->
## Related Issue(s)
<!-- Link to the issue(s) this PR addresses, using hashtag notation:
Fixes#123 -->
## Type of Change
- [ ] Bug fix (non-breaking change that fixes an issue)
- [ ] New feature (non-breaking change that adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [ ] Documentation update
- [ ] Code refactoring
- [ ] Performance improvement
- [ ] Test update
## Checklist
- [ ] I have made corresponding changes to the documentation (if
applicable)
- [ ] I have added tests that prove my fix is effective or that my
feature works
---------
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Strengthens the UI Development directive in the root CLAUDE.md so that
working on playground packages requires reading their respective
CLAUDE.md files first, rather than just suggesting it.
Before: "code modifications should be made in... These packages contain
the user interface components and follow specific development standards
outlined in their respective CLAUDE.md files."
After: "you MUST read `packages/playground/CLAUDE.md` and
`packages/playground-ui/CLAUDE.md` before making any changes."
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Restructured Claude Code guidelines for frontend development by creating
centralized, reusable skills.
**What changed:**
Created two new skills in `.claude/skills/`:
- `react-best-practices` - 12 performance rules covering waterfalls,
bundle size, data fetching, re-renders, rendering, and JS patterns
- `tailwind-best-practices` - 5 rules for design system consistency
(component usage, tokens, classNames)
Simplified `CLAUDE.md` files in `packages/playground` and
`packages/playground-ui` to reference these skills instead of
duplicating content. Added `AGENTS.md` files for other AI tools.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
---------
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
## Description
Improve agent instructions and add `changeset` command
## Related Issue(s)
<!-- Link to the issue(s) this PR addresses, using hashtag notation:
Fixes#123 -->
## Type of Change
- [ ] Bug fix (non-breaking change that fixes an issue)
- [ ] New feature (non-breaking change that adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [ ] Documentation update
- [ ] Code refactoring
- [ ] Performance improvement
- [ ] Test update
## Checklist
- [ ] I have made corresponding changes to the documentation (if
applicable)
- [ ] I have added tests that prove my fix is effective or that my
feature works
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
* **Documentation**
* Expanded changeset and commit message guidelines with clearer
formatting and tone requirements.
* Added structured guidance for PR workflows to improve documentation
consistency.
* Introduced changeset writing standards to project documentation.
* **Chores**
* Updated configuration metadata across prompt files for consistency.
* Fixed code formatting in documentation.
<sub>✏️ Tip: You can customize this high-level summary in your review
settings.</sub>
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Summary
- Added references to playground CLAUDE.md files in the main
documentation locations section
- Helps developers discover the playground-specific development
guidelines
## Changes
- Added `packages/playground/CLAUDE.md` reference for playground
development standards
- Added `packages/playground-ui/CLAUDE.md` reference for component and
frontend standards
## Context
The playground packages have their own CLAUDE.md files with specific
development guidelines, but these weren't referenced in the main
CLAUDE.md documentation locations section. This makes it easier for
developers to discover these guidelines when working on the playground.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
* **Documentation**
* Added new guidance sections clarifying scope and where UI work should
be performed, plus a dedicated UI development guideline.
* Expanded documentation index to reference playground and playground UI
guideline pages.
* Editorial-only updates; no functional logic, public interfaces, or
runtime behavior were changed.
<sub>✏️ Tip: You can customize this high-level summary in your review
settings.</sub>
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
---------
Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>
## Description
`pnpm setup` is this https://pnpm.io/cli/setup, not `pnpm run setup`.
## Related Issue(s)
## Type of Change
- [ ] Bug fix (non-breaking change that fixes an issue)
- [ ] New feature (non-breaking change that adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [ ] Documentation update
- [ ] Code refactoring
- [ ] Performance improvement
- [ ] Test update
## Checklist
- [ ] I have made corresponding changes to the documentation (if
applicable)
- [ ] I have added tests that prove my fix is effective or that my
feature works
## Description
<!-- Provide a brief description of the changes in this PR -->
## Related Issue(s)
<!-- Link to the issue(s) this PR addresses, using hashtag notation:
#123 -->
## Type of Change
- [ ] Bug fix (non-breaking change that fixes an issue)
- [ ] New feature (non-breaking change that adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
- [ ] Documentation update
- [ ] Code refactoring
- [ ] Performance improvement
- [ ] Test update
## Checklist
- [ ] I have made corresponding changes to the documentation (if
applicable)
- [ ] I have added tests that prove my fix is effective or that my
feature works
---------
Co-authored-by: codesandbox-bot <codesandbot@codesandbox.io>