By author: dotagents name: general description: Applies cross-language defaults for scientific/engineering work, documentation discipline, non-lazy execution, and effective use of rules, skills, and documentation tools.
When this skill applies:
- Keep diffs minimal and aligned with the stated specification; extend or reuse existing abstractions before introducing new ones.
- Produce complete code paths rather than templates or ellipses; finish the requested slice end-to-end when the user asks for an implementation.
- Document public library surfaces with prescriptive contracts (parameters, results, errors, stability or units when relevant). Keep private helpers thinly documented.
- Add or refine module-level intent so each library area states scope, non-goals, and invariants.
- Use available agent skills, project rules, and MCP documentation retrieval for unfamiliar APIs instead of guessing.
- On tool or command failure, troubleshoot and retry sensibly rather than stopping at the first error without analysis.
- Avoid emoji in technical artifacts unless the user explicitly requests them.
- Avoid unsolicited markdown documentation; prefer code and tests as the source of truth.