Clarify goals and explore ideas with ASCII diagrams.
npx skills add https://github.com/ArtemYurov/TomoBar --skill aif-explore
Please help me install this Agent Skill. Skill: aif-explore Source: https://github.com/ArtemYurov/TomoBar/tree/main/.claude/skills/aif-explore Command: npx skills add https://github.com/ArtemYurov/TomoBar --skill aif-explore
Enter explore mode. Think deeply. Visualize freely. Follow the conversation wherever it goes.
IMPORTANT: Explore mode is for thinking, not implementing. You may read files, search code, and investigate the codebase, but you must NEVER write code or implement features. If the user asks to implement something, remind them to exit explore mode first (e.g., start with /aif-plan). You MAY update AI Factory context files (DESCRIPTION.md, ARCHITECTURE.md, RULES.md) if the user asks—that's capturing thinking, not implementing.
This is a stance, not a workflow. There are no fixed steps, no required sequence, no mandatory outputs. You're a thinking partner helping the user explore.
Describe a problem you want to think through and ask me to explore it.
High-intent search queries and answers about installing and using this skill.
To clarify requirements and explore ideas, use a thinking partner that helps you reason through problems, surface risks, and frame decisions without generating implementation code. You describe the problem, and the partner guides the exploration.
Design thinking involves reasoning through problems before implementation. A thinking partner helps by enforcing a stance of curiosity, asking open-ended questions, and visualizing concepts with ASCII diagrams to frame decisions.
Yes, you can read files, search code, and investigate the codebase to explore problems, but the thinking partner will not write code or implement features, ensuring the session stays focused on conceptual exploration.
You can visualize concepts during planning by using ASCII diagrams within a flexible conversation. This supports visual thinking by mapping out ideas, relationships, and system structures directly in text format.
You should not use an AI thinking partner when you are ready to implement features or write code. It is strictly for problem exploration and requirement clarification, so you must exit explore mode first to start coding.
The best way to frame decisions and surface risks is through open-ended conversation that proposes spikes or investigations, avoiding prescriptive steps to maintain a flexible, curious stance throughout the design session.
brandon-setegnExplore requirements, tradeoffs, and codebase context before implementation.
Globaly-IncGenerate technical specs, implementation plans, and SQL migration skeletons for Supabase applications.
KaimingWanCapture user principles as deduplicated rules in knowledge/rules.md.
agnt-ggTranslate task specifications into deterministic step-by-step implementation plans.
