senmu-build-engineeringlisted
Install: claude install-skill SenMuShare/senmu-buildos
# Software Engineering
Use project rules first; continue for contract gaps, conflicts, changes or review.
## Route by Outcome
- Quality, defects, AI collaboration, review: [Source Quality](references/source-code-quality-and-ai-collaboration.md).
- Technology/framework/component choice: [Technology Selection](references/technology-and-component-selection.md).
- Minimum correct implementation, reuse, overengineering: [Implementation Economy](references/implementation-economy-and-overengineering.md).
- Architecture, dependencies, change budgets, debt: [Architecture](references/architecture-constraints-and-technical-debt.md).
- Frontend state, navigation, forms, responsive/browser checks: [Frontend](references/frontend-engineering-contracts-and-validation.md).
- APIs, services, data, transactions, caches, queues, jobs: [Backend](references/backend-services-and-data-contracts.md).
- Test strategy, doubles, dependencies, data, flakiness: [Testing](references/software-testing-and-quality-verification.md).
- Source modernization or stack upgrades: [Modernization](references/source-modernization-and-stack-upgrades.md).
- Derive rules from an existing codebase: [Discovery](references/project-engineering-standard-discovery.md).
- Only if local rules are absent/under review: [Python](references/python-engineering-profile.md), [TypeScript](references/typescript-engineering-profile.md), [Go](references/go-engineering-profile.md), [Java](references/java-engineering-profile.md), [Ant Desi