Socratic discovery and design exploration before planning. Activates when starting non-trivial work — asks clarifying questions, explores alternatives and tradeoffs, produces a design document for approval. Pulls context from Linear issue description, linked docs, and existing CLAUDE.md learnings. Simple bugs and fixes skip this automatically.
Facilitates design exploration through clarifying questions and produces a concise design document before implementation.
/plugin marketplace add https://www.claudepluginhub.com/api/plugins/brite-nites-britenites-plugins-britenites/marketplace.json/plugin install brite-nites-britenites-plugins-britenites@cpd-brite-nites-britenites-plugins-britenitesThis skill inherits all available tools. When active, it can use any tool Claude has access to.
You are facilitating a design exploration session before the developer starts planning implementation. Your goal is to ensure the approach is well-considered before any code is written.
Before asking questions, silently gather context:
Synthesize this into your understanding before engaging the developer.
Ask clarifying questions the developer might not have considered. Ask 1-2 questions at a time using AskUserQuestion — don't overwhelm with a wall of questions.
Areas to probe:
Adapt your questions to the issue. Don't ask about UI for a backend task. Don't ask about database schema for a CSS change. Be relevant.
After the conversation converges, produce a design document:
## Design: [Issue Title]
**Issue**: [ID] — [Title]
**Date**: [today]
### Problem
[1-2 sentences: what problem are we solving and why]
### Approach
[The chosen approach, clearly stated]
### Key Decisions
1. [Decision] — [Rationale]
2. [Decision] — [Rationale]
### Alternatives Considered
- **[Alternative A]** — [Why not chosen]
- **[Alternative B]** — [Why not chosen]
### Risks & Mitigations
- [Risk] → [Mitigation]
### Scope Boundaries
- **In scope**: [list]
- **Out of scope**: [list]
### Open Questions
- [Anything still unresolved — should be empty if brainstorming was thorough]
Present the design document and ask:
"Does this design look right? Any changes before we move to planning?"
If approved: Save the design document to docs/designs/[issue-id]-[slug].md (create the directory if needed). This document will be referenced during planning and execution.
If changes requested: Iterate on the specific sections, then re-present.
_shared/validation-pattern.md for self-checking.Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.