Skip to content

Latest commit

 

History

9 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

OpenCoven UI

Standalone interface specimens and design artifacts for OpenCoven.

OpenCoven UI component browser showing the editorial Messages specimen on desktop

What this repository is

OpenCoven UI is a small, inspectable workspace for exploring interface direction before it enters a production application. The current artifact, Components.dc.html, is a self-contained HTML, CSS, and JavaScript component browser with no dependency installation or build step.

This repository is not a packaged component library, production app, or canonical source for Coven Cave components.

Component states

Use the specimen navigation to move between four interface states:

State Purpose
Composer Keeps drafting, context, model, and send controls legible without competing with the message.
Messages Presents a familiar response as an editorial turn with clear identity, provenance, response, and utility hierarchy.
Context Makes attached repositories, files, branches, and access state explicit.
Actions Uses direct verbs, visible consequences, and secondary keyboard cues.

The browser preserves visible focus states, arrow-key navigation, reduced-motion handling, and a responsive layout without horizontal overflow at 390px.

Open locally

git clone https://github.com/OpenCoven/ui.git
cd ui
open Components.dc.html

No install step is required. On platforms without the macOS open command, open Components.dc.html directly in a browser.

Responsive behavior

The same Messages hierarchy contracts naturally on narrow screens while keeping the response aligned beneath Cody's identity.

OpenCoven UI editorial Messages specimen at a 390 pixel mobile viewport

Repository map

Path Purpose
Components.dc.html Self-contained interactive component browser
artifacts/ Verified desktop and mobile visual receipts
docs/superpowers/specs/ Approved design decisions
docs/superpowers/plans/ Implementation plans and verification steps
handoffs/ Completion and validation receipts

Contributing

When changing a specimen:

  1. Keep the browser self-contained unless a separately approved design changes the repository architecture.
  2. Preserve all four states and the existing navigation semantics.
  3. Verify embedded JavaScript parsing, four-state selection, arrow-key navigation, and 390px horizontal overflow.
  4. Refresh both desktop and mobile screenshots when visual behavior changes.
  5. Record exact commands and results in the relevant handoff receipt.

The current implementation plan contains the exact specimen verification commands.

Design provenance

About

Reference interface components, UI explorations, and design artifacts for OpenCoven products.

Topics

Resources

Contributing

Security policy

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages