asking-questions
Asking Questions
Purpose
Ask clarifying questions when the answer materially changes what you'll build. This skill helps identify when to ask, how to structure questions effectively, and when to proceed autonomously.
When to Use
Ask questions for:
- Ambiguous implementation choices - Multiple valid technical approaches (middleware vs wrapper functions, library selection, architectural patterns)
- Missing critical context - Specific information needed (database type, deployment platform, credential management)
- Potentially destructive actions - Requests that could be interpreted dangerously ("clean up files" = delete vs archive)
- Scope clarification - Vague terms like "refactor," "optimize," or "improve"
- Conflicting requirements - Goals that may work against each other ("make it faster" + "add extensive logging")
- Technical trade-offs - Solutions with different costs/benefits depending on priorities
When NOT to Use
More from arielperez82/agents-and-skills
algorithmic-art
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.
16problem-solving
Apply systematic problem-solving techniques for complexity spirals (simplification
15markdown-syntax-fundamentals
Use when writing or editing markdown files. Covers headings, text formatting, lists, links, images, code blocks, and blockquotes.
15research
Use when you need to research, analyze, and plan technical solutions that are scalable, secure, and maintainable.
14brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
14docs-seeker
Search technical documentation using executable scripts to detect query
14