docs: brand vs product register awareness#29
Conversation
Surfaces the brand-vs-product register distinction that emerges after running the existing skills against both brand surfaces (landing pages, campaign pages) and product surfaces (dashboards, admin, tools). Names the rules that genuinely swap between registers (Inter font, system font stack, fluid clamp() vs fixed rem, layout patterns, motion duration, image stock source, navigation patterns, component states), provides a per-skill register-fit table for the current bundle, and proposes two clean shapes for surfacing register at the skill level — either as a top-level dial or as per-skill frontmatter. Pure documentation addition. No skill content changed, no existing behavior altered. Cross-references pbakaus/impeccable (Apache 2.0, derived from Anthropic's frontend-design) for adjacent prior art on the register split.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 86ca4a9d9b
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| | Skill | Default fit | Notes | | ||
| |---|---|---| | ||
| | `design-taste-frontend` | Brand | The default all-rounder; reads brand-leaning when applied to dashboards | | ||
| | `gpt-tasteskill` | Brand | Stricter brand-grade output | |
There was a problem hiding this comment.
This row uses gpt-tasteskill (folder name), but the callable skill name is gpt-taste (skills/gpt-tasteskill/SKILL.md has name: gpt-taste, and README’s install table also documents --skill gpt-taste). In this table the other entries are largely presented as skill names, so this mismatch can cause users to copy the wrong identifier when selecting a register-aligned skill.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Fixed in f32ed6b. Changed gpt-tasteskill to gpt-taste in the register-fit table to match the callable name in SKILL.md and the README install table.
…l) in register-fit table Address Codex bot review comment: REGISTER_AWARENESS.md table had 'gpt-tasteskill' (the folder name) where 'gpt-taste' (the SKILL.md name: field, matching README install table) is the correct callable identifier.
1 participant
Summary
Adds
docs/REGISTER_AWARENESS.md— a single documentation file that names the brand-vs-product register distinction that emerges after running the skills against both brand surfaces (landing pages, campaign pages) and product surfaces (dashboards, admin tools).Pure documentation addition. No skill content changed, no existing behavior altered.
Motivation
The taste-skill bundle is genuinely useful. After applying the skills across multiple project types, one pattern emerges worth surfacing in the docs: many rules read as brand-register defaults when they're applied uniformly to every project. Concretely:
Interbanned for premium contexts. In a marketing surface that's the right call; in a product UI (dashboard, admin panel)Interis the common cross-platform default and system fonts are legitimate.clamp()typography. Brand-shaped. Product UIs are viewed at consistent DPI, and a fluidh1that shrinks in a sidebar looks worse than a fixed-rem scale.SECTION 04) are generally right to skip, but a real ops dashboard has legitimate operator labels and small mono metadata. "Skip unless truly necessary" sometimes gets misread as "always skip."What this PR contains
One new file at
docs/REGISTER_AWARENESS.mdwith:minimalist-skillis closest to product;output-skillis register-agnostic)REGISTER: brand) alongside the existing three, OR per-skill frontmatter — without committing to eitherfrontend-design) which uses the register split as its primary structuring decision, and to kylezantos/design-motion-principles for the Frequency Gate that reads cleanly across both registersWhat this PR does NOT contain
skills/*/SKILL.mdfilesproduct-ui-tasteskill would fit, but doesn't ship one)Reviewer notes
Thank you for the work on this skill.