2.4 KiB
Unisono Constitution
Core Principles
I. Conventions
Rigorously adhere to existing project conventions when reading or modifying code. Analyze surrounding code, tests, and configuration first.
II. Libraries/Frameworks
NEVER assume a library/framework is available or appropriate. Verify its established usage within the project (check imports, configuration files like 'package.json', 'Cargo.toml', 'requirements.txt', 'build.gradle', etc., or observe neighboring files) before employing it.
III. Style & Structure
Mimic the style (formatting, naming), structure, framework choices, typing, and architectural patterns of existing code in the project.
IV. Idiomatic Changes
When editing, understand the local context (imports, functions/classes) to ensure your changes integrate naturally and idiomatically.
V. Comments
Add code comments sparingly. Focus on why something is done, especially for complex logic, rather than what is done. Only add high-value comments if necessary for clarity or if requested by the user. Do not edit comments that are separate from the code you are changing. NEVER talk to the user or describe your changes through comments.
Quality Gates
I. Proactiveness
Fulfill the user's request thoroughly. When adding features or fixing bugs, this includes adding tests to ensure quality. Consider all created files, especially tests, to be permanent artifacts unless the user says otherwise.
II. Verification (Tests)
If applicable and feasible, verify the changes using the project's testing procedures. Identify the correct test commands and frameworks by examining 'README' files, build/package configuration (e.g., 'package.json'), or existing test execution patterns. NEVER assume standard test commands.
III. Verification (Standards)
VERY IMPORTANT: After making code changes, execute the project-specific build, linting and type-checking commands (e.g., 'tsc', 'npm run lint', 'ruff check .') that you have identified for this project (or obtained from the user). This ensures code quality and adherence to standards. If unsure about these commands, you can ask the user if they'd like you to run them and if so how to.
Governance
All PRs/reviews must verify compliance with these principles. Complexity must be justified.
Version: 1.0 | Ratified: 2025-10-13 | Last Amended: 2025-10-13