clarify things

Author: philipp-spiess

.github/CONTRIBUTING.md

@@ -42,7 +42,7 @@ If you've found a bug in Tailwind that you'd like to fix, [submit a pull request
 
 ## New features
 
-If there's a new feature you'd like to see added to Tailwind, [share your idea with us](https://github.com/tailwindlabs/tailwindcss/discussions/new?category=ideas) in our discussion forum to get it on our radar as something to consider for a future release.
+If there's a new feature you'd like to see added to Tailwind, [share your idea with us](https://github.com/tailwindlabs/tailwindcss/discussions/new?category=ideas) in our discussion forum to get it on our radar as something to consider for a future release before starting work on it.
 
 **Please note that we don't often accept pull requests for new features.** Adding a new feature to Tailwind requires us to think through the entire problem ourselves to make sure we agree with the proposed API, which means the feature needs to be high on our own priority list for us to be able to give it the attention it needs.
 

AGENT.md

@@ -0,0 +1,23 @@
+# Tailwind CSS Development Guide
+
+## Build Commands
+
+- Full build: `pnpm build`
+- Development: `pnpm dev`
+- Format code: `pnpm format`
+- Lint: `pnpm lint`
+- Run all tests: `pnpm test` (combines Rust and JS tests)
+- Run integration tests: `pnpm test:integrations`
+- Run UI tests: `pnpm test:ui`
+- Run tests in watch mode: `pnpm tdd`
+- Run a single test: `vitest --file <path-to-test-file>`
+
+## Code Style Guidelines
+
+- TypeScript-first codebase with Rust specific parts for the Oxide extractor
+- Prettier for formatting with semi: false, singleQuote: true, printWidth: 100
+- Use organized imports (prettier-plugin-organize-imports)
+- Prefer explicit typing with TypeScript interfaces
+- Cross-platform compatibility (especially Windows vs Unix line endings)
+- For text templates, use the dedicated helpers: svg, css, html, ts, js, jsx, json, yaml, txt
+- Tests use "vitest" framework with custom utilities from integrations/utils.ts