swpm-dev-standards

SWPM development standards mandate using type over interface, avoiding any, keeping types in *.types.ts files, and enforcing kebab-case file naming conventions to ensure consistent codebase structure.

Enforce coding conventions by applying centralized rules during file creation and code reviews, checking for explicit exports, early returns, preferred try/catch styles, and arrow function patterns to guide onboarding.

Use default exports for configurations and commands, while reserving named exports for utility functions. This pattern ensures clear module boundaries and consistent import behaviors across the project architecture.

No dependencies are required to apply these coding standards. The rules are codified directly within the skill to enforce SOLID principles, typing rules, and clean code patterns without needing external ESLint plugins.

The best way to structure a new module is to follow the defined folder layout, use kebab-case for file names, separate types into *.types.ts files, and ensure business logic is kept out of ternary operators.