OverKill Hill P³ OverKill Hill SPA styling. Use when a user wants an OverKill Hill application, documentation artifact, presentation, or image brief aligned to the approved OverKill Hill profile. Also activate when a target needs the forge-like technical visual system of the OverKill Hill family. This specialization applies the approved local profile and does not substitute Glee-fully or AskJamie styling.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add OKHP3/skillz --skill okhp3-overkill-hill-brand --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Okhp3 Overkill Hill Brand?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/okhp3-okhp3-overkill-hill-brand-skillz)More formats (shields.io, HTML) on the badges page.
---
name: okhp3-overkill-hill-brand
description: >
OverKill Hill P³ OverKill Hill SPA styling. Use when a user wants an OverKill Hill application, documentation artifact, presentation, or image brief aligned to the approved OverKill Hill profile. Also activate when a target needs the forge-like technical visual system of the OverKill Hill family. This specialization applies the approved local profile and does not substitute Glee-fully or AskJamie styling.
license: MIT
metadata:
author: Jamie Hill (OverKill Hill P³)
version: "1.1.0"
category: developer-tooling
origin: okhp3/skillz
homepage: https://overkillhill.com
author-github: https://github.com/OKHP3
in_scope: "Styling and layout decisions for OverKill Hill-branded SPAs, documents, presentations, and image briefs against the approved local profile."
out_of_scope: "Blending other family profiles, inventing brand tokens not present in the profile, or restyling non-OverKill Hill surfaces."
---
# okhp3-overkill-hill-brand
**OverKill Hill P³** · [overkillhill.com](https://overkillhill.com) · [github.com/OKHP3](https://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.
## Workflow
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.
## Scope
| In scope | Out of scope |
|---|---|
| OverKill Hill SPAs, documentation, presentations, and image briefs | Glee-fully or AskJamie visual substitutions |
| Approved local-profile application | Shared stylesheet or sibling-repository changes without direction |
## About
Built by [Jamie Hill](https://overkillhill.com) · [OverKill Hill P³](https://overkillhill.com)
Published at [github.com/OKHP3](https://github.com/OKHP3)
Part of the [OKHP3/skillz](https://github.com/OKHP3/skillz) Agent Skill library.
MIT License -- free to use, fork, and adapt. A nod to the source is appreciated.

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!