explore

Explore codebases and clarify requirements without writing code.

3|1|Updated Apr 13, 2023
One-click install
npx skills add https://github.com/detorresramos/CaramelDB --skill explore-detorresramos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: explore
Source: https://github.com/detorresramos/CaramelDB/tree/main/.claude/skills/explore
Command: npx skills add https://github.com/detorresramos/CaramelDB --skill explore-detorresramos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enter explore mode to think deeply about problems and clarify requirements before implementing. You may read files, search code, and investigate the codebase, but you must NEVER write code or implement features.

Core Features & Use Cases

  • Thinking partner for exploring ideas, debugging problems, and clarifying requirements without making changes to the codebase.
  • Open-ended exploration that surfaces multiple directions, asks questions, and visualizes concepts with ASCII diagrams.
  • Guardrails to keep discussions non-prescriptive and focused on understanding rather than execution.

Quick Start

Enter explore mode and think deeply about the user's goal before implementing.

Frequently Asked Questions about explore

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I explore ideas and clarify requirements before writing code?

To explore ideas and clarify requirements before writing code, you can use a thinking partner mode that allows you to read files, search the codebase, and discuss problem framing without implementing features.

What is the best way to investigate a codebase without making changes?

The best way to investigate a codebase without making changes is to enter a non-prescriptive exploration mode that applies safety guardrails to prevent unintended modifications while you analyze files and requirements.

Can I visualize concepts and problem directions during a design discussion?

Yes, you can visualize concepts during design discussions by using ASCII diagrams generated through open-ended exploration, which surfaces multiple directions and asks questions to frame the problem.

Does this exploration mode write or modify code in the codebase?

No, this exploration mode does not write or modify code in the codebase; it enforces strict guardrails to keep discussions focused on understanding, problem-solving, and clarifying requirements.

When do I need to use a thinking partner for problem framing?

You need to use a thinking partner for problem framing when you must clarify requirements, debug problems, or deeply understand a codebase before moving into actual implementation and execution.