How can we help you?

Quick-start with an AI prompt

Copy this into your AI coding agent of choice to get set up without having to work through the steps below by hand.

Set up Stark's source code accessibility scanning in this React Native project.

Facts to use as-is (don't guess at flags or invent options):
- Package: `@stark-lab-inc/stark-accessibility-react-native`, installed as a dev dependency.
- CLI: `npx stark-scan-react-native <path>` — e.g. `npx stark-scan-react-native src/`.
  A Stark token is required for every scan; there is no tokenless mode.
- Token comes from `STARK_TOKEN` in the environment, a `.env` file at the project root,
  or `--stark-token <token>`. The CLI checks all three.
- CLI options, and only these: `--stark-token <token>`, `--config <preset>`,
  `--name <name>` (defaults to the current directory name), `--silent`,
  `--merge-config`, `--help`.
- `--config` presets: `basic` (rules that apply to any RN project), `ios` (basic plus
  iOS-only rules like `accessibilityIgnoresInvertColors`), `android` (basic plus
  Android-only rules like `importantForAccessibility` and `accessibilityLiveRegion`),
  and `all` (everything, and the default).
- By default the CLI uses its own embedded ESLint config and ignores yours.
  `--merge-config` makes it find and merge your local `eslint.config.js` — needed if
  your rules depend on custom parser or environment settings.
- Separately, the package ships an ESLint plugin for in-IDE feedback, exposing
  `configs.basic`, `configs.ios`, `configs.android`, and `configs.all`.
- My Stark token: PASTE_YOUR_TOKEN_HERE

Steps:
1. Confirm this is a React Native project, tell me the source root you'd scan, and check
   whether an `eslint.config.js` already exists. Report back before changing anything.
2. Tell me which platforms this app actually ships to, and which `--config` preset that
   implies. Don't just take the `all` default — if this is iOS-only, Android rules will
   produce findings nobody is going to act on. Ask me if it's ambiguous.
3. Install the package as a dev dependency.
4. Put the token in `.env` as `STARK_TOKEN`, and verify `.env` is gitignored before
   writing it. If it isn't, stop and tell me.
5. Run a first scan with the preset from step 2 and an explicit `--name` describing this
   codebase rather than letting it default to the directory name.
6. Summarize what came back: how many issues, grouped by rule, and separate the
   platform-specific findings from the basic ones. Don't start fixing them.

Once I've reviewed:
7. Propose (don't write yet) the ESLint plugin wiring for IDE feedback, using the same
   preset. Plain JS uses the flat-config array form; TypeScript uses `tseslint.config([...])`
   with the preset in `extends`. Match whichever this project actually is.
8. Propose a CI step running the scan with `--silent`, token supplied as a secret.

Constraints: use only the flags and presets listed above, don't add a config file the
docs don't describe, and if the scan errors show me the real output before proposing a fix.