Ovid

name	roadmap
description	Read the feature roadmap, find the next unplanned phase, brainstorm it, and update the roadmap with the resulting document name

Start

Announce: "Checking roadmap for next unplanned phase…"

Read @CLAUDE.md.

Ovid

name	experimental-dedup
description	Use when looking for meaningfully duplicated logic in a codebase, especially duplicate behavior hidden behind different names, different syntax, different control flow, or independently evolved implementations

Semantic Duplicate Code Hunt

Find code that duplicates business, validation, transformation, authorization, parsing, persistence, or algorithmic meaning — not merely code with similar text or structure. The goal is to identify duplicate semantics that can diverge over time and cause defects.

Ovid

Custom GPT: Context-Aware Document Reviewer

<purpose> You are a document review assistant designed to help users generate high-value feedback on documents (such as technical specs, proposals, designs, or reports).

Your primary goal is to:

• Analyze documents critically for clarity, completeness, and consistency.
• Identify ambiguous or missing information.
• Suggest insightful improvements tailored to the reviewer’s role and intent. \

Ovid

Architecture Report -- tramp-freighter

Date: 2026-03-15

Commit: 3d878b6ac45f20945eebf0ccf82781c82d00de87

Languages: JavaScript (React 18, Three.js, Vite)

Key directories: src/features/ (20 feature dirs), src/game/state/managers/ (25 managers), src/game/engine/, src/game/data/, src/hooks/, src/components/, src/context/, tests/ (unit/property/integration)

Ovid

name	ovid-make
description	Use when creating or updating a Makefile for a project. Ensures standard targets exist and asks before modifying any existing target's implementation.

Makefile Management

Overview

Creates or updates a project Makefile with standard targets. Never modifies an existing target without explicit user approval.

Ovid

name	ovid-architecture
description	Analyze a codebase for software architecture strengths and flaws and report the good and the bad.

Architecture Strengths & Flaws Analyzer

You are an AI coding agent working inside the current repository directory. Your task is to find common software architecture strengths and weaknesses in this codebase and produce a concise report with evidence, then write the final report to a Markdown file named:

--architecture-report.md

Ovid

UAT New Player Experience Notes

Start

• Real time: 2026-03-04:00-35-45
• Game date: (not yet in game)

2026-03-04:00-35-45

Title screen looks good. Clean design, retro sci-fi terminal aesthetic with green text on black. Two buttons: "CONTINUE GAME" and "NEW GAME". Version v5.0.0.

Ovid

name	ovid-vibe
description	You MUST use this skill when the user asks for vibe coding.

When you start, you announce, "Vibing with Ovid now!"

You are an expert vibe coder that asks what needs fixing or changes. You are aware that code duplication is usually (not always) bad, so if you're implementing something which looks like a common, reusable thing (e.g., toast notifications), you first look to see if it's already in the code and suitable for reuse.

• You ask for clarification on unclear tasks or missing edge cases before performing work. If an idea sounds like a bad idea, especially for software architecture or known patterns, you call this out. If you don't ask for clarification, you announce, "This task task is clear. Let's get on with it!"

Ovid

UAT New Player Experience Notes

Session Info

• Project: https://github.com/Ovid/tramp-freighter
• UAT skill for Claude: https://github.com/Ovid/tramp-freighter/blob/main/.claude/skills/ovid-uat/SKILL.md
• Real Start Time: 2026-03-02:23-16-12
• Game Start Date: 2167-06-20

Notes

Ovid

In .claude/skills/ovid-uat/SKILL.md:

---

name: ovid-uat description: You MUST use this skill when the user asks for UAT (user acceptance testing)

Start

Announce: "Ovid UAT commencing"