glyph
Design and implement product-specific frontends. Use for interface design, composition, responsive implementation, purposeful interaction, and rendered verification. Preserve an established product direction unless redesign is requested.
- License 许可
- MIT
- 最近更新
- 2026-11-04
- Stars
- ★ 13
- Forks
- 1
01 前言 Front Matter
- name
- glyph
- description
- Design and implement product-specific frontends. Use for interface design, composition, responsive implementation, purposeful interaction, and rendered verification. Preserve an established product direction unless redesign is requested.
02 资源文件 23
- 资产文件assets/starter.css17.4 KB
- 许可证LICENSE1.0 KB
- 参考文档MIGRATION.md3.8 KB
- 参考文档references/accessibility-rules.md2.5 KB
- 参考文档references/anti-slop-rules.md2.4 KB
- 参考文档references/background-rules.md1.7 KB
- 参考文档references/category-playbook.md10.0 KB
- 参考文档references/component-rules.md4.8 KB
- 参考文档references/core-color-rules.md2.4 KB
- 参考文档references/direction-composition-assets.md2.5 KB
- 参考文档references/framework-rules.md1.8 KB
- 参考文档references/implementation.md2.4 KB
- 参考文档references/landing-composition.md4.4 KB
- 参考文档references/landing-page-research.md4.1 KB
- 参考文档references/layout-rules.md2.3 KB
- 参考文档references/motion-rules.md3.3 KB
- 参考文档references/responsive-rules.md2.3 KB
- 参考文档references/starter-kit.md5.3 KB
- 参考文档references/style-directions.md12.4 KB
- 参考文档references/typography-rules.md2.4 KB
- 参考文档references/verification.md2.8 KB
- 参考文档references/visual-craft.md11.5 KB
- 参考文档THIRD_PARTY_NOTICES.md2.9 KB
03 SKILL.md 正文
Glyph — frontend design judgment
One skill, one entry point. Help the assistant decide, compose, build, interact, and verify. Do not reproduce the Glyph website as a template.
Instruction roles
- Requirements protect functionality, truthful claims and accessibility. State conflicts and limitations.
- Patterns are starting points; change them when the product or evidence calls for it.
- Taste hypotheses are design judgments, not high-confidence research findings. Explain and inspect them.
- The user's goals and existing brand take precedence over aesthetic defaults. Never claim this skill overrides system instructions. Do not brand an unnamed product “Glyph”; use a descriptive working title and label it provisional.
Workflow
- Understand. Inspect existing UI and code before edits. Establish audience, primary task, real content, brand, language, constraints and supported stack. Ask only for facts that materially block progress. Preserve unrelated work.
- Choose. For open-ended work compare a few meaningfully different compositions, not just palettes. State tradeoffs and choose with reasons unless the user wants to choose. Preserve established direction unless redesign is requested. Read direction and assets. For landing, marketing, brand or launch pages, first map the brief with the category playbook, pick one or two style directions, then read landing composition and name the hero pattern and direction you chose. Clean is one direction, not the default for every product; for reference-led exploration read landing-page research.
- Compose. Sketch or code the important screen with actual content. Resolve hierarchy, proportions, density, type and asset placement before polishing components. Figma is optional. Check the primary task at small and large sizes.
- Express. Decide what carries personality: typography, product imagery, illustration, photography, interaction or a combination. Without an established brand or design system, read visual craft and build to its baseline, applying the chosen direction's recipe: fonts only from the baseline list or that direction's list, its type and spacing scales, and one high-fidelity hero visual. Never improvise fonts or hand-drawn object illustrations. Verify asset provenance and rights. References inform principles; never copy a reference design or fill space with unrelated scenery.
- Build. Read implementation and relevant topic references below. For pages without a design system, start from the starter kit (
assets/starter.css) and its direction presets rather than inventing tokens. Use the actual project stack. Implement loading, empty, error, success, focus and disabled states where applicable; do not simulate successful persistence. - Interact. Read motion for interactions that benefit from movement. Decide whether to animate at all. Account for purpose, frequency, distance, interruption, gestures and reduced motion.
- Verify and revise. Read verification. Inspect real renders and exercise interactions. For visual work, run the craft checklist in visual craft at desktop and mobile widths. Compare with the chosen direction and revise. Report checks performed, failures, limitations and remaining risks. Never equate a successful build with a successful interface.
Load selectively
Do not dump every rule into every task. Start with the workflow and load only relevant references.
| Need | Reference |
|---|---|
| Direction, composition and asset rights | Direction / composition / assets |
| What a category's visitors need, primary action, hero and direction | Category playbook |
| Named looks beyond clean: recipes for type, colour, surfaces, visuals, motion | Style directions |
| Production-quality type, spacing, surfaces, controls and visuals | Visual craft |
| Ready tokens and components with direction presets | Starter kit |
| Hero patterns, section library and page anatomy | Landing composition |
| Landing-page libraries and evidence-led composition | Landing-page research |
| Color roles, semantic and categorical palettes | Color |
| Content, language and type | Typography |
| Hierarchy, proportions and density | Layout |
| Component behavior and states | Components |
| Stack and functioning implementation | Implementation, frameworks |
| Interaction, interruption and gestures | Motion |
| Keyboard, names and contrast | Accessibility |
| Mobile, zoom and long content | Responsive |
| Unconsidered defaults | Anti-slop |
| Surfaces, imagery and backgrounds | Background |
| Rendering and release evidence | Verification |
Commands (assistant request conventions)
These are prompt conventions, not executable CLI commands or guaranteed native slash-command registrations. Natural-language equivalents work too.
/glyph design: understand the brief, compare directions when appropriate, choose a composition and return implementation-ready decisions with reasons, tokens, responsive behavior, assets and states./glyph audit: inspect source and rendered UI, report observed issues with concrete fixes, distinguish measured accessibility failures from risks, preserve intended brand./glyph vibe: produce one usable implementation prompt with objectives, composition, type/color roles, assets, state behavior, stack constraints and verification plan. Use this entry point and relevant references; no external template dependency./glyph prompt: turn approved decisions into concise reusable project instructions. Include exceptions and what must be verified. Do not append unsolicited marketing links.
Coherence without sameness
A dashboard, expressive landing and personal portfolio should not share a compulsory hero, card grid, font pairing or footer. Consistency means coherent roles and behavior, not identical layouts. Simple can still have color, personality and strong composition. Poppins, purple gradients and familiar layouts are valid considered choices. Avoid thoughtless defaults, not entire visual vocabularies. The owner's portfolio logos, rotating greeting, website colors and fonts are not reusable skill defaults.
See third-party notices for attribution and migration for the keep/change/remove map.