How do I install the Think First skill?

Run npx skillmds@latest add ofershap/think-first 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 Think First safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Think First?

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 Think First free to use?

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

Who published Think First?

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

Think First by ofershap — Agent Skill

Name: Think First
Rating: 4.2 (5 reviews)
Author: ofershap

File contents

When to use

This skill is always active. It changes how the AI agent approaches every task - from "dive into code" to "understand first, plan second, implement third."

Critical Rules

1. Read Before Writing

Wrong: Immediately start editing files based on the user's request Correct: First read all relevant files, understand the existing code structure, patterns, and conventions

2. Understand the Full Picture

Wrong: Fix the symptom without understanding the root cause Correct: Trace the issue through the codebase - understand data flow, dependencies, and side effects

3. Check If It Already Exists

Wrong: Create a new utility function without checking if one exists Correct: Search the codebase for existing implementations before creating new ones

4. Propose a Plan for Complex Changes

Wrong: Start implementing a multi-file change without explaining the approach Correct: For changes touching 3+ files, outline the plan: what files change, what the approach is, what the risks are

5. Identify Affected Areas

Wrong: Make a change without considering what else it affects Correct: Before implementing, identify all files, tests, and features that could be affected

6. Consider Alternatives

Wrong: Implement the first approach that comes to mind Correct: For non-trivial changes, briefly consider 2-3 approaches and explain why you chose one

7. Verify Assumptions

Wrong: Assume a function exists or works a certain way Correct: Read the actual code to verify before building on assumptions

8. Minimal Change Principle

Wrong: Refactor everything while fixing a bug Correct: Make the smallest change that solves the problem - separate refactoring from bug fixes

9. Test Awareness

Wrong: Make changes without considering how to verify them Correct: Before implementing, identify how the change will be tested - existing tests, new tests, manual verification

10. Context Preservation

Wrong: Lose track of the original goal while exploring tangential issues Correct: Stay focused on the user's request - note tangential issues but don't chase them

---name: think-firstdescription: Stop your AI agent from coding before thinking. Enforces plan-first workflow to reduce backtracking and wasted tokens.---## When to useThis skill is always active. It changes how the AI agent approaches every task - from "dive intocode" to "understand first, plan second, implement third."## Critical Rules### 1. Read Before WritingWrong: Immediately start editing files based on the user's request Correct: First read all relevantfiles, understand the existing code structure, patterns, and conventions### 2. Understand the Full PictureWrong: Fix the symptom without understanding the root cause Correct: Trace the issue through thecodebase - understand data flow, dependencies, and side effects### 3. Check If It Already ExistsWrong: Create a new utility function without checking if one exists Correct: Search the codebase forexisting implementations before creating new ones### 4. Propose a Plan for Complex ChangesWrong: Start implementing a multi-file change without explaining the approach Correct: For changestouching 3+ files, outline the plan: what files change, what the approach is, what the risks are### 5. Identify Affected AreasWrong: Make a change without considering what else it affects Correct: Before implementing, identifyall files, tests, and features that could be affected### 6. Consider AlternativesWrong: Implement the first approach that comes to mind Correct: For non-trivial changes, brieflyconsider 2-3 approaches and explain why you chose one### 7. Verify AssumptionsWrong: Assume a function exists or works a certain way Correct: Read the actual code to verifybefore building on assumptions### 8. Minimal Change PrincipleWrong: Refactor everything while fixing a bug Correct: Make the smallest change that solves theproblem - separate refactoring from bug fixes### 9. Test AwarenessWrong: Make changes without considering how to verify them Correct: Before implementing, identifyhow the change will be tested - existing tests, new tests, manual verification### 10. Context PreservationWrong: Lose track of the original goal while exploring tangential issues Correct: Stay focused onthe user's request - note tangential issues but don't chase them

Frequently asked questions

Think First