<span class="home-wordmark"><strong>Duck<span>!</span></strong><small>SoloPM</small></span>

1. Brand foundation

Duck exists to reduce the repeated cost of returning to a project.

Projects rarely live in one place. Their working reality gets spread across folders, repositories, documents, notes, links, terminals, browser tabs, conversations, and project-specific tools.

Every return creates a reorientation task:

• What is this project?
• Where does it stand?
• What happened recently?
• What matters now?
• Where is the relevant material?
• How do I get back into the work?

Duck reduces the mechanical and cognitive cost of returning to a project.

2. Name architecture

The exclamation mark

The exclamation mark is part of the brand.

The name began with:

“Fuck, I don’t have a name for this.”

Duck! preserves that origin without requiring the story to be repeated every time the software enters a room.

3. Positioning

What Duck is

Duck is a local-first project workspace built around one person’s view of their work.

It gives the user one place to see:

• what a project is;
• why it exists;
• where it stands;
• what happened;
• what needs attention;
• which resources belong to it;
• where the work actually happens.

The Local Folder remains the project.

Duck adds an orientation and management layer around the work instead of moving the work into a separate proprietary universe.

The pressure condition

Duck works with one project.

Its value becomes more obvious when many projects remain ongoing, unfinished, interrupted, and capable of demanding context at any time.

The user’s space

Duck is the user’s own coherent view across their project work.

What Duck is not

Duck is not:

• a Gantt chart;
• a sprint ceremony system;
• a productivity lifestyle;
• a workflow engine waiting to become another job;
• a replacement for local folders and files;
• an excuse to manufacture process.

4. Core brand idea

Primary line

Quick clarity across tons of ongoing projects.

Founder statement

I made Duck! to get quick clarity and fast pivoting across tons of ongoing projects—to fend off cognitive burn.

Functional explanation

Duck keeps each project’s context, status, activity, resources, files, and working locations within immediate reach.

Product standard

Duck should help the user understand, access, or resume a project with less mechanical and cognitive friction.

5. Logo system

Duck uses a wordmark-first identity.

The identity does not depend on an illustrated duck, mascot, arrow, folder, route, node, path, or symbolic diagram of project management.

The name already has personality. The visual system does not need to hire a small bird to explain the product with props.

Primary wordmark

Reversed wordmark

Formal product lockup

Compact interface badge

The compact badge is used for app icons, favicons, navigation bars, launchers, sidebars, repository avatars, and constrained interface spaces.

<span class="duck-mark__letter">D</span>
<span class="duck-mark__bang">!</span>

<span class="duck-mark__letter">D</span>
<span class="duck-mark__bang">!</span>

The badge contains:

• a Duck Ink container;
• a large white D;
• a separate orange !;
• rounded corners;
• no gradients;
• no bird illustration;
• no additional symbol.

The D carries most of the visual weight. The exclamation mark remains clearly separate to its right.

Badge HTML

<span class="duck-mark" role="img" aria-label="Duck!">
  <span class="duck-mark__letter">D</span>
  <span class="duck-mark__bang">!</span>
</span>

Use

• Use Duck! as the primary visible brand.
• Keep the D white and the exclamation mark orange inside the badge.
• Keep the badge background Duck Ink.
• Keep SoloPM visually subordinate.
• Use the compact badge in constrained interface spaces.
• Leave clear space around the wordmark.
• Preserve the badge proportions at every size.
• Test the smallest mark at actual favicon size.

Do not use

• Do not use an illustrated duck as the primary logo.
• Do not combine a duck with a folder, arrow, node, or route.
• Do not place the exclamation mark inside the D.
• Do not compress the characters until they collide.
• Do not use gradients, gloss, bevels, or dimensional effects.
• Do not make the whole wordmark orange.
• Do not give SoloPM equal visual weight.
• Do not add a slogan inside the logo lockup.

6. Color system

Duck uses a quiet base with one sharp accent.

Core tokens

:root {
  --duck-ink: #243746;
  --duck-slate: #526775;
  --duck-orange: #f97316;
  --duck-paper: #f7f5f1;
  --duck-white: #ffffff;
  --duck-mist: #e9edf0;
  --duck-line: #d4dce1;
}

Duck Ink

Use for primary text, large dark surfaces, navigation, app-icon backgrounds, and strong structural elements.

Duck Slate

Use for secondary text, descriptions, metadata, and the quieter SoloPM descriptor.

Duck Orange

Use for the exclamation mark, primary actions, active emphasis, and selected states.

Orange is an accent, not wallpaper.

When everything is orange, the interface has simply become a traffic cone.

Functional colors

Status colors remain functional interface colors rather than core identity colors.

:root {
  --duck-success: #2f9e61;
  --duck-warning: #d9841c;
  --duck-danger: #c34a3d;
  --duck-info: #3977a8;
}

7. Typography

Duck uses system fonts.

Sans-serif stack

font-family:
  system-ui,
  -apple-system,
  BlinkMacSystemFont,
  "Segoe UI",
  Roboto,
  Helvetica,
  Arial,
  sans-serif;

Monospace stack

font-family:
  ui-monospace,
  "SFMono-Regular",
  Menlo,
  Monaco,
  Consolas,
  "Liberation Mono",
  "Courier New",
  monospace;

System fonts:

• render quickly;
• work offline;
• fit naturally into desktop and web interfaces;
• avoid third-party font dependencies;
• remain readable across operating systems;
• keep the identity focused on structure, color, language, and use.

Duck should not have to wait for a font request before remembering where the repository is.

8. Voice

Duck sounds:

• direct;
• concrete;
• capable;
• independent;
• observant;
• slightly irreverent;
• personal when the founder perspective matters.

Duck does not sound:

• promotional;
• motivational;
• inflated;
• corporate;
• cute;
• overly polished;
• impressed with itself.

Tell the work truth

Name the actual friction, behavior, and value.

Do not dress ordinary functions in revolutionary clothing.

Prefer concrete language

Say folder, repository, status, document, terminal, link, activity, context, current state, and next action.

Avoid abstraction when a concrete word exists.

Use first person where it belongs

The founder voice belongs in the origin, reasoning, and product philosophy.

It does not need to dominate installation instructions or interface labels.

Do not perform personality

Humor should come from an accurate observation or honest irritation.

Do not glue a joke onto every paragraph merely because the brand is allowed to possess a pulse.

9. Language

Language that belongs

• quick clarity;
• fast pivoting;
• tons of ongoing projects;
• cognitive burn;
• where things stand;
• get back into the work;
• find what I need;
• local-first;
• one person’s view;
• project context;
• working locations;
• reorientation;
• current state;
• immediate reach.

Language to avoid

• juggling;
• seamless;
• empower;
• unlock;
• effortless;
• supercharge;
• all-in-one;
• productivity hub;
• work smarter;
• game-changing;
• transform your workflow;
• one source of truth;
• maximize productivity;
• next-generation;
• revolutionary;
• intuitive solution.

These phrases usually arrive with no evidence and several gradients.

10. Messaging hierarchy

Primary headline

Quick clarity across tons of ongoing projects.

Founder statement

I made Duck! to get quick clarity and fast pivoting across tons of ongoing projects—to fend off cognitive burn.

Short description

Duck SoloPM is a local-first project workspace built around quick reorientation.

Functional description

Duck keeps each project’s context, status, activity, resources, files, and working locations within immediate reach.

Local-first explanation

The Local Folder remains the project. Duck adds a clear management layer around the work instead of moving it into a separate document system.

Activity explanation

Notes, Todos, Statuses, Links, and Files stay in one chronological project stream.

Reorientation explanation

Open a project, see where it stands, find what you need, and get back into the work.

Product principle

The point is not to keep the user inside Duck. The point is to make Duck the fastest place to understand where to go next.

11. Messaging examples

Say this

See where the project stands, find what you need, and get back into the work.

Not this

Seamlessly juggle your projects and unlock effortless productivity from one powerful hub.

Say this

The project folder remains the project.

Not this

Bring all your work into one revolutionary productivity ecosystem.

Say this

Duck keeps the repository, folder, files, activity, status, and next work close.

Not this

Duck empowers modern professionals to streamline complex workflows.

12. Interface principles

Dense enough to orient

Meaningful project state should be visible without excessive opening, browsing, or drilling down.

Density is useful when it reduces searching.

Density becomes clutter when it removes hierarchy.

Quiet enough to think

The interface should not compete with the work.

Avoid:

• decorative widgets;
• unnecessary animation;
• persistent pop-ups;
• oversized empty regions;
• repeated confirmation rituals;
• controls without immediate value;
• branding inserted into routine tasks.

Show what matters first

Prioritize:

• project identity;
• current state;
• next action;
• recent activity;
• open Todos;
• important resources;
• direct access to working locations.

Use orange sparingly

Orange identifies the principal action, active emphasis, the exclamation mark, and selected states where appropriate.

Do not use orange for every clickable object.

Preserve directness

Links should open the relevant resource.

Files should remain ordinary files.

A project folder should remain the project folder.

The interface should not create extra layers merely to prove it has architecture.

13. Brand review checklist

Before publishing a Duck page or interface, check:

• Is the product named Duck! or Duck SoloPM correctly?
• Is SoloPM subordinate to Duck!?
• Is the compact badge using a white D and orange !?
• Are system fonts being used?
• Is orange functioning as an accent rather than a flood?
• Does the language name concrete project friction?
• Does the copy avoid inflated productivity claims?
• Is the founder voice being used where it adds context?
• Is the page helping the user understand Duck rather than trying to persuade them through fog?
• Could anything be removed without losing meaning?

If the answer to the last question is yes, remove it.

The brand also has to protect cognitive bandwidth.