From fd059e119be3c25803c6f1bb9fde9cbc4c1c6164 Mon Sep 17 00:00:00 2001 From: randogoth Date: Fri, 9 Oct 2026 13:18:29 +0300 Subject: [PATCH] chore: remove AGENTS.md --- AGENTS.md | 31 ------------------------------- 1 file changed, 31 deletions(-) delete mode 100644 AGENTS.md diff --git a/AGENTS.md b/AGENTS.md deleted file mode 100644 index 0780b93..0000000 --- a/AGENTS.md +++ /dev/null @@ -1,31 +0,0 @@ -# General Working Rules - -## Writing Strings - -- **Plain and direct.** Follow the Microsoft Writing Style Guide. Address the user as "you," use contractions, sentence case, and the fewest words that work. Start with verbs. Prefer simple words ("use," not "utilize"). -- **Actionable UI.** Buttons say what they do ("Save draft," not "OK"). Use input-neutral verbs ("Select," not "click" or "tap"). Errors say what happened and what to do next, without blaming the user or using "invalid," "illegal," or "fatal." -- **No jargon.** Write for non-technical users. Never show raw error codes, exception names, or implementation details on their own. Add a code only after the plain explanation, e.g. "(Error 502)." -- **Consistent terms.** Use one term per concept. Avoid idioms, puns, and abbreviations so strings translate cleanly. -- **Avoid filler.** Don't default to em dashes, "not just X, it's Y" constructions, abstract triads, rhetorical questions, hype adjectives, hedging, or summary lines. Avoid "delve," "leverage," "robust," "seamless," "testament to," and "in today's world." - -## Documentation - -- Keep documentation concise, accurate, and synchronized with the implementation. -- Distinguish implemented behavior from proposals and historical plans. Remove outdated information and shorten resolved findings. -- Update specifications alongside changes to interfaces, formats, and contracts. Record important decisions where they are enforced. -- **Natural reflow.** Write paragraphs as continuous lines without hard wrapping. Use blank lines between paragraphs and explicit line breaks only where structurally necessary. - -## Working Style - -- **Inspect first.** Examine existing code, configuration, architecture, and conventions rather than assuming how things work. -- **Respect scope.** Follow the latest explicit instructions. Do not make unrelated changes or resume superseded tasks. -- **Work silently.** No progress narration or request recaps. Interrupt only for genuine blockers or discoveries that materially change the approach. -- **Resolve uncertainty.** Investigate missing information before asking. Never invent requirements or assume unverified behavior. -- **Respect user decisions.** Identify significant design problems and propose concrete alternatives with trade-offs, but follow the user's choice. -- **Respect authorization.** Observe approval requirements for changes, tests, commits, deployments, and destructive operations. -- **Commit messages.** Use concise, single-line, tag-prefixed messages (e.g., fix:, feat:, refactor:, docs:). Describe what changed using the imperative mood. -- **No credit notes.** Omit attribution, co-author trailers, AI-generated notices, and other credit statements from commits and generated documentation. - -## Completion - -Summarize changes, verification results, important decisions, and unresolved issues in a few sentences. Avoid lengthy reports unless requested. \ No newline at end of file