dnhess

Spectra — Design skill for Claude Code

Design community

Multi-agent deliberation skills for Claude Code — structured design review and decision debate using blackboard architecture.

How to install Spectra

This entry records only its repository, not the path inside it, so there is no exact command to give. Open dnhess/spectra and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Spectra does

Multi-agent deliberation skills for Claude Code — structured design review and decision debate using blackboard architecture.

Alternatives in Design

Brainstorming — Transform rough ideas into fully-formed designs through structured questioning and alternative exploration 27.9k ★
Extract — Design System & Product Reverse-Engineering - Extract tokens, components, architecture, and PRDs from codebase 2.8k ★
Deep Code Review — Perform deep code review for Python and TypeScript focusing on architecture, design patterns, code quality, an 232 ★

README

Spectra

[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE) [![Lint](https://github.com/dnhess/spectra/actions/workflows/lint.yml/badge.svg)](https://github.com/dnhess/spectra/actions/workflows/lint.yml)

A local-first multi-agent deliberation runtime for structured review and debate using a **blackboard architecture** — every perspective refracted, every angle examined. Claude Code remains the default execution path; the provider-neutral runtime now also supports an opt-in, approval-gated Codex Quick peer-review opening phase.

Available Skills

deep-design

**Rigorous multi-perspective design review.** Use when a document, spec, or idea needs stress-testing from every angle before implementation. Produces a revised document with all findings incorporated.

Triggers: design docs, architecture specs, product requirements, feature proposals.

decision-board

**Structured multi-perspective debate.** Use when a decision needs structured debate before committing. Produces an Architecture Decision Record (ADR) with recommendation, dissent, and conditions.

Triggers: architectural decisions, technology selection, build-vs-buy, migration strategy.

peer-review

**Multi-perspective code review.** Use when code changes need thorough review from multiple specialist viewpoints before merge. Includes a Scout + Research reconnaissance phase that gathers codebase context and best practices before reviewers begin.

Triggers: pull requests, code changes, refactoring review.

trust-layer

**Adversarial verification for AI-generated output.** Use before accepting any AI-generated code, diff, file, or Spectra session recommendation. Four adversarial personas (Package Validator, Intent Auditor, Security Challenger, Coherence Checker) challenge the output from independent angles.

Triggers: AI-generated code, diffs, files, or Spectra session output needing verification before acceptance.