latitude-dev
- 28 skills
- 0 followers
- 1 week ago last updated
- ▌ 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.