How do I install the Brainstorming Into Designs skill?

Run npx skillmds@latest add tomevault-io/brainstorming-into-designs in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Brainstorming Into Designs safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Brainstorming Into Designs?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Brainstorming Into Designs free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Brainstorming Into Designs?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Brainstorming Into Designs by tomevault-io

Name: Brainstorming Into Designs
Author: tomevault-io

Brainstorming Into Designs

Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Focuses on Java backend and React/Angular frontend integration.

tomevault-io Updated Sep 17, 2026

File contents

Brainstorming Ideas Into Designs

Overview

Help turn ideas into fully formed designs and specs through natural collaborative dialogue. Focus on how a feature lives in the Java backend and manifests in the React/Angular frontend.

Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design in small sections (200-300 words), checking after each section whether it looks right so far.

The Process

Understanding the idea:

Check out the current project state first (files, docs, recent commits) mainly those related to the idea.
Ask questions one at a time to refine the data flow: "Will this require a new database table (Flyway) or just a frontend state change?".
Ask about the UI framework choice: "Is this specific to the React implementation or the Angular alternative?".
Prefer multiple choice questions when possible.
Focus on understanding: purpose, constraints, and success criteria.

Exploring approaches:

Propose 2-3 different approaches covering:
- Backend: Entity design, DTO mapping (MapStruct), and Security.
- Frontend: Component structure, State management, and Styling (Tailwind).
Present options conversationally with your recommendation and reasoning.
Recommend the most "YAGNI" (You Ain't Gonna Need It) approach to keep the boilerplate clean.

Presenting the design:

Once you believe you understand what you're building, present the design in sections of 200-300 words.
Ask after each section whether it looks right so far.
Cover:
- Architecture & Data Flow: REST endpoints and JSON structures.
- Components & Validation: JSR-303 (Backend) and React Hook Form/Angular Reactive Forms (Frontend).
- Error Handling & Testing: Be ready to clarify if something doesn't make sense.

After the Design

Documentation:

Write the validated design to docs/plans/YYYY-MM-DD-<topic>/design.md.
Use elements-of-style:writing-clearly-and-concisely skill if available.

Implementation (if continuing):

Ask: "Ready to set up for implementation?".
Use writing-plans skill to create a detailed implementation plan.

Key Principles

One question at a time - Don't overwhelm with multiple questions.
Multiple choice preferred - Easier to answer than open-ended when possible.
YAGNI ruthlessly - Remove unnecessary features from all designs.
Explore alternatives - Always propose 2-3 approaches before settling.
Incremental validation - Present design in sections, validate each.
Be flexible - Go back and clarify when something doesn't make sense.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: brainstorming-into-designsdescription: Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Focuses on Java backend and React/Angular frontend integration.---# Brainstorming Ideas Into Designs## OverviewHelp turn ideas into fully formed designs and specs through natural collaborative dialogue. Focus on how a feature lives in the Java backend and manifests in the React/Angular frontend.Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design in small sections (200-300 words), checking after each section whether it looks right so far.## The Process**Understanding the idea:**- Check out the current project state first (files, docs, recent commits) mainly those related to the idea.- Ask questions one at a time to refine the data flow: "Will this require a new database table (Flyway) or just a frontend state change?".- Ask about the UI framework choice: "Is this specific to the React implementation or the Angular alternative?".- Prefer multiple choice questions when possible.- Focus on understanding: purpose, constraints, and success criteria.**Exploring approaches:**- Propose 2-3 different approaches covering: - **Backend**: Entity design, DTO mapping (MapStruct), and Security. - **Frontend**: Component structure, State management, and Styling (Tailwind).- Present options conversationally with your recommendation and reasoning.- Recommend the most "YAGNI" (You Ain't Gonna Need It) approach to keep the boilerplate clean.**Presenting the design:**- Once you believe you understand what you're building, present the design in sections of 200-300 words.- Ask after each section whether it looks right so far.- Cover: - **Architecture & Data Flow**: REST endpoints and JSON structures. - **Components & Validation**: JSR-303 (Backend) and React Hook Form/Angular Reactive Forms (Frontend). - **Error Handling & Testing**: Be ready to clarify if something doesn't make sense.## After the Design**Documentation:**- Write the validated design to `docs/plans/YYYY-MM-DD-<topic>/design.md`.- Use elements-of-style:writing-clearly-and-concisely skill if available.**Implementation (if continuing):**- Ask: "Ready to set up for implementation?".- Use writing-plans skill to create a detailed implementation plan.## Key Principles- **One question at a time** - Don't overwhelm with multiple questions.- **Multiple choice preferred** - Easier to answer than open-ended when possible.- **YAGNI ruthlessly** - Remove unnecessary features from all designs.- **Explore alternatives** - Always propose 2-3 approaches before settling.- **Incremental validation** - Present design in sections, validate each.- **Be flexible** - Go back and clarify when something doesn't make sense.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/rhorba) — claim your Tome and manage your conversions.

Frequently asked questions