Voice & imagery
Current Tectra wording · shared Cosmik v0.16.1 rules
Product presentation comes from the current family guide. General writing and imagery rules below follow the pinned foundation. Its superseded organization-positioning section is omitted here; see current Cosmik positioning. The vendored source remains unchanged.
Product presentation#
Tectra helps people create and revise 3D structures through conversation. Lead with Create structures for worlds real or imagined. Explain the concrete workflow nearby: describe a structure, inspect the proposed revision, and direct what changes next. “Describe the space. Shape what comes next.” is a supporting product line, not a Cosmik-wide motto.
Audience and value#
Show a creator developing a structure for a scene or world: changing an opening, reworking a roof or refining a material. The distinctive story is a construction made of connected parts that can be revised and reviewed. AI assistance explains how the person directs it; “AI-powered” alone does not explain its value.
Demonstrate one understandable use case at a time. A first marketing example need not define the full product scope. Vary examples over time so the identity does not imply only buildings, one architectural style or one game engine. Do not promise support for an audience's workflow until the relevant outcome is verified.
Scope and availability#
Describe checked declared rules, not a guarantee that a structure “works” in every sense. Dimensional examples do not establish building-code compliance, structural safety, manufacturing suitability or professional approval. Name the rule and show the finding when explaining a check. Preserve the distinction between a proposed revision and one the person has accepted.
Do not promise that every edit preserves all other geometry, that an agent always succeeds, or that the person will never need another tool. Explain what the person can inspect and decide. Exports, integrations and material behavior should be named at their tested scope; an export format does not prove compatibility with every application that can open it.
Tectra is in development. A working feature in a private build is not public availability. Pricing, access and any free-credit allowance remain undecided; do not promise a free tier, credits, a trial, a price or a release date. Commercial terms belong beside the decision they affect once settled, not in the headline.
Voice, imagery and next steps#
Keep artistic direction with the creator. Write plainly about describing, inspecting, revising and exporting. The mineral palette, restrained teal and clear typography frame the work without recoloring it or prescribing its style.
Prefer a real revision sequence and representative output. Label prepared examples, illustrative diagrams and hypothetical values where they appear. Never present a mock conversation or conceptual viewport as a real customer result or app capture.
Tectra leads its marketing, application, documentation and integrations. Use a quiet “By Cosmik” in the footer or About context, separate from the product logo. Give interested visitors a real product-specific next step: a maintained development update or a way to ask about Tectra while access is unavailable. Add “Open app” or “Sign in” only when that destination is available to the intended visitor.
Useful, direct language#
Write like an independent developer sharing useful work: say what a project does, what works today and what someone can do next. Use “I” for Matthew's personal updates and “Cosmik” for neutral descriptions. Do not imply a larger team or write like a press release. Use plain American English in interface copy.
Labels name the task: “Export”, “Save changes”, “Choose folder”. Use sentence case, specific verbs and familiar nouns. Explain an unfamiliar setting directly beside it; a tooltip may carry optional detail, but not the information needed to decide. Do not expose internal service names or implementation details unless they help the person solve the problem.
| Situation | Say | Avoid |
|---|---|---|
| Pending work | What is happening, with real progress when known | A fake percentage or reassurance unsupported by the operation |
| Error | What failed, what was preserved and the next useful action | “Something went wrong” without recovery or blaming the user |
| Empty collection | What belongs here and the relevant first action | Repeated onboarding copy after every empty search |
| Confirmation | The item and consequence of the action | An unexplained “Are you sure?” |
| Product update | What now works, its build or version and remaining limits | Announcing a plan as a shipped feature |
Do not repeat the same explanation in a heading, subtitle and helper. Short does not mean cryptic: keep important consequences and limitations visible. Product copy can be confident without exaggerated claims or decorative slogans.
Imagery and icons#
Use real project screenshots, diagrams or relevant artwork when they explain the work. Label illustrative examples and hypothetical data. Do not publish private project screenshots without authorization. Preserve proportions and crop only when the essential information remains visible.
Keep genre imagery inside the project it belongs to. Avoid generic space wallpaper, decorative starfields and artificial glow as default Cosmik styling. A product's interface frames the user's work; its accent colour must not recolour that work.
Utility icons use a consistent stroke family and alignment. Give meaningful icons an accessible name through their control; hide decorative icons from assistive technology. Pair unfamiliar symbols with words. Use the same icon for the same action across the product, and distinguish different actions even when their names are similar. Icons and marks are different assets: do not adapt a logo into a generic toolbar glyph.
Identity animation#
A centred emblem sliding left to reveal lettering remains an exploration, not an approved deliverable. Keep recurring branding static. A logo reveal must never delay essential content. All interface motion, including reduced-motion behavior, follows the dedicated motion guide.