How do I install the Solveit skill?

Run npx skillmds add majiayu000/solveit 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 Solveit 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 Solveit?

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

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

Who published Solveit?

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

Solveit by majiayu000 — Agent Skill

Name: Solveit
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

Solveit

Generate a structured learning guide for building a feature using the Pólya problem-solving method. Creates a self-contained Markdown document that guides the user through understanding, planning, executing, and reflecting on the implementation. Triggers on phrases like "create a solveit guide", "make a learning guide for", "solveit for", "guided problem-solving for", or when the user wants a documented curriculum for building a feature rather than real-time guidance.

majiayu000 8551ed8 2 files · 3.4 KB Updated Sep 9, 2026 567 repo stars

File contents

Solveit Guide Generator

Generate a structured, self-contained learning document based on George Pólya's "How to Solve It" method. The output is a Markdown file that guides the reader to build a feature themselves.

Key difference from Teach skill: Solveit produces a complete document upfront; Teach is interactive real-time guidance.

Core Principles

The human is the agent - The guide provides questions and structure; the reader does the thinking and coding
Tiny increments - 1-3 lines of code at a time, verified immediately
Stop when unfamiliar - Learning moments pause to explore new concepts
Document thinking - Reader writes answers down, not just thinks them

Pólya's Four Phases

Every chapter follows this structure:

Understand - What is the unknown? The data? The conditions? Can you restate it?
Plan - Have you seen similar problems? Can you solve a simpler version first?
Execute - Build in tiny steps, verify each one, prove correctness
Look Back - Check the result, generalize, identify the key insight

Workflow

1. Research First

Before writing the guide, thoroughly explore the codebase:

Use Glob/Grep to find relevant files
Read files that will be affected
Trace data flow and dependencies
Find similar implementations for reference

2. Generate the Guide

Create a document following the structure in references/document-structure.md.

Key elements:

Opening with challenge, target state, and learning objectives
Chapters following Pólya's 4 phases
Hidden solutions using <details> tags
Learning moments as blockquotes
Verification commands after each tiny increment
Progress checks between chapters
Final reflection and acid test

3. Output Location

Save to: history/YYYY-MM-DD-solveit-<kebab-case-title>.md

Create history/ directory if needed.

Critical Rules

Maximum 1-3 lines per code increment - Smaller than feels natural
Every increment has verification - Exact command, exact expected output
Solutions are hidden - Reader must try first
Be codebase-specific - Reference actual files with path/to/file.ex:line_number
No generic advice - Everything relates to THIS codebase

References

Document Structure - Complete template with all sections
Formatting Patterns - Code blocks, learning moments, details tags

---name: solveitdescription: Generate a structured learning guide for building a feature using the Pólya problem-solving method. Creates a self-contained Markdown document that guides the user through understanding, planning, executing, and reflecting on the implementation. Triggers on phrases like "create a solveit guide", "make a learning guide for", "solveit for", "guided problem-solving for", or when the user wants a documented curriculum for building a feature rather than real-time guidance.--- # Solveit Guide Generator Generate a structured, self-contained learning document based on George Pólya's "How to Solve It" method. The output is a Markdown file that guides the reader to build a feature themselves. **Key difference from Teach skill:** Solveit produces a complete document upfront; Teach is interactive real-time guidance. ## Core Principles 1. **The human is the agent** - The guide provides questions and structure; the reader does the thinking and coding 2. **Tiny increments** - 1-3 lines of code at a time, verified immediately 3. **Stop when unfamiliar** - Learning moments pause to explore new concepts 4. **Document thinking** - Reader writes answers down, not just thinks them ## Pólya's Four Phases Every chapter follows this structure: 1. **Understand** - What is the unknown? The data? The conditions? Can you restate it? 2. **Plan** - Have you seen similar problems? Can you solve a simpler version first? 3. **Execute** - Build in tiny steps, verify each one, prove correctness 4. **Look Back** - Check the result, generalize, identify the key insight ## Workflow ### 1. Research First Before writing the guide, thoroughly explore the codebase: - Use Glob/Grep to find relevant files - Read files that will be affected - Trace data flow and dependencies - Find similar implementations for reference ### 2. Generate the Guide Create a document following the structure in [references/document-structure.md](references/document-structure.md). Key elements: - Opening with challenge, target state, and learning objectives - Chapters following Pólya's 4 phases - Hidden solutions using `<details>` tags - Learning moments as blockquotes - Verification commands after each tiny increment - Progress checks between chapters - Final reflection and acid test ### 3. Output Location Save to: `history/YYYY-MM-DD-solveit-<kebab-case-title>.md` Create `history/` directory if needed. ## Critical Rules - **Maximum 1-3 lines per code increment** - Smaller than feels natural - **Every increment has verification** - Exact command, exact expected output - **Solutions are hidden** - Reader must try first - **Be codebase-specific** - Reference actual files with `path/to/file.ex:line_number` - **No generic advice** - Everything relates to THIS codebase ## References - [Document Structure](references/document-structure.md) - Complete template with all sections - [Formatting Patterns](references/formatting-patterns.md) - Code blocks, learning moments, details tags

Frequently asked questions