Documentation / Use Glyph

Guidance & exceptions

Understand requirements, patterns and design judgment.

Instruction roles

Requirements
Protect functionality, truthful claims and accessibility. State conflicts and limitations.
Patterns
Adaptable starting points. Change them when the task or evidence calls for it.
Taste hypotheses
Design judgments to inspect in context. They are not high-confidence research findings.

When to break a pattern

Consistency means coherent roles and behavior, not identical layouts. A data-heavy dashboard, expressive landing and personal portfolio should not inherit the same hero and card grid.

Meaningful categorical colors and expressive brand palettes are valid. Poppins, purple gradients and familiar layouts can be considered choices. Font pairing should follow content, language, brand and legibility.

The user’s goals and existing brand take precedence over aesthetic defaults. Accessibility and truthful reporting still need to be checked.

Research with references

For reference-led landing work, use a bounded study of accessible sources such as Mobbin or Lapa Ninja. Record what was actually visible, what principle transfers, what to reject and any access limits.

Glyph does not bundle a paid library integration. Public screenshots do not grant permission to redistribute assets or copy artwork and code. Build an original composition suited to the product.

Guides & section titles

IntroductionWhat Glyph does and when to use it.What is Glyph?IntroductionHow to think about itIntroductionStart buildingIntroductionInstallationAdd Glyph to your coding assistant.Install with the skills CLIInstallationInstall from a local checkoutInstallationVerify the installationInstallationDesign workflowFrom understanding the product to inspecting the result.Understand and chooseDesign workflowCompose and expressDesign workflowBuild and interactDesign workflowVerify and reviseDesign workflowCommands & promptsWays to ask your assistant to use Glyph.Request conventionsCommands & promptsAn example briefCommands & promptsGuidance & exceptionsUnderstand requirements, patterns and design judgment.Instruction rolesGuidance & exceptionsWhen to break a patternGuidance & exceptionsResearch with referencesGuidance & exceptionsSkill filesRead the actual Markdown included in the skill.Explore the sourceSkill filesLoad guidance selectivelySkill filesCustomizationAdapt Glyph to your brand and project.Bring your own directionCustomizationWrite useful constraintsCustomizationTroubleshootingResolve installation, discovery and output issues.The assistant cannot find GlyphTroubleshootingThe result feels genericTroubleshootingCopy or theme is unavailableTroubleshootingVerificationCheck the implementation and report evidence honestly.Before shippingVerificationEvaluating the skillVerificationCurrent evidence limitsVerificationSources & licenseAttribution, license and reference use.Source acknowledgmentsSources & licenseMIT licenseSources & license
Tab to move · Enter to open · Esc to close