See it
in context.
Practical examples for using the Cortlet WebSocket CLI identity across repositories, terminal interfaces, documentation, and third-party integrations.
Before you start
Three rules.
Most cases covered.
Use the official assets
Use the supplied Cortlet WebSocket CLI logo and icon files rather than rebuilding or modifying them.
Name it consistently
Use Cortlet WebSocket CLI in product-facing copy and cortlet-ws for executable commands.
Keep relationships accurate
Describe compatibility factually without implying partnership, endorsement, or certification.
01 // Repository
README usage.
A repository is one of the clearest places to use the full product identity alongside technical naming.
Repository README
Use the Cortlet WebSocket CLI product identity in repository documentation when the CLI itself is the subject of the project or documentation.
Use the full product logo near the top of the README when the product name should be immediately recognizable.
Use cortlet-ws in commands, code examples, and terminal instructions.
Keep the product mark separate from repository metadata and ordinary documentation text.
Cortlet-Org / cortlet-ws
Public repository
Cortlet WebSocket CLI
A lightweight command-line tool for connecting to, testing, and inspecting WebSocket endpoints.
Quick start
$ cortlet-ws connect wss://example.dev
connected
Commands
cortlet-ws connectOpen a WebSocket connection.
cortlet-ws sendSend a message.
cortlet-ws pingTest endpoint responsiveness.
cortlet-ws inspectInspect connection details.
Product-led
The full logo appears where the Cortlet WebSocket CLI itself is the primary subject.
Technical naming
The formal product name is used in prose while cortlet-ws is reserved for commands and terminal contexts.
Unmodified
The official product logo and icon are used without rebuilding, recoloring, or distorting them.
02 // Terminal
CLI interface.
In terminal-focused experiences, the product icon can provide identity while the command-line interface stays primary.
Terminal interface
In terminal-focused interfaces, use the product icon as a compact identity while keeping command syntax in plain monospaced text.
Keep the icon separate from command output.
Use cortlet-ws exactly in terminal commands.
Let the technical interface stay primary instead of turning the product mark into decoration.
Cortlet WebSocket CLI
Interactive session
Cortlet WebSocket CLI
Use in product-facing copy, headings, and descriptive prose.
cortlet-ws
Use in commands, terminal output, code examples, and technical documentation.
Technical
The terminal experience remains functional and readable instead of becoming a decorative brand treatment.
Consistent naming
Cortlet WebSocket CLI identifies the product while cortlet-ws is reserved for executable commands.
Compact identity
The product icon provides recognizable branding without interfering with terminal output.
03 // Documentation
Documentation header.
Use the horizontal logo where the product itself needs to be clearly identified before documentation begins.
Documentation header
Use the full Cortlet WebSocket CLI logo where the product needs to be clearly identified at the start of documentation or a dedicated product area.
Use the full product logo in prominent introductory areas.
Keep documentation navigation and controls visually separate from the product mark.
Use cortlet-ws only when referring to the executable or command syntax.
Documentation for connecting to, testing, and inspecting WebSocket endpoints with Cortlet WebSocket CLI.
Getting started
Connect to a WebSocket endpoint
Use the connect command to open a WebSocket connection.
Product
Cortlet WebSocket CLI
Command
cortlet-ws
Explicit
The full product logo makes it immediately clear which documentation the user is reading.
Structured
Branding, navigation, prose, and code each have distinct visual roles.
Consistent naming
The formal product name is used in documentation while cortlet-ws remains the executable command.
04 // Third-party use
Integration listing.
When another product references compatibility, Cortlet should remain a secondary identity and the relationship language should stay descriptive.
Third-party integration
When another product references compatibility with the Cortlet WebSocket CLI, keep that product visually primary and use the Cortlet mark as a secondary integration identity.
Keep the third-party product's own identity primary.
Use the product icon alongside the full product name when identifying the integration.
Use descriptive wording such as “Works with Cortlet WebSocket CLI” without implying partnership or endorsement.
ACME
Developer platform
Integrations
Connect your developer tools.
Extend ACME with tools your development workflow already uses.
Neon
Serverless Postgres
Vercel
Deployment platform
Cortlet WebSocket CLI
WebSocket tooling
Compatibility
Works with Cortlet WebSocket CLI
Resend
Email infrastructure
Recommended
Works with Cortlet WebSocket CLI
Describes compatibility without suggesting a commercial or official relationship.
Avoid
Official Cortlet Partner
Avoid claims of partnership, certification, sponsorship, or endorsement unless Cortlet has explicitly authorized them.
Secondary
The third-party product remains the dominant identity while Cortlet appears only where the integration is referenced.
Descriptive
The wording explains compatibility without creating an unsupported relationship claim.
Recognizable
The official product icon and full product name make the integration easy to identify.
05 // Avoid
Incorrect usage.
A quick reference for common visual, naming, and relationship mistakes.
Incorrect usage
Keep the Cortlet WebSocket CLI identity recognizable and accurate. Don't alter the official assets, rename the product, or imply relationships that do not exist.
Don't stretch, recolor, rotate, crop, or decorate the product mark.
Don't rebuild the horizontal logo from separate text and icon elements.
Don't use unofficial names such as Cortlet WS in formal product-facing copy.
Don't imply partnership, certification, or endorsement without authorization.
01 // Avoid
Don't stretch
Preserve the original proportions.
02 // Avoid
Don't recolor
Use the official provided variants.
03 // Avoid
Don't rotate
Keep the mark in its original orientation.
04 // Avoid
Don't add effects
Avoid glow, shadow, outlines, and decoration.
05 // Avoid
Don't crop
The full product mark should remain visible.
06 // Avoid
Don't crowd
Give the mark enough surrounding space.
✓ Use
Cortlet WebSocket CLI
Use the full official product name in headings, descriptive copy, and formal references.
× Avoid
Cortlet WS
Avoid shortening or inventing alternate public-facing product names.
✓ Use
Works with Cortlet WebSocket CLI
Descriptive compatibility wording is appropriate when it accurately reflects the integration.
× Avoid
Official Cortlet Partner
Do not imply partnership, certification, sponsorship, or endorsement without authorization.
Use the official asset as supplied, preserve its proportions, and choose a variant with strong contrast against the background.
Recognition
Consistent treatment makes the Cortlet WebSocket CLI immediately recognizable across different contexts.
Accuracy
Correct names and relationship language prevent confusion about what the product is and how it relates to others.
Consistency
Using the official assets as provided keeps product identity aligned across websites, repositories, documentation, and interfaces.
Keep the
product recognizable.
Use the full horizontal logo where the product name needs to be immediately understood.
Use the standalone icon in compact interfaces and contexts where the product is already identified.
Use “Cortlet WebSocket CLI” in prose and “cortlet-ws” for commands and executable references.
Choose light or dark variants based on background contrast.
Keep third-party relationship language descriptive and accurate.
Never stretch, recolor, rotate, crop, rebuild, or decorate official assets.
Cortlet WebSocket CLI
Use it
consistently.
Get the official product assets, follow the naming guidance, and use these examples as the reference for implementation.