Local Companion guidelines
Brand essentials
Approved name, visual signatures, assets, and usage rules.
Name and relationship
Approved name: Local Companion
Relationship: A ShruggieTech project
Visual signatures
Mark: The calm orbit places a centered disc inside two open bands. The open shape suggests an owner-controlled space with room for different companions. A thicker Reduced master keeps the same center and opening clear at small icon sizes.
Color: Graphite provides a quiet desktop canvas and indigo carries the product identity. Use the accessible darker indigo on light surfaces. Functional interface cues are measured separately and include text, shape, or control-state cues.
- Companion indigo:
#8B9CFF - Graphite mark ink:
#F4F6FB
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: Full 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 reduced mark takes over at and below 32 px.
Usage limits
Keep the delivered artwork geometry unchanged. The Logo page has the complete mark rules.
- Do not substitute the rejected LC monogram or W placeholder packaging icon.
- Do not combine companion character imagery with the product mark.
- Do not rotate, skew, stretch, outline, bevel, or glow the mark.
- Use the reduced master at and below 32 pixels.
Local Companion is the workspace identity. A companion portrait or conversation belongs to its own context and should not become the default product mark or a public sample without separate approval.
Implementation authority
An interface is the controls, layout, and feedback a person uses. This brand uses its own delivered interface rules and approved identity. Its palette is independent of ShruggieTech house styling.
Relationship: A ShruggieTech project
For the current published kit, inspect the public documentation facts (JSON). Example query: GET /local-companion/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.0.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/local-companion-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.