wise-before-dev

To ensure Wise code changes align with architecture constraints, agents must load required task context and enforce Wise frontend, Tauri, and Trellis workflow invariants before modifying source code. This prevents unscoped development by checking implementation boundaries and project specifications.

Scoping Trellis task changes requires reviewing task artifacts and relevant implementation context before editing. Agents apply focused validation procedures and check implementation boundaries to keep repository updates safe and aligned with the Agent Harness workflow.

You do not need to launch the full application to validate Tauri command changes. The skill provides validation guidance to help select focused tests and checks for code changes, avoiding unnecessary application launches while ensuring safe repository updates.

Yes, you can use this to manage implementation boundaries for Wise product surface modifications. It enforces architecture invariants and requires adherence to project specifications, guiding controlled implementation planning across frontend, Tauri, tests, and project skills.

Unscoped development causes issues in the Trellis workflow because agents may bypass active task context and architectural rules, leading to inconsistent code changes. Loading specifications and enforcing implementation boundaries prevents these unsafe repository updates.

Architecture compliance checks apply strictly to Wise frontend, Tauri, Trellis workflow, product surface, test, and project skill changes. Changes outside these controlled implementation areas or lacking project specifications are not covered by this validation guidance.