TNTcraftHIM

Trace shared meanings and owners across Piik code, UI, copy and lifecycle. Use for cross-surface consistency work, recurring sibling-path defects or repository standardization audits; not every isolated edit.

Choose the smallest coherent implementation for Piik coding, code review, refactoring and implementation design, including dependency choices. Also use when Ponytail or YAGNI is requested; not for ordinary prose or status.

Keep Piik implementation, debugging and review proportionate and complete. Use to control speculative defenses, research or verification loops, and when Stop That Shit or removal of overengineering is requested.