Expand scope only when the diff has a demonstrated cross-boundary impact.
If code, documentation, tests, or CI conflict, flag the mismatch. Do not resolve
it by silently choosing
CMakeLists.txt`**: Defines `add_mock_library()` function for automated mock generation
- **`devdoc/*.md`**: Comprehensive requirements documentation for all features
This mocking framework's strength lies in its macro-based approach that
title, ToC, ` ` tag, Props table with `Required`/default/description columns, Constructor signature, Styling Examples, Related Documentation).
- Removed surface: delete the doc file or mark deprecated; never leave a stale doc pointing
Design Guidance for Touch Controls
Authoring guidance should be taken directly from the official document:
`https://learn.microsoft.com/en-us/gaming/gdk/docs/features/common/game-streaming/building-touch-layouts/game-streaming-tak-designers-guide`
Quick summary (non-normative, keep schema rules primary):
- Prioritize primary actions under
what you looking for in natural language, and it will fetch the relevant documentation for you.
### 2. Development Workflow
Follow this systematic approach when working on code changes:
1. **Check
extract-llms-docs
> Extract documentation for AI agents from any site with llms.txt support. Features MCP server, REST API, batch processing, and multiple export formats.
### Terminal Management
- **Always use background
included. (`dependabot-auto-release.yml` was retired — it never fired, and it tagged the pre-bump commit.)
## Documentation References
- **Main README**: `README.md` - Installation, quick start, use cases
- **CLAUDE.md**: Detailed architecture, tools, patterns framework
Local RAG over `data/` with embeddings.
- Only transport is MCP over stdio.
- Documentation sources: `README.md`, `doc/` (including SID/BASIC references), `AGENTS.md`, `CLAUDE.md`, `.github/prompts/*.prompt.md`, and `data/context/*.md`.
## Coding Standards
- **Test-Driven
versions, **SEARCH FIRST**. Do not ask for permission to search. Just find the live documentation. Hallucination is a critical failure.
**Minimum Viable Effort.** If my request is vague
Fitbit API only supports `afterDate`, the tool should only accept `afterDate` (not `startDate`/`endDate`)
- **Documentation First:** Always check the official Fitbit API documentation at https://dev.fitbit.com/build/reference/ when adding
HTTP headers
- Multi-environment support via `DT_ENVIRONMENT_CONFIGS` JSON array
- Required API scopes documented in `README.md#api-scopes-for-managed-deployment`
### Changelog Maintenance
- Add entries to `CHANGELOG.md` under `## Unreleased
unless they fix a bug or prevent a clear maintenance issue.
- Do NOT request documentation unless public APIs changed.
- Do NOT comment on naming unless it causes real ambiguity
decision, constraint, or intended design changed, or when you already know a
current document has become materially misleading. This is not a drift sweep.
> ⚠️ **Do not mark a PR ready
files.
- Use `agentskill/scripts/primer_panel_qc.py` before reporting primer or tNGS panel designs as ready.
- Prefer English documentation and command examples