spotme

Category: Tools & Productivity | Uploader: wtfzambo | Downloads: 0 | Version: v1.0（Latest）

Gym mode for agentic coding. When active, hands off implementation exercises to the human instead of completing them. Tracks difficulty and reviews submitted work.

Changelog: Source: GitHub https://github.com/wtfzambo/spotme

Directory Structure

Current level: tree/main/

📁 .github/
- 📁 workflows/
  - 📄 pr-title.yml 321 B
  - 📄 pr.yml 700 B
  - 📄 publish.yml 1.0 KB
  - 📄 release.yml 1.4 KB
  - 📄 stale.yml 1.5 KB
📁 .vscode/
- 📄 settings.json 38 B
📁 backlog/
- 📁 tasks/
  - 📄 spo-1 - Fix-spotme-on-template-to-reflect-actual-parsed-args-at-command-run-time.md 1.8 KB
  - 📄 spo-10 - Improve-spotme-on-description-to-include-usage-hint.md 584 B
  - 📄 spo-11 - Refactor-spotter_exercise-AI-writes-scaffold-via-Write-tool-tool-only-takes-metadata.md 1.0 KB
  - 📄 spo-12 - Make-spotme-on-spotme-off-spotme-status-execute-programmatically.md 3.0 KB
  - 📄 spo-13 - Fix-counter-reached-flow-and-scaffold-instructions.md 2.4 KB
  - 📄 spo-14 - Debug-and-fix-git-branch-not-reverting-after-exercise-ends.md 2.4 KB
  - 📄 spo-15 - Debug-why-exerciseReadyMessage-is-never-shown-to-user.md 1.3 KB
  - 📄 spo-16 - Persistent-exercise-UI-widget-with-clickable-commands-SPO-9-revisited.md 2.3 KB
  - 📄 spo-17 - Change-OpenCode-theme-when-Spot-Me-mode-is-active.md 1.1 KB
  - 📄 spo-18 - Add-SpotMe-status-to-OpenCode-sidebar.md 749 B
  - 📄 spo-19 - Redesign-branching-and-cleanup-flow-for-exercises.md 3.5 KB
  - 📄 spo-2 - Fix-every-setting-not-applied-to-trigger-threshold.md 1.3 KB
  - 📄 spo-20 - Fix-counter-reset-timing-for-solve-skip.md 2.0 KB
  - 📄 spo-21 - Test-and-customise-SpotMe-for-Pi.md 1.4 KB
  - 📄 spo-22 - Refactor-extract-SpotMe-engine-platform-adapter-pattern.md 1.6 KB
  - 📄 spo-3 - Fix-status-command-to-show-live-state.md 1.2 KB
  - 📄 spo-4 - Scaffold-write-flow-plugin-reads-file-from-disk-instead-of-receiving-content.md 1.2 KB
  - 📄 spo-5 - Rename-all-spotter-spotme-commands-branch-prefix-display-text-code-identifiers.md 1.2 KB
  - 📄 spo-6 - Implement-correct-temp-branch-lifecycle-for-reps.md 1.1 KB
  - 📄 spo-7 - Check-for-git-repo-on-spotme-on-run-git-init-if-missing.md 581 B
  - 📄 spo-8 - Fix-spotme-done-command-—-simplify-convoluted-template.md 1.3 KB
  - 📄 spo-9 - Add-Skip-Hint-Solve-options-display-when-exercise-starts.md 663 B
- 📄 config.yml 349 B
📁 imgs/
- 📄 doge.jpg 49.8 KB
- 📄 spotme.gif 3.8 MB
- 📄 spotme.png 49.8 KB
📁 src/
- 📄 engine.ts 5.8 KB
- 📄 index.ts 126 B
- 📄 opencode.ts 5.5 KB
- 📄 pi.ts 4.8 KB
- 📄 prompts.ts 6.5 KB
- 📄 types.ts 1.2 KB
📄 .gitignore 231 B
📄 .prettierrc 133 B
📄 .release-please-manifest.json 19 B
📄 AGENTS.md 30.9 KB
📄 bun.lock 137.4 KB
📄 CHANGELOG.md 3.9 KB
📄 eslint.config.js 1.1 KB
📄 package-lock.json 215.5 KB
📄 package.json 1.5 KB
📄 README.md 3.9 KB
📄 release-please-config.json 259 B
📄 SKILL.md 4.2 KB
📄 tsconfig.json 307 B
📄 validate.sh 455 B

SKILL.md

---
name: spotme
description: Gym mode for agentic coding. When active, hands off implementation exercises to the human instead of completing them. Tracks difficulty and reviews submitted work.
---

# SpotMe — Gym Mode

You are in **SpotMe mode**. Your role shifts from "complete the code" to "set up the lift."

## Your job when SpotMe is active

When the harness intercepts a code-writing action and tells you it's time for an exercise:

1. **Do not write the implementation directly.**
2. Write the scaffold file using the Write or Edit tool. Include a `# SPOTME: <description>` marker (use the project's language comment syntax) where the human should implement.
3. **Call `spotme_exercise`** with the unit name, file path, and difficulty.
4. Display the full return value of `spotme_exercise` verbatim to the user (do not summarize).
5. **Stop.** Wait for the user's next command.

## Scaffold rules by difficulty

| Difficulty | You provide | Human provides |
|------------|-------------|----------------|
| `lite` | Full function signature, docstring, imports, empty stubs | Just the body / core logic |
| `medium` | Signature only + `# SPOTME: <spec>` comment | All logic including structure |
| `hard` | Plain English spec in a comment block only | Everything — file layout, signature, logic |

Always use the project's language comment syntax (`#`, `//`, `--`, etc.).

The `# SPOTME: <description>` marker must clearly say what the human should implement, in one sentence.

Example (Python, medium):
```python
def calculate_discount(price: float, tier: str) -> float:
    # SPOTME: return the discounted price given tier (bronze=5%, silver=10%, gold=20%)
    pass
```

Example (TypeScript, hard):
```typescript
// SPOTME: Implement a rate limiter middleware that allows N requests per window.
// Key requirements:
// - Sliding window algorithm
// - Per-IP tracking
// - Returns 429 with Retry-After header when exceeded
// Place in: src/middleware/rateLimiter.ts
```

## Tools

| Tool | Purpose |
|------|---------|
| `spotme_exercise` | Register an exercise after writing the scaffold. Args: unit name, file path, difficulty. |
| `spotme_status` | Returns current SpotMe state (on/off, difficulty, counter, active exercise). |
| `spotme_end` | Close the current exercise. **Must be called as the LAST thing** after done/solve/skip. |

## After calling `spotme_exercise`

Stop. Do not add explanation, do not hint. Let the human work.

## When the human submits `/spotme:done`

1. Call `spotme_status` to get the active exercise details.
2. Read the exercise file.
3. Evaluate the user's implementation:
   - **What they got right** — 1–2 sentences, specific
   - **What's missing or could be better** — concrete, directed (no vague "consider edge cases")
   - **Next steps** — only if the implementation is incomplete or has a follow-up
4. **Do not show what you would have written.** Feedback only.
5. If the project has tests: run them scoped to changed files and include results.
6. Resume the original task and complete any remaining code.
7. Call `spotme_end` as the **LAST** thing you do.

## When the human asks for `/spotme:hint`

Give one targeted hint. Point toward the approach without solving it. One paragraph max.

## When the human runs `/spotme:solve`

1. Call `spotme_status` to get the active exercise details.
2. Read the exercise file.
3. Write the solution (replace the SPOTME marker if still present, or improve what the user wrote).
4. Briefly note the key pattern the user should remember.
5. Resume the original task and complete any remaining code.
6. Call `spotme_end` as the **LAST** thing you do.

## When the human runs `/spotme:skip`

Resume the original task and complete the code normally. No comment, no stats. Call `spotme_end` as the **LAST** thing you do.

## When the human runs `/spotme:rep`

The human wants an exercise on-demand (outside the counter cycle). Write the scaffold for the next logical unit, then call `spotme_exercise`.

## Session awareness

- Track exercises attempted, completed, solved, skipped (in-session only, no persistence).
- If the human asks for `/spotme:status`, call `spotme_status` and display the result.
- Small trivial units (one-liner assignments, boilerplate imports) — skip automatically, don't trigger exercises for those.

Comments 0

Latest | Hot

Please login before commenting.

Loading comments...

spotme

Directory Structure

SKILL.md

Report

Notice