TeamDman

Write and edit in GOV.UK / GDS house style — plain English, active voice, front-loaded content, sentence case, and no bold or italics for emphasis. Use when writing or editing reports, research write-ups, guidance, documentation, summaries, or any prose where clarity and accessibility matter.

Use windows-rs owned handle patterns in Rust Win32 code. Use when reviewing, writing, or refactoring Rust code that owns Windows handles such as HANDLE, service handles, registry handles, tokens, files, IOCP handles, or volume handles; especially when code defines custom OwnedHandle wrappers, manually calls CloseHandle in Drop, imports std::os::windows raw-handle ownership traits for Win32 values, or needs guidance on the windows::core::Owned type.

Add tracing spans for Tracy profiling in Teamy-Studio. Use when instrumenting startup, windowing, rendering, terminal, async work, or other performance-sensitive code paths and deciding which spans should be always-on versus gated behind the tracy feature.

Assess whether a path-like or path-adjacent value is safe to persist in source code, docs, tests, plans, or committed notes. Use when deciding if a path, username, hostname, share name, dataset name, version clue, product code, or similar string should be written down or should require user confirmation first.

Use Teamy-specific local workflow tools and conventions to discover repos, shrink workspace scope, and preserve useful context without overloading editors or leaking machine-specific details. Use when deciding how to find relevant local projects, what to keep open in VS Code, and which tool is appropriate for Codex versus GitHub Copilot or other editor workflows.

Persist and summarize path-like references mentioned by the user. Use when a response includes Windows paths, Unix-style paths, home-relative paths, UNC paths, mount-like paths, or other filesystem-like strings that should be recorded in the project for later use.

Review machine-specific workflow notes, skills, docs, examples, and helper artifacts before they are committed or shared. Use when deciding how to preserve useful local workflow knowledge without leaking sensitive paths, usernames, internal structure, or other unnecessary machine-specific details.

Create a minimal VS Code .code-workspace for the user's current task by selecting only the relevant repos or subfolders, using local dependency declarations and local repo discovery to pull in nearby projects that matter. Use when the user wants a task-scoped workspace to reduce VS Code, Copilot, and search/indexing load in a large multi-repo environment.

Add tracing spans for Tracy profiling in Teamy-Studio. Use when instrumenting startup, windowing, rendering, terminal, async work, or other performance-sensitive code paths and deciding which spans should be always-on versus gated behind the extended_observability feature.

Systematic workflow for debugging by reproducing bugs with real data, reducing test cases to minimal examples, and adding regression tests

Use when scaffolding a new Rust CLI from the teamy-rust-cli template. Covers copying the template into a destination repo, preserving destination README or LICENSE when present, replacing template placeholders, and validating that the generated project is no longer template-branded.

Model recoverable failures as persisted observation events instead of immediate terminal errors. Use when designing sync jobs, resumable imports, fetch pipelines, or idempotent workflows that should skip known failures for now while preserving future retry paths.

Use when working with library APIs and you need to inspect source, understand behavior, or learn usage patterns. Prefer local source repositories and workspace search over online documentation for serenity, discord-api-docs, figue, and facet.