GEMINI.md polish (#17680)

packages/cli/GEMINI.md

@@ -0,0 +1,15 @@
+## React & Ink (CLI UI)
+
+- **Side Effects**: Use reducers for complex state transitions; avoid `setState`
+  triggers in callbacks.
+- Always fix react-hooks/exhaustive-deps lint errors by adding the missing
+  dependencies.
+- **Shortcuts**: only define keyboard shortcuts in
+  `packages/cli/src/config/keyBindings.ts
+
+## Testing
+
+- **Utilities**: Use `renderWithProviders` and `waitFor` from
+  `packages/cli/src/test-utils/`.
+- **Snapshots**: Use `toMatchSnapshot()` to verify Ink output.
+- **Mocks**: Use mocks as sparingly as possilble.

packages/cli/src/commands/extensions/examples/context/.gitignore

@@ -1,26 +0,0 @@
-# Dependencies
-node_modules/
-npm-debug.log*
-yarn-error.log
-yarn-debug.log
-
-# Build output
-dist/
-
-# OS metadata
-.DS_Store
-Thumbs.db
-
-# TypeScript
-*.tsbuildinfo
-
-# Environment variables
-.env
-.env.local
-.env.development.local
-.env.test.local
-.env.production.local
-
-# IDEs
-.vscode/
-.idea/

packages/cli/src/commands/extensions/examples/context/GEMINI.md

@@ -1,14 +0,0 @@
-# Ink Library Screen Reader Guidance
-
-When building custom components, it's important to keep accessibility in mind.
-While Ink provides the building blocks, ensuring your components are accessible
-will make your CLIs usable by a wider audience.
-
-## General Principles
-
-Provide screen reader-friendly output: Use the useIsScreenReaderEnabled hook to
-detect if a screen reader is active. You can then render a more descriptive
-output for screen reader users. Leverage ARIA props: For components that have a
-specific role (e.g., a checkbox or a button), use the aria-role, aria-state, and
-aria-label props on <Box> and <Text> to provide semantic meaning to screen
-readers.

packages/cli/src/commands/extensions/examples/context/gemini-extension.json

@@ -1,4 +0,0 @@
-{
-  "name": "context-example",
-  "version": "1.0.0"
-}