docs(agents): Remove duplicated build commands and rules

AGENTS.md is force-read at the start of every session, so anything stated
there costs context on every task. Several rules had accumulated multiple
copies of themselves within that one file.

`spotlessApply`/`apiDump` was stated five times in AGENTS.md; it is now
stated once as a command and once as a workflow step, with the underlying
facts (Spotless enforces formatting, `.api` files are generated) kept where
they belong. The Testing command block is dropped in favour of the `test`
skill, which already resolves the per-module task and the unit-vs-system
split and does not drift. The Repository Skills bullet list restated skill
descriptions that the harness already injects, so it is now a pointer.

In the rules, `new_module.mdc`'s "Important Notes" was a verbatim
restatement of the AGENTS.md contributing guidelines, and `api.mdc` repeated
the opt-in-by-default rule in passing; both now defer to their canonical
homes.

No guidance is lost — every removed line is still stated somewhere that is
loaded when it applies.

Author: runningcode

.cursor/rules/api.mdc

@@ -34,7 +34,7 @@ Public API is tracked via `.api` files generated by the [Binary Compatibility Va
 - `SentryAndroidOptions` — Android-specific options
 - Integration modules may add their own (e.g. `SentrySpringProperties`)
 
-New features must be **opt-in by default** — add a getter/setter pair to the appropriate options class.
+See the `options` rule for how to add and wire up a new option.
 
 ### Internal Classes (Not Public API)
 

.cursor/rules/new_module.mdc

@@ -79,10 +79,3 @@ Remind the user to perform the following tasks after the module is merged and re
 - Use kebab-case for module names: `sentry-{module-name}`
 - Follow existing patterns: `sentry-okhttp`, `sentry-apollo-4`, `sentry-spring-boot`
 - For version-specific modules, include the version: `sentry-apollo-3`, `sentry-apollo-4`
-
-## Important Notes
-
-1. **API Files**: Do not modify `.api` files manually. Run `./gradlew apiDump` to regenerate them
-2. **Backwards Compatibility**: Ensure new features are opt-in by default
-3. **Testing**: Write comprehensive tests for all new functionality
-4. **Documentation**: Always include proper documentation and examples

AGENTS.md

@@ -40,7 +40,6 @@ The project uses **Gradle** with Kotlin DSL. Key build files:
 
 ## Essential Commands
 
-### Development Workflow
 ```bash
 # Format code and regenerate .api files (REQUIRED before committing)
 ./gradlew spotlessApply apiDump
@@ -50,36 +49,14 @@ The project uses **Gradle** with Kotlin DSL. Key build files:
 
 # Generate documentation
 ./gradlew aggregateJavadocs
-```
-
-### Testing
-```bash
-# Run unit tests for a specific file
-./gradlew ':<module>:testReleaseUnitTest' --tests="*<file name>*" --info
-
-# Run system tests (requires Python virtual env)
-make systemTest
-
-# Run specific test suites
-./gradlew :sentry-android-core:testReleaseUnitTest
-./gradlew :sentry:test
-```
-
-### Code Quality
-```bash
-# Check code formatting
-./gradlew spotlessJavaCheck spotlessKotlinCheck
-
-# Apply code formatting
-./gradlew spotlessApply
-
-# Update API dump files (after API changes)
-./gradlew apiDump
 
 # Dependency updates check
 ./gradlew dependencyUpdates -Drevision=release
 ```
 
+To run tests, use the `test` skill rather than composing the Gradle invocation by hand — it
+resolves the per-module test task and the unit-test vs system-test split for you.
+
 ### Android-Specific Commands
 ```bash
 # Assemble Android test APKs
@@ -102,11 +79,9 @@ make systemTest
 
 ## Repository Skills
 
-This repo ships task-specific skills (declared in `agents.toml`, sources under `.agents/skills`). Prefer them over performing the steps manually:
-- **`create-java-pr`**: Branch, format, `apiDump`, commit, push, open PR, and add the changelog entry (automates the PR workflow above)
-- **`test`**: Run unit or system tests for a module or a specific class
-- **`check-code-attribution`**: Verify third-party code attribution on the current branch (see Third-Party Code Attribution below)
-- **`btrace-perfetto`**: Capture and compare Perfetto traces for Android performance work
+This repo ships task-specific skills, declared in `agents.toml` with sources under
+`.agents/skills`. Your harness already lists them with their descriptions — prefer them over
+performing the steps manually.
 
 ## Module Architecture
 
@@ -150,8 +125,8 @@ The repository is organized into multiple modules:
 
 ### Code Style
 - **Languages**: Java 8+ and Kotlin
-- **Formatting**: Enforced via Spotless - always run `./gradlew spotlessApply` before committing
-- **API Compatibility**: Binary compatibility is enforced - run `./gradlew apiDump` after API changes
+- **Formatting**: Enforced via Spotless
+- **API Compatibility**: Binary compatibility is enforced. `.api` files are generated, never hand-edited
 
 ### Exception Handling
 
@@ -189,10 +164,9 @@ PR description why the broad catch is necessary.
 
 ### Contributing Guidelines
 1. Follow existing code style and language
-2. Do not modify API files (e.g. sentry.api) manually - run `./gradlew apiDump` to regenerate them
-3. Write comprehensive tests
-4. New features must be **opt-in by default** - extend `SentryOptions` or similar Option classes with getters/setters
-5. Consider backwards compatibility
+2. Write comprehensive tests
+3. New features must be **opt-in by default** - extend `SentryOptions` or similar Option classes with getters/setters
+4. Consider backwards compatibility
 
 ### Third-Party Code Attribution
 When adapting code from third-party libraries: