Rules

The **Implement** phase of [`../../workflow-rpi.md`](../../workflow-rpi.md). Goal: turn the approved `docs/plans/descriptive-name.md` into working code, phase by phase, without letting the context balloon.

def __init__(self, config: ServerConfig): self.clients: Dict[str, Client] = {} self.tools: Dict[str, Tool] = {} self.logger = setup_logger(__name__) async def handle_message(self, message: Message, client: Client) -> None:

workflow_dispatch: {} group: ${{ github.ref }}-${{ github.workflow }} cancel-in-progress: true cleanup_old_workflows: runs-on: ubuntu-latest uses: dmvict/clean-workflow-runs@v1 token: ${{ github.token }}

This is a Node.js CLI application that takes a trust indicator set (JSON) and a trust profile (YAML)and evaluates the trust indicator set against the trust profile, producing a trust report either in JSON, YAML or HTML format.

**Read `AGENTS.md` at the repo root first.** It holds the durable contract: layout, determinism rules, pgwire protocol gotchas, test tiers, commit conventions, and what-not-to-do. This file is a short Cursor-facing summary that points at the canonical

Follow this structure for all [.astro components](mdc:src/components/): // TypeScript frontmatter import type { Props } from './types'; import { getTranslation } from '@/i18n'; interface ComponentProps {

requires-python = ">=3.10" [project.optional-dependencies] target-version = "py310" python_version = "3.10"

Use when the task is documentation alignment, docs drift review, or safe docs cleanup. Canonical policy: `.hawp/kit/references/docs-alignment.md`

Canonical multi-agent rules: `@AGENTS.md`, then `@PROJECT_BIBLE.md`. Full lockdown: `CLAUDE.md §1–3` (that file wins on any conflict). This `.mdc` is the Cursor-specific pointer.

Cursor IDE rules and conventions for AI-assisted development.

Function/method calls use a space before `(` — see `.cursor/rules/code-style.mdc`: $content = QueryBuilder::for ($callback ()); array_map (fn (RoleEnum $role) => $role->value, RoleEnum::cases ());

Cursor IDE rules and conventions for AI-assisted development.

**Every new feature MUST include a `risks.yaml` file with initial risk assessment.**

Cursor IDE rules and conventions for AI-assisted development.

1. **After analyzing the prompt** 2. **Whenever you modify code** 3. **Sections order**

1. **Always-on rules** — `project-core`, `tech-stack`, this file 2. **File rules** — auto-attach when editing matching paths (see table below) 3. **Task skills** — `.cursor/skills/*/SKILL.md`; read the matching skill **before** implementing

Do **not** run package typecheck or production build commands yourself (e.g. `pnpm exec tsc --noEmit`, `pnpm run build`, `npm run build`, workspace `turbo` build tasks) unless: Assume CI and the user’s local/dev workflows will run builds and typechecks. Prefer editing code and letting those pipelines surface issues.

Cursor IDE rules and conventions for AI-assisted development.

**Context**: hass-addons (parent) + python-rebuild-tcp-comm (child) **Inheritance**: See `inheritance-model.mdc` for parent-child precedence rules **Phase**: [editing/verifying/documenting - detect from activity]

In user-facing text (documentation, comments, commit messages, PR descriptions, and assistant replies), avoid semicolons and em dashes.

Detect a **linked worktree**: `.git` is a **file** (not a directory).

This repo uses **Oxlint** (`oxlint` + `oxlint-plugin-eslint`) in **`api/`** and **`webapp/`**. After any substantive edit under `api/` or `webapp/`: 1. Run `npm run lint` in the package you changed (`cd api` or `cd webapp`).