Skip to content

oprogramadorreal/optimus-claude / skills/brainstorm

brainstorm

Verified

Runs a structured design conversation — clarifies intent, proposes 2-3 approaches with trade-offs, iterates the design — and writes a user-approved engineering spec to docs/specs/ that /optimus:tdd auto-detects. No implementation happens until the spec is approved. With the scaffold argument, creates docs/product/ steering skeletons instead (never overwrites, authors no content). Recommends /optimus:init first.

templates/product/tech-stack.md

View on GitHub
# Target Technology Stack

> **Altitude & precedence.** Part of a docs-first cascade — **product vision -> MVP PRD -> target tech-stack -> active build spec**. The full statement of what that means lives in [product vision](./product-context.md); the short version is that when these conflict about current work, the active build spec (in `docs/specs/`) wins.
> Siblings: [product vision](./product-context.md) · [MVP PRD](./mvp-prd.md).
>
> **What this document is.** The **target** stack the product grows toward — *not* a constraint on the
> current build. The active build spec uses only the small subset it needs. This is forward-looking
> product/architecture *planning*; it is distinct from any post-code structure notes your engineering
> setup keeps about the code as it actually exists.

## Core principles

> TODO — not yet decided. The few rules guiding technology choices (e.g. prefer popular,
> well-documented tools an AI agent can use reliably; keep the initial architecture simple).

## Selected stack

> TODO — not yet decided. Fill only the categories you need; leave the rest blank. For each, name the
> choice and one line on *why*.

- **Language:** TODO
- **Frontend:** TODO
- **Backend / API:** TODO
- **Data / persistence:** TODO
- **AI layer (if any):** TODO
- **Auth (if any):** TODO
- **Testing:** TODO
- **Observability:** TODO

## Architectural direction

> TODO — not yet decided. The shape of the system (e.g. modular monolith vs. separate services) and why.

## Adoption & phasing

> TODO — not yet decided. What to adopt now vs. add only when a real need appears.

## Notes for AI coding agents

> TODO — not yet decided. How an agent should use this doc. Typically: build to the current spec, not
> the full target; do not introduce major libraries without explaining why.
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies 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.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall