ShruggieTech guidelines
Brand essentials
Approved name, visual signatures, assets, and usage rules.
Name and relationship
Approved name: ShruggieTech
Approved words
- Slogan
- We’ll figure it out.
Visual signatures
Mark: The custom stylized shruggie face is paid artwork, not a Unicode glyph. Paired lockups use the complete arms, eyes, and smile. Standalone marks and application icons use the approved vivid face-only square projection.
Color: Pure black and restrained near-black surfaces carry the parent identity. Bright green marks identity, links, focus, and the shruggie face on dark surfaces. Accessible green replaces it for text on light surfaces. Orange remains rare emphasis.
- ShruggieTech green:
#2BCC73
Type: Display Space Grotesk; body Geist; mono Geist Mono. See Logo, Color, and Typography for detailed rules.
Where each asset belongs
Choose the delivered artwork for its declared surface, role, and size. The asset library contains every verified variant.
- Logos and lockups: Stacked logo lockup, full color, for dark backgrounds (Brand identity).
- Marks: Reduced brand mark, full color, for dark backgrounds (Brand identity).
- Social images: Social share image, full color, dark background (Social sharing).
- Web icons: Web maskable, opaque background (Web root).
The face-only reduced master is the standalone mark at every size. Use the supplied icon files for each platform.
Usage limits
Keep the delivered artwork geometry unchanged. The Logo page has the complete mark rules.
- Do not redraw, trace, or approximate the custom shruggie mark.
- Do not substitute the Unicode shruggie or any emoji for the mark.
- Do not distort, rotate, crop, outline, bevel, or add glow to the mark.
- Do not use the bright green for text or links on the light reading surface.
- Do not combine a sub-brand mark with the parent mark inside one lockup.
Implementation authority
An interface is the controls, layout, and feedback a person uses. This brand starts with shared ShruggieTech interface rules while keeping its own approved identity and any declared overrides.
For the current published kit, inspect the public documentation facts (JSON). Example query: GET /shruggietech/facts/documentation.json. The file declares schema version 1 and documentation contract version 1.2.0. A downloaded kit keeps its own pinned facts at enforcement/documentation-facts.json.
Interface overrides
No brand-specific interface overrides are declared. The delivered interface rules supply the default values for controls, layout, and feedback.
Versions and bindings
These version domains move independently. Match each integration to the exact files in the downloaded kit.
- Shared brand system
2.0.0- Interface rules
1.0.1- Component recipes
1.1.0- Web and React adapter
1.1.0- egui adapter
1.0.2- wordpress adapter version
1.0.0- BrandBuilder
3.0.1- Brand identity
1.1.1
Implementation files
- Default interface rules:
enforcement/interface-canon.json - Component recipes:
enforcement/component-recipes.json - Web and React adapter:
web/adapter.json - Web support coverage:
web/support-matrix.json - egui adapter:
native/egui/adapter.json - egui support coverage:
native/egui/support-matrix.json - wordpress adapter:
wordpress/adapter.json - wordpress support matrix:
wordpress/support-matrix.json - wordpress theme zip:
wordpress/shruggietech-stbb-theme.zip
The BrandBuilder system manual explains the shared architecture. The downloaded kit governs its pinned implementation bytes.
Get the kit
Download the kit for its approved assets, typography specimens, and exact implementation files. In a Next.js and Tailwind v4 project using the pinned shadcn CLI, the registry catalog lists available resources for discovery; an individual item URL supplies an installable theme or component. Open the catalog, choose the item your host needs, then follow the shadcn installation instructions. The catalog alone does not install a theme or the complete kit.