okhp3-overkill-hill-brand

Topics in the source

• okhp3-overkill-hill-brand
• Workflow
• Scope
• About

OverKill Hill P³ · overkillhill.com · github.com/OKHP3 Load references/overkill-hill.yaml before editing and treat it as the primary profile baseline. Preserve forge-like technical confidence, readable hierarchy, and the profile’s accessibility notes. Do not blend in another family profile unless the user explicitly asks and scopes its supporting role. 1. Inspect the target’s existing token layer, framework constraints, generated files, and behavior that must remain unchanged. 2. Map the profile’s declared tokens first, then apply observed and inferred direction to shared primitives before one-off components. 3. Preserve routing, data flow, responsive behavior, and content. Do not rewrite sibling repositories or shared stylesheets without explicit direction. 4. Verify representative viewports, contrast for orange-on-dark states, keyboard focus, font fallback, reduced motion, and text alternatives for imagery. 5. Review the diff and report the profile version, changed surfaces, omitted cues, unresolved conflicts, and remaining human decisions. | In scope | Out of scope | |---|---| | OverKill Hill SPAs, documentation, presentations, and image briefs | Glee-fully or AskJamie visual su

This is an excerpt. Refer to the complete source and its current requirements.