Base link colour on the org chart, and deal-negotiation from the buy side - #33
Merged
Conversation
… the buy side
The four links in the usage panel rendered as browser-default blue, purple
once visited, against the page's own palette. Root cause: the stylesheet had
no base rule for `a`. Skill links set `color:inherit` and colour their own
children; the footer link sets its own colour. Those four were the only
anchors that fell through to the user agent, and any future link would have
done the same.
Fixed at the base rather than on the four: `a { color:var(--accent) }` with
an underline on hover. The existing rules still win where they apply, so
nothing else moves.
Verified in a real browser rather than by reading the CSS — computed colour
on all four links is rgb(217,119,87) on the dark ground and rgb(194,102,63)
on the light one, which are the accent token in each theme. The first probe
run reported the light palette for both schemes, so the dark branch was
re-checked under an explicit preferred-colour-scheme flag rather than
assumed from the light result.
revenue:deal-negotiation gains a buy-side section. The renewal situation in
USE-CASES reads the skill from the purchasing side, which the skill itself
never mentioned — a capability that existed and was undiscoverable. It names
the two things that actually differ: your alternative is weaker than it
feels because switching cost is real, and the leverage sits in the calendar
and expires at the notice window. Points at operations:vendor-management for
the renewal discipline and operations:procurement-and-sourcing for the
competitive process that makes a buy-side walk-away credible.
All nine checks pass; references at 273.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FaQP2WCqeFYH7s9pi1CJ5u
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The link bug
The four links in the usage panel rendered as browser-default blue — purple once visited — against the page's own palette.
Root cause is more general than those four. The stylesheet had no base rule for
aat all. It worked everywhere else by accident: skill links setcolor:inheritand colour their own children, and the footer link sets its own colour. My four were the only anchors that fell through to the user agent, and any link added later would have done the same.Fixed at the base rather than on the four:
The existing
li aandfooter arules still win where they apply, so nothing else moves.Verified in a real browser rather than by reading the CSS. Computed colour on all four links:
rgb(217,119,87)rgb(11,14,20)rgb(194,102,63)rgb(246,247,249)Those are the
--accenttoken in each theme. Worth noting: the first probe run reported the light palette for both schemes — the flag I used wasn't taking effect — so the dark branch was re-checked under an explicit preferred-colour-scheme flag rather than inferred from the light result.The cross-reference
revenue:deal-negotiationgains a buy-side section. The renewal situation inUSE-CASES.mdreads that skill from the purchasing side, which the skill itself never mentioned — a capability that existed and was undiscoverable.It names the two things that actually differ rather than restating the sell-side material:
Points at
operations:vendor-managementfor the renewal discipline andoperations:procurement-and-sourcingfor the competitive process that makes a buy-side walk-away credible at all.Verification
scripts/check-all.sh— all nine checks pass. References at 273.🤖 Generated with Claude Code
https://claude.ai/code/session_01FaQP2WCqeFYH7s9pi1CJ5u
Generated by Claude Code