software-engineering

Apply a defined set of engineering principles covering naming, organization, testing, and security to every change. This Skill provides rules like concrete naming (retryAfterMs over timeout), behavior-focused tests, and OWASP compliance that can be applied during writing or review.

Use concrete, specific names such as retryAfterMs instead of timeout or emailValidator instead of validator. Avoid vague terms like data, item, list, or info, and use nested objects like config.public.ENV_NAME to provide context.

Write a test for every bug you fix to prevent re-occurrence. Test behavior rather than implementation, use third-person verbs instead of "should", and organize cases with describe blocks.

Avoid abstractions when a function mainly calls one other function or a helper is used only once. Keep code close to where it is used unless it is needed in three or more places, following KISS and YAGNI principles.

Use query-builders instead of writing pure SQL strings, which protects against injection attacks. Combine this with OWASP best practices and WCAG 2.0 accessibility guidelines for secure, accessible applications.