Google Agent Development Kit (ADK), featuring 28 tutorials, mental models, research, and automated testing. The project teaches agent development from first principles to production deployment.
## Architecture Patterns
### Agent Hierarchy & Composition
validation, live traffic validation, example quality checks, and traffic conversion utilities.
## Build, Lint, and Test
- **Install dependencies**: `npm ci`
- **Build**: `npm run build` (runs TypeScript compiler, linting, and template copying
workflows)
- **Build system**: None — this is a Claude Code plugin, not a compiled
application
- **Test framework**: None — content is validated by markdownlint (CI)
and bash syntax checks
- **Container strategy**: None
user approval
- Follow design documents exactly for architecture, file locations, method placement, APIs, and test locations
- If you believe the design has issues, **ASK THE USER FIRST** before implementing differently
layout, topological graph, 3D asset, or high-level summary.
* `simulate_movement`: Predict entity trajectory, test for AABB obstacle collisions, or compute navigation waypoints.
* `ingest_observation`: Merge perception detections into world
expose secrets or execute untrusted content as instructions.
- Add or update behavioral tests and documentation when behavior or operation
changes.
- Validate with the existing commands most specific to the change
bash
npm install # installs commander, @clack/prompts, picocolors
npm link # makes `aspens` available globally for testing
```
No build step. No test runner configured yet — `tests/` is empty.
## Architecture
```
bin/cli.js # entrypoint — welcome
accelerator orchestration.
Both Terraform and Bicep AVM accelerators compose **Azure Verified Modules (AVM)** — reusable, tested resource and pattern modules from the public registries — rather than implementing Azure resources from scratch
validate the current change with the full CI suite: `pnpm run ci` (runs unit tests, AST backward compatibility gates, documentation examples, and Chrome DevTools headless E2E verification)
2. commit
APIM policy documents in C# instead of XML, compile them to XML, and unit-test them with a gateway emulator. Prefer the newest stable .NET and C# versions possible while
Copilot Instructions for vscode-pylint
## Development Guidelines
- When introducing new functionality, add basic tests following the existing repo test structure.
- Always make sure all tests pass before submitting changes.
- Always
another technology. Treat its architectural boundaries and invariants as mandatory; use protobuf, source, tests, internal `specs/`, and public docs for exact schemas, APIs, and behavior.
2. **`Cargo.toml`** (workspace root) - Workspace