/>/>
🛠 Interactive Tool

Build Your AI Boundaries

Most engineers don't set AI boundaries — they just react. This 5-minute tool helps you define exactly where AI stops and you begin. Get a shareable Boundary Score.

How it works

Boundary #1 — Usage Pattern

How often do you reach for AI while coding?

Think about a typical workday over the past two weeks.

Boundary #2 — Ownership

When you ship AI-assisted code, how much of it do you deeply understand?

Be honest — this is about knowing, not about what you tell others.

Boundary #3 — Protected Time

Do you have recurring time blocks where you code without AI?

This could be mornings, certain days, or specific project phases.

Boundary #4 — Discomfort Signal

When AI suggests something that feels wrong, what happens?

Think about the last time you sensed something was off in AI-generated code.

Boundary #5 — Skill Maintenance

How often do you deliberately practice a skill without AI assistance?

This could be debugging, algorithm design, writing tests, or any craft skill.

/ 100

Your Boundary Score

Calculating your boundaries...

Your 5 Boundaries

    🎯

    Focus Area

    Loading...

    🌱

    Start Here

    Pick one boundary to set this week.

    Your First Boundary Action

      How It Works

      It's a 5-question interactive tool that helps you identify where you've let AI take over too much of your coding process. You answer honestly, get a Boundary Score (0-100), and leave with one specific action to start reclaiming your craft.
      Software engineers who use AI coding tools daily and want to make sure they're still the driver — not a passenger in their own work. Especially useful if you've noticed you're less confident debugging without AI, or that you sometimes ship code you don't fully understand.
      No. All answers stay in your browser (localStorage). Nothing is sent to any server. You can close the tab and come back — your answers are only saved on your machine.
      0-30: You may have lost track of where AI ends and you begin. High risk of skill atrophy and ownership loss. / 31-60: Moderate boundaries — you're aware but not consistent. Room to strengthen. / 61-85: Healthy boundaries with clear ownership. You're using AI as a tool, not a replacement. / 86-100: Strong AI hygiene. You're actively maintaining your craft while leveraging AI.
      Yes. You can retake it as often as you like. Your Boundary Score should improve as you implement changes. Think of it as a quarterly check-in for your AI hygiene.
      🧠

      What is AI Fatigue

      The full picture of what's happening to engineers

      📉

      Skill Atrophy

      The quiet erosion happening to your craft

      🧭

      Mental Models

      12 frameworks for using AI without losing yourself

      🌿

      Recovery Guide

      Concrete steps to reclaim your engineering identity

      🛠 Interactive Tool

      Build Your AI Boundaries

      Most engineers don't set AI boundaries — they just react. This 5-minute tool helps you define exactly where AI stops and you begin. Get a shareable Boundary Score.

      How it works

      Boundary #1 — Usage Pattern

      How often do you reach for AI while coding?

      Think about a typical workday over the past two weeks.

      Boundary #2 — Ownership

      When you ship AI-assisted code, how much of it do you deeply understand?

      Be honest — this is about knowing, not about what you tell others.

      Boundary #3 — Protected Time

      Do you have recurring time blocks where you code without AI?

      This could be mornings, certain days, or specific project phases.

      Boundary #4 — Discomfort Signal

      When AI suggests something that feels wrong, what happens?

      Think about the last time you sensed something was off in AI-generated code.

      Boundary #5 — Skill Maintenance

      How often do you deliberately practice a skill without AI assistance?

      This could be debugging, algorithm design, writing tests, or any craft skill.

      / 100

      Your Boundary Score

      Calculating your boundaries...

      Your 5 Boundaries

        🎯

        Focus Area

        Loading...

        🌱

        Start Here

        Pick one boundary to set this week.

        Your First Boundary Action

          How It Works

          It's a 5-question interactive tool that helps you identify where you've let AI take over too much of your coding process. You answer honestly, get a Boundary Score (0-100), and leave with one specific action to start reclaiming your craft.
          Software engineers who use AI coding tools daily and want to make sure they're still the driver — not a passenger in their own work. Especially useful if you've noticed you're less confident debugging without AI, or that you sometimes ship code you don't fully understand.
          No. All answers stay in your browser (localStorage). Nothing is sent to any server. You can close the tab and come back — your answers are only saved on your machine.
          0-30: You may have lost track of where AI ends and you begin. High risk of skill atrophy and ownership loss. / 31-60: Moderate boundaries — you're aware but not consistent. Room to strengthen. / 61-85: Healthy boundaries with clear ownership. You're using AI as a tool, not a replacement. / 86-100: Strong AI hygiene. You're actively maintaining your craft while leveraging AI.
          Yes. You can retake it as often as you like. Your Boundary Score should improve as you implement changes. Think of it as a quarterly check-in for your AI hygiene.
          🧠

          What is AI Fatigue

          The full picture of what's happening to engineers

          📉

          Skill Atrophy

          The quiet erosion happening to your craft

          🧭

          Mental Models

          12 frameworks for using AI without losing yourself

          🌿

          Recovery Guide

          Concrete steps to reclaim your engineering identity