responding to the user:
- [ ] Update `lat.md/` if you added or changed meaningful functionality, architecture, tests, behavior, or planned work. Keep it a focused snapshot of current/planned state, not a journal/changelog
conversion wrapper
- `scripts/template.html`, `scripts/template_ebook.html` — HTML templates
## Prerequisites
- **Python 3.12+** — the version CI runs.
- **Unit tests need nothing else.** Every third-party import in `scripts/` is guarded
(`try/except ImportError` or function
Power Apps Portals samples (OAuth, Web API)
- **powershell/** & **build-tools/**: Deployment automation
## Building and Testing
### Power Apps Component Framework (PCF)
Each PCF control is a self-contained project with TypeScript/React
SSH/network task, verify `hostname` and connection direction** (source → target).
12. **Report outcomes faithfully.** "Tests pass" means you ran them and saw them pass; if a step was skipped or failed
production code
- Proper error handling with try/catch
- Input validation with Zod or similar
### 3. Testing
- TDD: Write tests first
- 80% minimum coverage
- Unit tests for utilities
- Integration tests for APIs
choices
- Uses AskUserQuestion tool for targeted clarifying questions (1-6 questions)
## Build & Development Commands
**Testing:**
- Run all tests: `pytest tests/` or `python -m pytest`
- Run specific test suite:
- Engine tests
Claude Code.
**Contributors: start with `CONTRIBUTING.md`** — the short version (setup, boundaries, house rules,
testing habits). This file is what you reach for when you need to know *why* a rule
this repository.
## Build and Development Commands
```bash
# Build the binary
make build
# Run tests with race detection
make test
# Run tests with coverage report
make test-cover
# Lint with golangci
integrations. Uses Cookiecutter templates with Jinja2 conditionals.
## Commands
```bash
# Install dependencies
uv sync
# Run tests
uv run pytest
# Run single test
uv run pytest tests/test_file.py::test_name -v
# Linting
Tiger Docs MCP Server - Development Guidelines
## Build, Test & Run Commands
- Build: `./bun run build` - Compiles TypeScript to JavaScript
- Watch mode: `./bun run watch http` - Watches for changes and rebuilds automatically
Local Development Commands
### Server
```bash
cd server
./start.sh
```
Useful commands:
```bash
pnpm build
pnpm test
pnpm backend
pnpm format-and-lint
pnpm format-and-lint:fix
pnpm --filter @repo/db
local SQLite store and exposes it via CLI and MCP Server.
## Build & Test
```bash
go build -o gortex ./cmd/gortex/ # requires CGO (tree-sitter C bindings)
go test -race ./... # all test
line names a symbol or a file, it's wrong. Internal-only changes (typecheck, tests, refactors, doc/agent tweaks, lint, dep bumps with no behavior change) get NO entry.
**At release
truth for "what version are we on"); `nix/tests/` = pg_regress + smoke + migration NixOS tests; `nix/docs/` = the real developer docs (start here, not README) |
| `ansible/` | Config management for the production
/docs/agent-reference/runtime-and-layout.md)
- [docs/blueprints.md](./docs/blueprints.md)
- [docs/plugins.md](./docs/plugins.md)
## Quick Commands
```bash
npm run build:sdk
npm run test:sdk
npm run test:e2e:docker
npm run verify:metadata
```
## Claude Code Local Notes
- `.claude/settings.json
with `#!/bin/bash`
4. **Use environment variables**: Access `$DMUX_ROOT`, `$DMUX_WORKTREE_PATH`, etc.
5. **Test it**: Set env vars manually and run the script
## Hook Execution Model
- **Non-blocking**: Hooks
ext4 persistence image
.\4-copy-to-usb.ps1 # Copy ISO + persistence + scripts to USB
```
### Tests
```bash
node --test "tests/*.test.mjs" # Run all tests (node:test, no test framework dep)
# NOTE
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.