coding-standards

Files (1)

• SKILL.md

SKILL.md (first lines)

# Coding standards

Follow the project's language, framework, architecture, and conventions. Prefer the smallest change that fully addresses the requirement. Avoid unrelated refactors and dependencies.

## Before changing code

- Read the relevant implementation, tests, and local instructions.
- Identify inputs, outputs, state changes, and external effects.
- Check supported runtime and dependency versions from project files or authoritative documentation.
- Convert ambiguous requirements into an explicit question or a documented assumption.

## Implementation

- Validate untrusted input at system boundaries and handle expected errors explicitly.
- Keep security decisions and authorization checks close to the operation they protect.
- Use deterministic code for exact calculations, parsing, sorting, and policy enforcement.
- Avoid logging secrets, tokens, personal data, or full sensitive request bodies.
- Keep interfaces small and names descriptive. Reuse established project abstractions.
- Add or update tests for changed behavior when the project has a test suite.

## Review and verification

Check edge cases, failure paths, compatibility, documentation, and privacy implications. Run the narrowest relevant checks and report their outcomes. Do not claim behavior was verified when only a static inspection was performed.

From Stinocon/pi-workbench, MIT.

More from Stinocon/pi-workbench