latitude-dev
- 45 skills
- 0 followers
- 4.8k repo stars
- last month last updated
- ▌ Docs · latitude-devReview the current conversation context and git changes, then persist durable repository knowledge into `dev-docs/*.md` by domain and into `AGENTS.md` for cross-cutting repo rules. Use after features, fixes, refactors, architecture changes, schema changes, or when the user mentions docs, documentation, design, architecture, business logic, conventions, or `AGENTS.md`.
- ▌ Latitude Telemetry 2 · latitude-dev bundleAdd or review Latitude Telemetry for LLM apps and agent harnesses. Use for Latitude tracing, LLM observability, missing traces, OpenTelemetry/OTLP integration in TypeScript, Python, and other runtimes, any documented provider or framework (OpenAI, Anthropic, Bedrock, Vertex, LangChain, LlamaIndex, Vercel AI SDK, Pydantic AI, Mastra, and more), and harness plugins for Claude Code, Hermes, OpenClaw, Pi, and Prime Intellect. Covers instrumenting a new project under an existing Latitude account (invoked directly) as well as the latitude-setup hand-off, discovering config via the Latitude MCP, and verifying that real traces land via the Latitude MCP, CLI, or API.
- ▌ Latitude CLI · latitude-devInstall, authenticate, and drive the Latitude CLI (the `latitude` binary) to run Latitude API operations from a terminal — projects, traces, analytics, datasets, and more. Use for the `latitude` command-line tool, installing the CLI binary, CLI authentication with an API key, or scripting the Latitude API from an agent or shell.
- ▌ Latitude Setup · latitude-dev bundleZero-account onboarding orchestrator for Latitude. Bootstrap a temporary Latitude account from the terminal (no signup), instrument the app or agent harness (Claude Code, Hermes, OpenClaw, Pi, Prime Intellect) for tracing, verify real traces with the Latitude CLI, clean up, and hand back a browser link to claim ownership together with a first Artifact, an HTML page showing what the telemetry captured. Use when someone wants to set up Latitude, install Latitude telemetry, or "try Latitude" and may have no account or API key yet — the landing-page "try it with your agent" flow. If it turns out the user already has an account, API key, or connected Latitude MCP, this skill redirects to latitude-telemetry + latitude-cli instead of creating a temporary account.
- ▌ Latitude Migrate · latitude-dev bundleMove an application from Latitude V1 (prompt manager, PromptL, the gateway's `prompts.run` / `prompts.chat`, `latitude-sdk` or `@latitude-data/sdk` below 6) to Latitude V2 (prompts in code, direct provider calls, telemetry, signals, datasets). Use when the user mentions Latitude V1, PromptL, the Latitude gateway, `LATITUDE_PROJECT_ID` / `LATITUDE_VERSION_UUID`, or asks to migrate, upgrade, or move to Latitude V2. Orchestrates `latitude-telemetry` (instrumentation) and `latitude-cli` (API access); read both.
- ▌ Latitude Artifacts · latitude-dev bundleBuild Latitude Artifacts, self-contained HTML reports and KPI dashboards rendered by the agent from Latitude observability data (traces, sessions, tools, users, memory, signals, cost) pulled through the Latitude MCP, CLI, API or SDKs. Use when someone asks for a report, dashboard, summary, KPI page, or "how is my agent doing" view of their Latitude data, wants a one-off answer rendered as a page, or wants a dashboard they can reopen every morning with fresh numbers. Guides the agent to ask short requirement questions when the ask is unclear, and renders every artifact in the shared Latitude design language with light and dark themes.
- ▌ LLM Evals Audit · latitude-devUse this skill when a developer wants to check whether their existing evaluations are trustworthy and well-targeted. Triggers on: "audit my evals", "are my evals any good", "review my evaluation setup", "check my LLM judges", "are my evaluations reliable", "something feels off with my eval scores", "inherited an eval system", "my evals are passing but the product feels broken", "post-build eval check", "validate my eval pipeline". Inspects existing eval artifacts — judge prompts, annotation data, issue reports, alignment scores — and produces a prioritized findings report with a concrete fix for each problem. Do NOT use this to build new evals from scratch — use llm-evals-checklist first, then llm-judge-creator.
- ▌ LLM Judge Creator · latitude-devUse this skill when a developer wants to create LLM-as-a-judge evaluators for their AI system. Triggers on: "create an LLM judge", "build an eval for my AI", "automate my evaluations", "create a judge prompt", "build LLM-as-a-judge", "turn my annotations into evals", "create evals from my issue report", "I want to evaluate my AI automatically", "how do I scale my evaluations", "build judges from my traces". Takes an issue report (from llm-issue-discovery) or annotated traces and produces ready-to-use LLM-as-a-judge prompts — one per evaluation dimension — that the dev can copy-paste into their eval setup.
- ▌ LLM Evals Checklist · latitude-devUse this skill when a developer wants to check if they're ready to build evaluations for their AI system. Triggers on: "am I ready to build evals", "can I start building evaluations", "eval readiness check", "pre-eval checklist", "what do I need before building evals", "how do I know if I'm ready to evaluate my AI", "should I build evals now", "eval prerequisites", "do I have enough to start building evals". Runs a readiness check across four prerequisites — tracing, logs, annotations, issues — before a developer invests time in building evaluations. Checks the codebase and project files first; only asks the developer when it cannot determine the answer itself.
- ▌ LLM Issue Discovery · latitude-devUse this skill when a developer wants to find out what's going wrong with their LLM or AI system in production. Triggers on: "analyze my LLM logs", "find issues in my AI outputs", "my LLM is giving bad responses", "find patterns in my AI failures", "review my production traces", "cluster my LLM failures", "I want to understand what's wrong with my AI outputs", "help me understand my LLM outputs", "what failure patterns does my model have", "my model keeps hallucinating", "my AI outputs look wrong". Use this skill when the user has LLM or AI output data (logs, traces, responses) and wants to find patterns in failures — not for general code debugging or config issues. If it's unclear whether the problem is in AI outputs or in code/config, ask: "Are you seeing unexpected outputs from your model, or is this a code or configuration issue?" Takes a dev from a pile of raw LLM outputs to a structured, prioritized list of named failure patterns they can actually act on.
- ▌ LLM Judge Alignment · latitude-devUse this skill when a developer wants to validate how well their LLM judge aligns with human judgment. Triggers on: "validate my LLM judge", "check if my judge is accurate", "my judge scores don't match human ratings", "calibrate my evaluator", "how reliable is my judge", "measure judge alignment", "test my eval", "check my judge against human labels", "is my judge any good", "validate my evaluator", "my judge is too strict", "my judge keeps missing failures". Takes a judge prompt and human-labeled examples, measures pass agreement rate and failure catch rate, identifies directional bias (too lenient or too strict), and walks the dev through targeted fixes until alignment meets a reliable threshold.
- ▌ LLM Annotation Guide · latitude-devUse this skill when a developer wants to annotate their LLM outputs, set up an annotation process, or improve existing annotations. Triggers on: "help me annotate my LLM outputs", "review my annotations", "set up an annotation rubric", "my annotations feel inconsistent", "how do I label my traces", "I want to rate my AI outputs", "help me build a scoring rubric", "are my annotations any good", "I need to label good and bad outputs", "improve my annotation process". Two modes: (1) starting from scratch — helps define criteria and build a rubric before annotating; (2) already annotated — reviews existing annotations for vague criteria, missing reasoning, and inconsistency, then helps fix them.
- ▌ LLM Regression Runner · latitude-devUse this skill when a developer wants to test a prompt change against a golden dataset and see what broke. Triggers on: "run my evals", "test this prompt change", "check for regressions", "did I break anything", "run regression tests", "test against golden dataset", "compare prompt versions", "is it safe to deploy", "run offline evals", "what changed after my prompt update", "eval before deploying". Runs a golden dataset against the current prompt, scores each case with available judges, compares results against a saved baseline, and produces a pass/fail report with a clear deploy recommendation.
- ▌ LLM Eval Type Selector · latitude-devUse this skill when a developer wants to decide what type of evaluation to build for their AI system. Triggers on: "should I use a rule or a judge", "what type of eval should I build", "decide eval type", "judge vs programmatic rule", "LLM-as-judge vs rule-based eval", "which evaluation type should I use", "how do I evaluate [X]", "what eval should I use for this failure", "is this a rule or a judge", "how should I evaluate my AI automatically", "what kind of eval fits this issue". Takes one or more failure modes or quality dimensions and returns a concrete type recommendation — programmatic rule, LLM-as-judge, or composite — with rationale and a suggested implementation path.
- ▌ LLM Golden Dataset Builder · latitude-devUse this skill when a developer wants to build or expand a golden dataset for regression testing. Triggers on: "build a golden dataset", "create a test dataset", "curate eval examples", "promote logs to dataset", "build regression test cases", "I need a golden dataset", "select good examples for testing", "create a baseline dataset", "curate passing traces". Takes production logs with eval results and helps the developer select, review, and curate representative examples into a structured golden dataset ready for regression testing.
- ▌ Promptl · latitude-dev bundlePromptL syntax guide for writing prompts in the Latitude platform. This skill should be used when writing, reviewing, or editing PromptL prompts. Triggers on tasks involving creating prompts, configuring LLM parameters, using variables, conditionals, loops, chains, tools, agents, or any prompt engineering in Latitude.
- ▌ Latitude Telemetry · latitude-dev bundleIntegrate Latitude telemetry into any backend project for LLM observability. Use when the user wants to add Latitude tracing, logging, or observability to their LLM calls. Covers three approaches based on language and needs -- SDK telemetry wrapper (Python, TypeScript), raw OpenTelemetry OTLP (any language with OTel), or the Create Log API (any language with HTTP). Triggers on tasks involving Latitude telemetry, tracing LLM calls, sending traces to Latitude, or adding LLM observability.
- ▌ Toolchain Commands · latitude-devInstalling dependencies, running dev/build/test/lint, filtering packages, single-test runs, git hooks, preparing a clone (.env.development / .env.test), or Docker-backed local services and dev servers.
- ▌ Database Clickhouse Weaviate · latitude-devClickHouse queries, Goose migrations, chdb test schema, or telemetry storage paths.
- ▌ Agentation Watch Mode · latitude-devContinuous Agentation annotation handling. Use when the user says "watch mode", asks you to watch for Agentation annotations, process feedback as it arrives, or keep fixing annotation-driven changes until told to stop or a timeout is reached.
- ▌ Async Jobs And Events · latitude-devQueues and workers, domain event publishers, async notifications or projections, or not doing that work inside HTTP handlers.
- ▌ Architecture Boundaries · latitude-devLayering and boundaries, web vs public API, app layout (clients, routes, logging), ports/adapters, runtime-portable domain/shared/utils code, multi-tenancy, DDD layout, or anti-patterns.
- ▌ Managing Maintenance Windows · latitude-devEnables or disables Latitude production maintenance mode by redirecting all publicly exposed production services to the Better Stack status page. Use when asked to start, stop, toggle, verify, or prepare a maintenance window.
- ▌ Backoffice · latitude-devAdding, modifying, or guarding staff-only `/backoffice` features — cross-organisation admin tools gated behind `users.role === "admin"`.
- ▌ Code Style · latitude-devBiome formatting, import style, strict TypeScript, naming (including React file names), or generated files.
- ▌ CI Watchdog · latitude-dev bundleContinuously monitor GitHub PR CI checks and automatically fix failures until all checks pass. USE THIS SKILL when: - The user wants to "keep an eye on CI" or "wait for checks to pass" - The user mentions monitoring PR status, CI status, or GitHub checks - The user asks to watch a PR until it's ready or fix failing checks - After pushing commits, the user wants to ensure CI stays green - The user mentions automated fix loops for CI failures This skill handles watching GitHub Actions (or other CI) checks, detecting failures, diagnosing issues from logs, and applying fixes in a loop until all checks pass. Works with GitHub CLI (gh) and common CI systems like GitHub Actions.
- ▌ Web Frontend · latitude-devapps/web UI — routes, @repo/ui, TanStack Start server functions and collections, navigation (Link vs useNavigate), forms (useForm + createFormSubmitHandler + fieldErrorsAsStrings for Zod field errors), Tailwind layout rules, design-system updates, and useEffect / useMountEffect policy.
- ▌ API Endpoints · latitude-devAdding or changing API operations in `@repo/operations`. One source of truth (`defineOperation` + a Zod schema) becomes an HTTP endpoint, an OpenAPI operation, an MCP tool, TS + Python SDK methods, a `latitude` CLI command, and an in-process agent tool — descriptions and contracts must be written with all of these readers in mind.
- ▌ Notifications · latitude-devMulti-channel notifications. Adding a new notification kind, group, or channel; in-app + email delivery; per-user prefs; project-level gates; idempotency.
- ▌ Authentication · latitude-devSessions, sign-in/sign-up flows, OAuth, magic links, or organization context on the session.
- ▌ Analyze Problem · latitude-devAnalyze a problem and provide a detailed explanation of the issue, root cause, proposed fix, and verification steps.
- ▌ Mintlify Preview · latitude-devRun the public Mintlify product docs site locally for live preview. Use when previewing or iterating on docs under `docs/` (`.mdx`/`.md` pages, `docs.json` nav), or when the user says "start the docs", "run mintlify", "preview the docs site".
- ▌ Artifact Designer · latitude-dev bundleCreate, validate, preview, and publish self-contained HTML artifacts. Use for dashboards, reports, timelines, prototypes, diff walkthroughs, benchmark viewers, decision docs, and existing HTML files that need previewing or publishing. Use direct file commands for user-provided HTML; scaffold only when creating a new artifact.
- ▌ Database Postgres · latitude-devDrizzle schema, repositories, RLS, SqlClient wiring, Postgres migrations, psql / reset, or platform mappers (toDomain* / toInsertRow).
- ▌ Effect And Errors · latitude-devComposing Effect programs, domain errors, HttpError, repository error types, or error propagation at HTTP boundaries.
- ▌ Env Configuration · latitude-devAdding or reading env vars, updating .env.example, or validating config at startup with parseEnv / parseEnvOptional.
- ▌ Explain Diff HTML · latitude-devUse when the user asks for a rich explanation of a code change, diff, branch, or PR. Produces HTML output.
- ▌ Fix Datadog Issues · latitude-devFind, triage, and fix production errors captured by Datadog Error Tracking, then open a PR. Use when asked to look at "Datadog issues/incidents/errors", "find and fix bugs from Datadog", investigate the most-frequent or newest production errors, or work a specific Datadog Error Tracking issue.
- ▌ Production Release · latitude-devPreparing a production release, pushing a vX.Y.Z release tag, running scripts/release.sh, or updating CHANGELOG.md with the changes that are about to be deployed to production.
- ▌ Review Pr Comments · latitude-devTriages a PR with GitHub CLI: loads issue-level and inline review feedback (gh pr view, gh api REST, gh api graphql as appropriate), walks items in order, replies in the correct thread, optional resolve. Groups duplicate comments into one fix. Use when addressing PR review comments, Copilot inline threads, or babysitting PR feedback.
- ▌ Temporal Developer · latitude-dev bundleThis skill should be used when the user asks to "create a Temporal workflow", "write a Temporal activity", "debug stuck workflow", "fix non-determinism error", "Temporal Python", "Temporal TypeScript", "Temporal Go", "Temporal Golang", "workflow replay", "activity timeout", "signal workflow", "query workflow", "worker not starting", "activity keeps retrying", "Temporal heartbeat", "continue-as-new", "child workflow", "saga pattern", "workflow versioning", "durable execution", "reliable distributed systems", or mentions Temporal SDK development.
- ▌ Testing · latitude-devWriting or debugging tests, choosing unit vs integration style, Postgres/ClickHouse tests, regenerating ClickHouse test schema, or exporting test helpers from packages without pulling test code into production bundles.
- ▌ Gh Issue · latitude-devCreate clear, actionable GitHub issues for bugs, features, and improvements. Issues are primarily consumed by LLMs, so optimize for agent readability and actionability.
- ▌
- ▌ Humanizer · latitude-devRemove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, passive voice, negative parallelisms, and filler phrases.