ork-brainstorm
Compare plausible implementation, architecture, product, or operational approaches before committing to one. Use when a request asks to brainstorm, think through options, choose an approach, evaluate trade-offs, or resolve significant uncertainty before implementation. Do not use for an already specified mechanical change.
git clone --depth 1 https://github.com/yonatangross/orchestkit /tmp/ork-brainstorm && cp -r /tmp/ork-brainstorm/plugins/ork-codex/skills/ork-brainstorm ~/.claude/skills/ork-brainstormSKILL.md
# Ork Brainstorm Frame the outcome, constraints, non-goals, and decision deadline. Inspect the relevant repository and existing decisions before proposing options. Generate two to four materially different approaches. For each, state the implementation shape, benefits, costs, risks, dependencies, reversibility, and the evidence that would disprove it. Do not pad the list with cosmetic variations. When an option depends on what a library, framework, or service can actually do today, confirm it with the context7 MCP server (`resolve-library-id`, then `query-docs`) before scoring it. An option built on a capability you only remember is an assumption, and it belongs in the unresolved list. Use one context for a normal decision. Delegate only when there are at least three independent unknowns; give each subagent one bounded question and synthesize its evidence. Prefer the installed `ork_explorer` role when available, otherwise use Codex's built-in `explorer` role. End with a recommendation, the decision rationale, unresolved assumptions, and the smallest next action. Do not edit files until the user asks to implement the chosen approach.
Accessibility patterns for WCAG 2.2 compliance, keyboard focus management, React Aria component patterns, cognitive inclusion, native HTML-first philosophy, and user preference honoring. Use when implementing screen reader support, keyboard navigation, ARIA patterns, focus traps, accessible component libraries, reduced motion, or cognitive accessibility.
Agent orchestration patterns for agentic loops, multi-agent coordination, alternative frameworks, and multi-scenario workflows. Use when building autonomous agent loops, coordinating multiple agents, evaluating CrewAI/AutoGen/Swarm, or orchestrating complex multi-step scenarios.
AI-assisted UI generation patterns for json-render, v0.app, Google Stitch, Bolt Cloud, and Cursor workflows. Covers prompt engineering for component and full-stack app generation, review checklists for AI-generated code, design token injection, refactoring for design system conformance, and CI gates for quality assurance. Use when generating UI components with AI tools, rendering multi-surface MCP visual output, reviewing AI-generated code, or integrating AI output into design systems.
Queries local analytics across OrchestKit projects for agent usage, skill frequency, hook timing, team activity, session replay, cost estimation, and model delegation trends. Privacy-safe with hashed project IDs. Supports time-range filtering and comparative analysis. Use when reviewing performance, estimating costs, or understanding usage patterns.
Animation and motion design patterns using Motion library (formerly Framer Motion) and View Transitions API. Use when implementing component animations, page transitions, micro-interactions, gesture-driven UIs, or ensuring motion accessibility with prefers-reduced-motion.
API contract design for REST and GraphQL, covering resource shape, URL and header versioning with deprecation windows, RFC 9457 Problem Details error handling, and OpenAPI specs. Use when specifying the wire contract an endpoint exposes, choosing a versioning scheme, or standardizing error response bodies across services. Framework-agnostic protocol layer, not runtime implementation.
ADR templates in the Nygard format with context, decision, consequences, and alternatives. Use when writing ADRs, recording an architectural decision, or evaluating options.
Architecture validation and patterns for clean architecture, backend structure enforcement, project structure validation, test standards, and context-aware sizing. Use when designing system boundaries, enforcing layered architecture, validating project structure, defining test standards, or choosing the right architecture tier for project scope.