{"owner":"fabricjs","repo":"fabric.js","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md"],"skills":{"AGENTS.md":"# AGENTS.md instructions for /Users/andreabogazzi/develop/fabric.js\n\nThis file defines how coding agents should operate in this repository.\n\n## Project\n\n- Repository: `fabricjs/fabric.js`\n- Language: TypeScript/JavaScript\n- Package manager: `npm`\n- Runtime: Node `>=20`\n- Main test stacks: `vitest` (unit) and `playwright` (e2e)\n\n## Repository Priorities\n\n- Keep changes focused and minimal.\n- Preserve existing architecture and naming style.\n- Avoid broad refactors unless explicitly requested.\n- Prefer fixing root causes over adding workarounds.\n\n## Setup\n\nRun from repo root:\n\n```bash\npnpm install\n```\n\n## Common Commands\n\n- Build: `pnpm run build`\n- Fast build: `pnpm run build:fast`\n- Typecheck: `pnpm run typecheck`\n- Lint: `pnpm run lint`\n- Format check: `pnpm run prettier:check`\n- Format write: `pnpm run prettier:write`\n- Unit tests (node): `pnpm run test:vitest`\n- Unit tests with coverage: `pnpm run test:vitest:coverage`\n- E2E tests: `pnpm run test:e2e`\n- E2E typecheck: `pnpm run playwright:typecheck`\n\n## Testing Expectations\n\n- Add or update tests for behavior changes.\n- Prefer targeted test runs while iterating, then run relevant full suites before finalizing.\n\n## Code Style\n\n- Follow existing project style and patterns.\n- Keep imports stable; do not reorder unless necessary.\n- Use concise comments only when code is not obvious.\n- Avoid unrelated formatting-only diffs in touched files.\n\n## PR and Changelog Workflow\n\n- Use clear, short PR titles.\n- Prefer conventional-commit style in titles when possible:\n  - `feat`, `fix`, `docs`, `ci`, `test`, `refactor`, `chore`\n- Add `close #<issue-num>` in PR body only when an issue number exists; if the user states there is no issue, omit it.\n- Ensure `CHANGELOG.md` (`## [next]`) is updated for notable changes.\n- Keep changelog entry style consistent with existing lines.\n\n## In-Repo Skills\n\nAgents should check and use repository skills when tasks match.\n\nAvailable skill:\n\n- `fabricjs-open-pr`\n  - Path: `.codex/skills/fabricjs-open-pr/SKILL.md`\n  - Use when opening PRs for this repository.\n  - Handles PR title/body quality, optional `close #<issue-num>`, changelog entry, and predicted PR number flow.\n\n## Skill Trigger Guidance\n\nUse the `fabricjs-open-pr` skill when any of these apply:\n\n- User asks to open/create a PR.\n- User asks to prepare PR metadata (title/body/changelog).\n- User asks to include issue-closing syntax like `close #123`.\n\n## Git Safety\n\n- Never discard user changes unless explicitly asked.\n- Do not use destructive git commands without explicit instruction.\n- Commit only files relevant to the requested task.\n\n## Communication\n\n- Be concise and factual.\n- Surface assumptions and blockers early.\n- When something cannot be verified locally, state that clearly.\n"},"files":{"AGENTS.md":"# AGENTS.md instructions for /Users/andreabogazzi/develop/fabric.js\n\nThis file defines how coding agents should operate in this repository.\n\n## Project\n\n- Repository: `fabricjs/fabric.js`\n- Language: TypeScript/JavaScript\n- Package manager: `npm`\n- Runtime: Node `>=20`\n- Main test stacks: `vitest` (unit) and `playwright` (e2e)\n\n## Repository Priorities\n\n- Keep changes focused and minimal.\n- Preserve existing architecture and naming style.\n- Avoid broad refactors unless explicitly requested.\n- Prefer fixing root causes over adding workarounds.\n\n## Setup\n\nRun from repo root:\n\n```bash\npnpm install\n```\n\n## Common Commands\n\n- Build: `pnpm run build`\n- Fast build: `pnpm run build:fast`\n- Typecheck: `pnpm run typecheck`\n- Lint: `pnpm run lint`\n- Format check: `pnpm run prettier:check`\n- Format write: `pnpm run prettier:write`\n- Unit tests (node): `pnpm run test:vitest`\n- Unit tests with coverage: `pnpm run test:vitest:coverage`\n- E2E tests: `pnpm run test:e2e`\n- E2E typecheck: `pnpm run playwright:typecheck`\n\n## Testing Expectations\n\n- Add or update tests for behavior changes.\n- Prefer targeted test runs while iterating, then run relevant full suites before finalizing.\n\n## Code Style\n\n- Follow existing project style and patterns.\n- Keep imports stable; do not reorder unless necessary.\n- Use concise comments only when code is not obvious.\n- Avoid unrelated formatting-only diffs in touched files.\n\n## PR and Changelog Workflow\n\n- Use clear, short PR titles.\n- Prefer conventional-commit style in titles when possible:\n  - `feat`, `fix`, `docs`, `ci`, `test`, `refactor`, `chore`\n- Add `close #<issue-num>` in PR body only when an issue number exists; if the user states there is no issue, omit it.\n- Ensure `CHANGELOG.md` (`## [next]`) is updated for notable changes.\n- Keep changelog entry style consistent with existing lines.\n\n## In-Repo Skills\n\nAgents should check and use repository skills when tasks match.\n\nAvailable skill:\n\n- `fabricjs-open-pr`\n  - Path: `.codex/skills/fabricjs-open-pr/SKILL.md`\n  - Use when opening PRs for this repository.\n  - Handles PR title/body quality, optional `close #<issue-num>`, changelog entry, and predicted PR number flow.\n\n## Skill Trigger Guidance\n\nUse the `fabricjs-open-pr` skill when any of these apply:\n\n- User asks to open/create a PR.\n- User asks to prepare PR metadata (title/body/changelog).\n- User asks to include issue-closing syntax like `close #123`.\n\n## Git Safety\n\n- Never discard user changes unless explicitly asked.\n- Do not use destructive git commands without explicit instruction.\n- Commit only files relevant to the requested task.\n\n## Communication\n\n- Be concise and factual.\n- Surface assumptions and blockers early.\n- When something cannot be verified locally, state that clearly.\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"# AGENTS.md instructions for /Users/andreabogazzi/develop/fabric.js\n\nThis file defines how coding agents should operate in this repository.\n\n## Project\n\n- Repository: `fabricjs/fabric.js`\n- Language: TypeScript/JavaScript\n- Package manager: `npm`\n- Runtime: Node `>=20`\n- Main test stacks: `vitest` (unit) and `playwright` (e2e)\n\n## Repository Priorities\n\n- Keep changes focused and minimal.\n- Preserve existing architecture and naming style.\n- Avoid broad refactors unless explicitly requested.\n- Prefer fixing root causes over adding workarounds.\n\n## Setup\n\nRun from repo root:\n\n```bash\npnpm install\n```\n\n## Common Commands\n\n- Build: `pnpm run build`\n- Fast build: `pnpm run build:fast`\n- Typecheck: `pnpm run typecheck`\n- Lint: `pnpm run lint`\n- Format check: `pnpm run prettier:check`\n- Format write: `pnpm run prettier:write`\n- Unit tests (node): `pnpm run test:vitest`\n- Unit tests with coverage: `pnpm run test:vitest:coverage`\n- E2E tests: `pnpm run test:e2e`\n- E2E typecheck: `pnpm run playwright:typecheck`\n\n## Testing Expectations\n\n- Add or update tests for behavior changes.\n- Prefer targeted test runs while iterating, then run relevant full suites before finalizing.\n\n## Code Style\n\n- Follow existing project style and patterns.\n- Keep imports stable; do not reorder unless necessary.\n- Use concise comments only when code is not obvious.\n- Avoid unrelated formatting-only diffs in touched files.\n\n## PR and Changelog Workflow\n\n- Use clear, short PR titles.\n- Prefer conventional-commit style in titles when possible:\n  - `feat`, `fix`, `docs`, `ci`, `test`, `refactor`, `chore`\n- Add `close #<issue-num>` in PR body only when an issue number exists; if the user states there is no issue, omit it.\n- Ensure `CHANGELOG.md` (`## [next]`) is updated for notable changes.\n- Keep changelog entry style consistent with existing lines.\n\n## In-Repo Skills\n\nAgents should check and use repository skills when tasks match.\n\nAvailable skill:\n\n- `fabricjs-open-pr`\n  - Path: `.codex/skills/fabricjs-open-pr/SKILL.md`\n  - Use when opening PRs for this repository.\n  - Handles PR title/body quality, optional `close #<issue-num>`, changelog entry, and predicted PR number flow.\n\n## Skill Trigger Guidance\n\nUse the `fabricjs-open-pr` skill when any of these apply:\n\n- User asks to open/create a PR.\n- User asks to prepare PR metadata (title/body/changelog).\n- User asks to include issue-closing syntax like `close #123`.\n\n## Git Safety\n\n- Never discard user changes unless explicitly asked.\n- Do not use destructive git commands without explicit instruction.\n- Commit only files relevant to the requested task.\n\n## Communication\n\n- Be concise and factual.\n- Surface assumptions and blockers early.\n- When something cannot be verified locally, state that clearly.\n","category":"root","tokens":691}]}