Log in GO PRO NOW
GO PRO NOW
Your workflow could help someone. Share it!

Guides Claude

How this Hidden “Insights” Feature Improves Claude Code

In this guide, you’ll learn how to use Claude Code’s hidden /insights feature to improve your coding habits.

beginner 5 steps

Introduction

In this guide, you’ll learn how to use Claude Code’s hidden /insights feature to improve your coding habits. You’ll generate a built-in report from your Claude Code history, review Claude’s feedback on your process, and turn the report’s recommendations into reusable CLAUDE.md instructions, custom skills, or hooks.

If `/insights` fails, close Claude Code with `ctrl + c` and reopen it to update Claude Code before trying again.

Step-by-step 5 steps

Instructions

  1. Step 1 of 5

    Generate your insights report

    Create an empty folder and open it in your IDE. Open a new terminal session and run: claude /insights.

    Pro tip: If this command fails, close Claude Code with ctrl + c and reopen it. This should update Claude Code if you needed an update to use /insights.
  2. Step 2 of 5

    Open the report

    Claude should begin working on your insights report. When it’s done, it will give you a link to a file named report.html. Copy it into your current folder.

    Start the webpage with cmd + shift + p and find the “Open Live Server” tool.

    Pro tip: You can also give the HTML file to Claude or ChatGPT and have them run it for you.
  3. Step 3 of 5

    Review your usage patterns

    Scroll through the report sections. Here’s some of what you’ll find:

    • What You Work On shows cards for each project you’ve used Claude Code on, with session counts and a summary of what happened. It also breaks down what you asked for most, which tools Claude used, what languages you work in, and your session types.
    • Impressive Things You Did highlights what went well across your sessions.
    • Where Things Go Wrong helps you learn where the disconnects are between you and Claude Code. It flags patterns like Claude ignoring your instructions, producing buggy code, or taking wrong approaches.
    image-2043
    image-2044
    image-2045
  4. Step 4 of 5

    Add suggested CLAUDE.md instructions

    Scroll down to “Existing CC Features to Try.” This section has copy-paste-ready lines for your CLAUDE.md.

    Each suggestion comes with a “Copy” button and an explanation of why it matters for you specifically. For example, if Claude keeps ignoring your theme preferences, you might see a CLAUDE.md line like this:

    Prompt 
    This project uses TypeScript with a custom shadcn/ui dark theme. ALWAYS use the initialized theme tokens instead of arbitrary Tailwind color classes.

    Open your CLAUDE.md in any project, paste in the suggestions you want, and Claude will follow them in future sessions.

  5. Step 5 of 5

    Set up custom skills and hooks

    The report also suggests Custom Skills and Hooks based on your patterns.

    image-2047

    Custom skills are reusable prompts you trigger with a single command. If you keep doing the same task over and over, such as generating CLAUDE.md files for new repos, the report will suggest turning that into a skill so it runs with one command instead of a full session.

    To set one up, paste the skill code from the report into Claude Code and say:

    Prompt 
    Set up this skill

    Claude creates it for you. You can then use it anytime with a custom slash command in Claude Code.

    Pro tip: To use newly installed skills, exit and restart Claude Code.

You're done

That's the whole workflow

Mark it complete to save your progress. Background and answers to common questions follow below.

Keep going

Keep learning with Rundown Pro

A guide shows you one workflow. Pro opens the full course library, so you can learn the whole system behind it.

  • Every on-demand course
  • Certifications on completion
  • Group office hours and member perks

$29/mo, cancel anytime

Overview Back to the steps

Background and context

Who This Is Useful For

  • Vibe coders who aren’t confident in their coding habits
  • Anyone curious what Claude Code thinks of their process
  • Data nerds interested in what tools and skills their Claude Code uses the most

What You Will Build

You’ll produce a local Claude Code insights report and reusable improvements for future coding sessions.

  • A report.html insights report generated by Claude Code
  • Copy-paste-ready CLAUDE.md instructions based on your patterns
  • Optional custom skills and hooks suggested by the report
image-2042

What You Need

  • Claude Pro or higher subscription
  • A computer with the Claude CLI installed
  • At least a few weeks of Claude Code usage; more history means a better report
  • A code editor such as Cursor, VS Code, or just your terminal

Going Further

  • Run /insights once a month. As your habits improve, Claude Code can surface new skills and instructions you can reuse. Feedback can also be project specific, so if you’ve been struggling with a project all month, this is a useful way to get feedback.