arhuman

Task and project management in .claude/global-project/. Use when user ask for a new task.

Thinking guidelines to reduce common coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

TypeScript and Angular coding best practices. Use when working with TypeScript, Angular, or Node.js files: implementation, testing, refactoring, RxJS Observables, type system, strict mode, generics, and async patterns.

Docker and docker-compose best practices. Use for any Docker task: Dockerfiles (multi-stage builds, alpine, non-root), docker compose services (Go API, frontend, MariaDB, Oracle), healthchecks, volumes, networks, and K8S-compatible configurations.

Rules for writing and updating documentation. Use for any non-trivial documentation task in README.md, markdown files, text files, and code comments.

Best practices for Go project Makefiles. Use when creating or modifying a Go project Makefile: adding/reviewing targets, PHONY declarations, tab indentation, docker compose v2 targets.

Comprehensive testing specialist for all levels and types. Use when writing unit, integration, E2E, performance, or security tests; creating test strategies and plans; analyzing test coverage; building automation frameworks; managing defects; debugging test failures; manual testing (exploratory, usability, accessibility); scaling CI/CD test pipelines.

Writing rules for clear, powerful, incarnated blog posts.

Local-first agent memory for the current project, served by the `mnemos` MCP server (and the `mnemos` binary) over the project's OKF tree. Use in six cases. (1) RECALL — the user references a decision, preference, fact, name, value, file, endpoint, or convention that is NOT in the current conversation and may have been stored before (phrasings like "as we decided", "the usual", "that config", "remember when", "what was X", or any detail assumed-known but absent): search memory with `mnemos.search`/`mnemos.context` BEFORE answering from assumption. DEFAULT: if the user asks a project-specific factual question (a value, name, path, decision, endpoint, convention) whose answer is not already in this conversation, search memory FIRST — even with no cue phrase and even if you think you already know. (2) CAPTURE — the user states something durable worth keeping (a decision, preference, project fact, gotcha, convention) or says "remember this / note that / save this": persist it with `mnemos.remember`. (3) OKF — the