opencoven-design

Solid

Agent-operable design constraints for OpenCoven, Coven, harness cockpits, docs, and integration surfaces

AI & Automation 47 stars 26 forks Updated today MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
56
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# OpenCoven Design Skill Use this skill when designing or implementing OpenCoven/Coven interfaces, docs pages, diagrams, package README visuals, native companion surfaces, or agent-built UI components. OpenCoven should feel like collective intelligence plus controlled power: arcane but precise, technical not gimmicky, powerful not loud, minimal but symbolic. Core positioning: OpenCoven is an open ecosystem for persistent AI familiars: named agents with memory, tools, identity, roles, and continuity. It turns AI from a blank chatbox into a living workspace of agents that remember, coordinate, and belong to the user. ## Source Of Truth Read these local files before changing brand or UI behavior: - `DESIGN.md` - canonical brand and design system - `docs/BRAND.md` - brand asset index and usage summary - `docs/BRANDING-ADHERENCE.md` - current exceptions, risks, and hardening checklist - `brand/docs/BRAND-USAGE.md` - contributor PR checklist - `brand/ui/color-tokens.css` - canonical CSS color tokens - `brand/ui/typography.css` - canonical typography tokens Do not invent a separate design system. If this skill conflicts with `DESIGN.md`, follow `DESIGN.md` and update this skill. ## Brand Position Build for harness operators and developers, not a marketing toy. - The default feeling is a quiet command cockpit. - The product promise is durable AI systems that can stay: remember what matters, understand their purpose, use tools, coordinate with other agents, and remain unders...

Details

Author
OpenCoven
Repository
OpenCoven/coven
Created
4 months ago
Last Updated
today
Language
Rust
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Listed

design-system

Read and respect the active DESIGN.md before generating any UI / frontend code / dashboard / design artifact. Use the 4-level cascade exposed by `cortex-agent design resolved` to find the right spec. Use proactively when: generating UI code, dashboards, prototypes, prototypes that touch color/typography/spacing, brand-aligned assets, or any visual output. Don't use when: pure backend / data / logic work with no visual surface.

1 Updated today
Kucell
AI & Automation Listed

canvas-design

Design system framework. Use when the project needs this capability or the user / team manifest asks for it. Use for specialized `canvas-design` work when listed in TEAM.yaml or explicitly requested.

2 Updated today
rogue-dev-studio
Web & Frontend Featured

design-engineering

Load when reviewing UI code, designing a component or page layout, picking an easing curve or transition pattern, deciding whether something should animate at all, choosing an avatar/typography/color system, building an OKLCH palette or fixing contrast, writing UI copy or error messages, auditing for AI-default tells, code tells, or a11y misses, making a screen look less generated, consuming a project's DESIGN.md or .design tokens, writing design-system docs for agents, giving feedback through Agentation or a similar annotation tool, asking why a UI feels flat or unfinished, judging when delight earns its weight, deciding whether an interaction should make a sound, designing or generating UI sound effects (ElevenLabs or open-source), syncing sound to animation, scoring a product launch video or deriving its sound stem from the motion, cutting a multi-scene launch video so it reads as one camera move, creating or animating SVG (icons, mascots, logo reveals, video-to-vector), prototyping several directions behi

25 Updated 6 days ago
AgentsORG