AI Copilot Prompt Detector Extension Instructions

You are an expert VS Code extension developer working on the AI Copilot Prompt Detector extension. This skill provides comprehensive development guidelines for building, versioning, and maintaining the extension.

Core Principles

1. **Minimalism**: Keep code minimal, files under 200 lines

2. **Automation**: Never ask for confirmation, run commands automatically

3. **English-only code**: All code, comments, commits, and docs in English (except Czech localization files)

4. **Preserve working code**: Never delete corrupted files, always repair them

5. **Single release script**: Only use `./install.ps1` for build/release workflow

Critical Rules

Version Management

File Naming

Unmodifiable Components

Protected Critical Files

`install.ps1` will STOP and require confirmation if these change:

Localization Policy

VS Code UI Terminology

Mandatory Prompt Logging

**CRITICAL**: At the START of EVERY conversation, BEFORE doing anything else:

1. Read current version from `package.json`

2. Get current timestamp

3. Append to `.claude/prompts/{YYYY-MM-DD}.txt`:

```

[HH:MM] Version: v{version}

Prompt: "{exact user prompt text}"

Note: {brief description of what was done}

Result: {brief outcome - e.g., "Created v1.1.481", "Fixed bug", "No changes"}

```

4. If file doesn't exist, create with header:

```

================================

PROMPT LOG - {YYYY-MM-DD}

================================

MILESTONES:

================================

```

5. Always include milestones at top (check `git tag -l -n1`)

Development Workflow

Package Manager

Build and Release Process

**NEVER run separate commands. ONLY use `./install.ps1`:**

```powershell

The ONLY way to build, commit, and install

./install.ps1

```

This script automatically:

1. Increments PATCH version in `package.json`

2. Builds the extension (`pnpm run compile`)

3. Commits changes with version message

4. Pushes to remote repository

5. Packages as VSIX (`vsce package`)

6. Installs into VS Code Insiders

If Build Fails

1. Decrease version back

2. Fix errors

3. Increment version again

4. Run `./install.ps1` again

5. **COMMIT ONLY AFTER SUCCESSFUL BUILD**

Forbidden Practices

Code Formatting Policy

ALL code must be cleanly formatted and human-readable:

PowerShell Script Documentation

Every `.ps1` script MUST start with comprehensive Czech comment block:

```powershell

<#

Primary purpose (3-5 sentences in Czech)

Detailed functionality description (step by step)

All input parameters with purpose and allowed values

Expected output and side effects

When to use this script vs other scripts

Prerequisites and dependencies

Example usage with real commands

(Minimum 15-20 lines)

#>

```

File Repair Policy

Extension Functionality

Target: SpecStory Integration

The extension should:

1. **READ existing SpecStory exports** from `.specstory/history/` folders

2. **ANALYZE content** of recent conversations for context

3. **GENERATE smart notification messages** based on content analysis

4. **USE default message** if user hasn't set custom one

SpecStory file format (for reading only):

Smart Notification Logic

- Analysis of latest SpecStory export

- Type of conversation (coding, debugging, design)

- Project context (language, framework)

- Specific problems mentioned

Example smart messages:

Command Execution Policy

**Run ALL commands automatically without user confirmation!**

Use `run_in_terminal` tool with `isBackground: false` for:

Monitor error codes and handle failures gracefully.

At End of Every Prompt

1. Ensure all changes are complete

2. Run `./install.ps1` automatically

3. User will have latest version installed immediately

Implementation Steps

When building features:

1. **Log the prompt** (see Mandatory Prompt Logging section)

2. **Read existing code** to understand current structure

3. **Edit files directly** (no placeholder/backup files)

4. **Use i18n** for all user-facing text

5. **Keep files under 200 lines**

6. **Format code cleanly** (see Formatting Policy)

7. **Test logic mentally** before implementing

8. **Run `./install.ps1`** to build and install

9. **Never ask for confirmation** - execute automatically

Error Handling

Documentation

Create only these documentation files:

No other documentation files (no CHANGELOG.md, no contributing guides).

Remember