from claude-code-workflows340
Opinionated, language-agnostic principles for writing maintainable, readable, and secure code — use when implementing features, refactoring, or reviewing code q
This skill codifies a concise set of language-agnostic coding principles and best practices aimed at improving maintainability, readability, and long-term code quality. It provides recommendations on function design, error handling, dependency management, commenting, refactoring, testing, and security defaults. The guidance is practical and rooted in everyday engineering work — e.g., when to refactor, how to choose parameter shapes, and how to prefer explicitness and small, single-responsibility functions.
Invoke this skill whenever you're implementing a new feature, performing a refactor, reviewing a pull request, or writing guidelines for a codebase. It is useful during design discussions (to argue for simplicity and maintainability), code review (to point reviewers to concrete heuristics), and when onboarding engineers who need a compact set of standards. If a change involves API design, parameter shape, error handling, or dependency choices, consult this skill.
references/ with supporting docs and checklistsFits general assistant and developer-focused agents (Claude Code, Copilot-style assistants, and developer automation agents). The guidance is tool-agnostic and intended to be injected into code review or authoring workflows.
A well-crafted language-agnostic coding principles skill with no executable scripts — purely instructional. Covers code quality, function design, error handling, dependency management, security, testing, and refactoring with clear actionable guidance. Includes a notable 2026-03 security supplement referencing OWASP Top 10:2025 changes and AI-generated code risks. No security concerns; purely a reference document.
No scripts to execute — static analysis only. SKILL.md mentions a references/security-checks.md that isn't included in the fetched data; may be a broken reference or optional. Skill is well-aligned with its stated purpose. Security section is notably thorough and up-to-date (references OWASP 2025, OpenSSF AI guide). Minor deduction on architecture for missing references/ directory and being a single flat file.
