Thank you for your interest in contributing! This document provides code style guidelines and standards.
See the Development Workflow section in the README for the step-by-step process using /task, /review, and /execute commands.
- Follow the guidelines in
ai/skills/aidd-javascript/SKILL.md - Use functional programming patterns
- Keep functions small, pure, and composable
- Use
const, avoid mutation - Prefer explicit over implicit
- Use explicit path exports:
import { utilName } from 'aidd/<utilName>' - Favor named exports over default exports
- Add exports to
package.jsonexports field - Include TypeScript
.d.tsdefinitions - Add automated tests for all exports
- All code changes must include tests
- Follow TDD: write tests first, then implementation
- Use Vitest for testing (see existing tests for examples)
- Tests should be isolated and independent
- Run tests before committing:
npm test
Follow conventional commit format (see ai/commands/commit.md):
type(scope): description
Examples:
feat(server): add CORS middleware
fix(cli): resolve symlink creation bug
docs: update contributing guidelines
test: add export validation tests
Types: feat, fix, docs, test, refactor, chore, perf, ci, build, style, revert
- Ensure all tests pass (
npm test) - Update documentation if needed
- Follow the code review guidelines in
ai/skills/aidd-review/SKILL.md - Address review feedback promptly
- Squash commits if requested
- Wait for approval from maintainers
- Check existing issues
- Review the AI skills in
ai/skills/for guidance - Ask questions in your PR or open a discussion
By contributing, you agree that your contributions will be licensed under the MIT License.