Software Engineering
Use project rules first; continue for missing, conflicting, changing, or explicitly reviewed engineering contracts.
Route by Outcome
- Quality, defects, AI collaboration, review: Source Quality.
- Technology/framework/component choice: Technology Selection.
- Minimum correct implementation, reuse, overengineering: Implementation Economy.
- Architecture, dependencies, change budgets, debt: Architecture.
- Frontend state, navigation, forms, responsive/browser checks: Frontend.
- APIs, services, data, transactions, caches, queues, jobs: Backend.
- Test strategy, doubles, dependencies, data, flakiness: Testing.
- Source modernization or stack upgrades: Modernization.
- Derive rules from an existing codebase: Discovery.
- Only if local rules are absent/under review: Python, TypeScript, Go, Java, Ant Design, HTML/daisyUI.
Read matched references only; one profile does not imply others. Frontend/backend are references, not child skills or job roles.
Fast Path
Engineering alone handles a reversible, contract-preserving G1 change with one owner. Add no skills, PRD, ADR, or changelog. Follow Kernel isolation, proportional verification, and local commit. Check open-batch items narrowly; consolidate after test intent. Exclude security, privacy, permissions, payments, production data, paid/destructive actions, and releases.
Core Contract
- Preserve approved behavior and the symptom/call chain; locate the existing owner and reuse/variation boundary before coding. Share repeated behavior, use supported frameworks/SDKs, and remove verified obsolete wiring.
- Implement small changes directly. Create TD/ADR/POC only for durable public-contract, data, infrastructure, or release-boundary changes. Return behavior/acceptance changes to Product.
- Rerun the original path, then impact-based regressions. Report partial verification if the symptom was not covered. Never weaken types, tests, or security to pass.
Handoff only on real responsibility change, carrying facts, scope, evidence, unknowns, and authorization.
1---2name: senmu-build-engineering3description: Govern architecture, engineering contracts, implementation review, testing strategy, technical debt, or refactoring when project rules are missing or changing. Not for routine fixes, visual or interaction direction or prototype validation, or ordinary implementation under clear project rules.4---56# Software Engineering78Use project rules first; continue for missing, conflicting, changing, or explicitly reviewed engineering contracts.910## Route by Outcome1112- Quality, defects, AI collaboration, review: [Source Quality](references/source-code-quality-and-ai-collaboration.md).13- Technology/framework/component choice: [Technology Selection](references/technology-and-component-selection.md).14- Minimum correct implementation, reuse, overengineering: [Implementation Economy](references/implementation-economy-and-overengineering.md).15- Architecture, dependencies, change budgets, debt: [Architecture](references/architecture-constraints-and-technical-debt.md).16- Frontend state, navigation, forms, responsive/browser checks: [Frontend](references/frontend-engineering-contracts-and-validation.md).17- APIs, services, data, transactions, caches, queues, jobs: [Backend](references/backend-services-and-data-contracts.md).18- Test strategy, doubles, dependencies, data, flakiness: [Testing](references/software-testing-and-quality-verification.md).19- Source modernization or stack upgrades: [Modernization](references/source-modernization-and-stack-upgrades.md).20- Derive rules from an existing codebase: [Discovery](references/project-engineering-standard-discovery.md).21- 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 Design](references/frontend-ant-design-practice.md), [HTML/daisyUI](references/frontend-html-daisyui-practice.md).2223Read matched references only; one profile does not imply others. Frontend/backend are references, not child skills or job roles.2425## Fast Path2627Engineering alone handles a reversible, contract-preserving G1 change with one owner. Add no skills, PRD, ADR, or changelog. Follow Kernel isolation, proportional verification, and local commit. Check open-batch items narrowly; consolidate after test intent. Exclude security, privacy, permissions, payments, production data, paid/destructive actions, and releases.2829## Core Contract3031- Preserve approved behavior and the symptom/call chain; locate the existing owner and reuse/variation boundary before coding. Share repeated behavior, use supported frameworks/SDKs, and remove verified obsolete wiring.32- Implement small changes directly. Create TD/ADR/POC only for durable public-contract, data, infrastructure, or release-boundary changes. Return behavior/acceptance changes to Product.33- Rerun the original path, then impact-based regressions. Report partial verification if the symptom was not covered. Never weaken types, tests, or security to pass.3435Handoff only on real responsibility change, carrying facts, scope, evidence, unknowns, and authorization.
SenMuShare