agentleFS
OKHP3OKHP3/skillz/.agents/skills/okhp3-overkill-hill-brand/SKILL.md

okhp3-overkill-hill-brand

Skill3 starsChanged 2 months agoMITView on GitHub

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.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify representative viewports, contrast for orange-on-dark states, keyboard focus, font fallback, reduced motion, and text alternatives …

    line 28

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

okhp3-overkill-hill-brand

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.

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 scopeOut of scope
OverKill Hill SPAs, documentation, presentations, and image briefsGlee-fully or AskJamie visual substitutions
Approved local-profile applicationShared stylesheet or sibling-repository changes without direction

About

Built by Jamie Hill · OverKill Hill P³ Published at github.com/OKHP3 Part of the OKHP3/skillz Agent Skill library. MIT License -- free to use, fork, and adapt. A nod to the source is appreciated.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.