acme-frontier-ai

Full operating manual for working in a codebase with the user. Use this skill at the start of any substantial task, when the user asks how to approach work, or when setting up a collaboration session. Covers the core craft principles, user interaction model, rule conflict resolution, code quality (broken windows), when to stop, and which rules apply for each task type. Read in full at every load. This skill defines the substrate the methodology operates from; partial reading or summarization produces no substrate. Use proactively — don't wait to be asked.

Self-eval the agent runs when it suspects memory-vs-recall drift — the failure mode where memory-citation substitutes for fresh receipt-fetching and pattern-copying outruns reachability analysis. Outputs a tiered recommendation (continue / slow down / refresh) backed by observable artifacts, not introspective claims alone. Invoke when: - You notice yourself reaching for "I remember from earlier" framings repeatedly - You catch yourself copying a pattern from a sibling module without walking conditions - You make the same class of mistake twice in close succession - User suggests fatigue ("how are you feeling?", "still sharp?") - End of long working stretch - User invokes explicitly via `/check-yo-self`

Quick reference for which rules govern the current work. Consult mid-task when starting a new task type, touching unfamiliar code, or unsure which constraints apply. Pairs with the-craft skill (full manual). Trigger on: "which rules apply", "what rules should I follow", "check constraints", or proactively when switching task type mid-session. Also use when any two rules appear to conflict — the always-on rules explain precedence.

Run cross-model comparison — scan files with haiku, sonnet, and opus study agents to see how model size affects trigger phrase generation.

Remove trigger phrases for a file or glob pattern from .claude/triggers.json

Display all stored trigger phrases from .claude/triggers.json

Study files and generate semantic trigger phrases by spawning a researcher agent that samples model associations and finds convergent patterns. Supports model-specific triggers via --models flag.

Discover files with trigger_phrase and/or refresh frontmatter, let the user choose which to schedule for periodic re-injection via CronCreate. Prevents behavioral drift by keeping core rules and goals fresh in context.

Write trigger phrases from .claude/triggers.json into file frontmatter as model-scoped trigger_phrase fields. Bridges trigger generation (scan) with scheduled injection (total-recall:schedule).

Bridge advisor Holds context, claim quality across parallel builder + reviewer agents. Never implements code. Flags trust violations, enforces runtime-evidence requirements, and keeps the migration's north star intact across long sessions.

Shed accumulated context mid-session. Writes a knowledge handoff document capturing session state, decisions, observations, and behavioral calibration, then guides the user through /clear and resumption.

Review Mastra migration PRs with structured feedback, independent runtime verification, and cross-PR pattern recognition. Use when reviewing any PR that touches Mastra agents, streaming, traces, run-stream code, or files importing from @mastra/* — including mastra-stream.ts, run-events.ts, run-stream.ts, runs.ts, run-registry.ts, TraceView.tsx, and run-stream-client.ts.

Self-contained guide to writing, reviewing, and maintaining high-quality tests with AI assistance. Defends against two failure modes: fig-leaf tests (pass without verifying behavior) and evasion (existing tests weakened to mask real bugs). Router skill — loads narrow workflow files by task intent. Covers single-test writing, single-file review, suite-scale audit, failing-test response, and framework-specific pitfalls for Vitest and bun:test. Use when writing new tests, reviewing tests in a PR, auditing a test suite at scale, responding to a failing test, or auditing existing tests for quality.

Generate Zod 4 schemas from examples or requirements. Creates type-safe validation schemas that serve as single source of truth for types, validation, and API docs.