Skip to content
Back to skills

Use Brainstorm Mtthsnc Autonome 2

ASecurity

Use before any creative work - creating features, building components, adding functionality, or modifying behavior to explore intent, requirements, and design before implementation.

  • 666 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 2, 2026
ai-agentstestingdocumentation

Security analysis

A100/100

Scanned September 2, 2026

npx -y skills add majiayu000/claude-skill-registry --skill use-brainstorm-mtthsnc-autonome-2 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Use Brainstorm Mtthsnc Autonome 2?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Use Brainstorm Mtthsnc Autonome 2
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-use-brainstorm-mtthsnc-autonome-2/badge)](https://www.skillsdirectory.com/skills/majiayu000-use-brainstorm-mtthsnc-autonome-2)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: use-brainstorm
description: "Use before any creative work - creating features, building components, adding functionality, or modifying behavior to explore intent, requirements, and design before implementation."
---

You help turn ideas into validated designs through collaborative dialogue, then guide the transition to implementation.

# How to Brainstorm

1. **Understand the idea**:
   - Check current project state (files, docs, commits)
   - Ask questions one at a time (prefer multiple choice when possible)
   - Focus on: purpose, constraints, success criteria

2. **Explore approaches**:
   - Propose 2-3 different approaches with trade-offs
   - Lead with your recommended option and explain why
   - Present conversationally with reasoning

3. **Present the design**:
   - Break into sections of 200-300 words
   - Ask after each section whether it looks right so far
   - Cover: architecture, components, data flow, error handling, testing
   - Be ready to clarify if something doesn't make sense

# After Design Validated

**Documentation:**
- Write design to `docs/plans/YYYY-MM-DD-<topic>-design.md`
- Use elements-of-style:writing-clearly-and-concisely if available
- Commit the design document

**Implementation (if continuing):**
- Ask: "Ready to set up for implementation?"
- Use autonome:use-worktrees to create isolated workspace
- Use autonome:use-plan-create to create detailed implementation plan

# Core Principles

- **One question at a time** - Don't overwhelm with multiple questions
- **Multiple choice preferred** - Easier to answer when possible
- **YAGNI ruthlessly** - Remove unnecessary features from designs
- **Explore alternatives** - Propose 2-3 approaches before settling
- **Incremental validation** - Present in sections, validate each
- **Be flexible** - Clarify when something doesn't make sense

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.