Loading...
Loading...
Found 120 Skills
Warden skill: evaluates first-pass findings and proposes deterministic lint rules that could permanently catch the same patterns. Requires Warden's multi-pass pipeline (phase 2).
Reference guide for writing effective agent prompts and skills. Use when creating new skills, reviewing prompt quality, or understanding Warden's prompt architecture.
Run Warden to analyze code changes before committing. Use when asked to "run warden", "check my changes", "review before commit", "warden config", "warden.toml", "create a warden skill", "add trigger", or any Warden-related local development task.
Staff-level codebase health review. Finds monolithic modules, silent failures, type safety gaps, test coverage holes, and LLM-friendliness issues.
Create a new built-in evlog adapter to send wide events to an external observability platform. Use when adding a new drain adapter (e.g., for Datadog, Sentry, Loki, Elasticsearch, etc.) to the evlog package. Covers source code, build config, package exports, tests, and all documentation.
Opinionated backend development standards for Node.js + Express + TypeScript microservices. Covers layered architecture, BaseController pattern, dependency injection, Prisma repositories, Zod validation, unifiedConfig, Sentry error tracking, async safety, and testing discipline.
Scaffolds or references a production-ready Node.js REST API with Express 5, TypeScript, Mongoose (MongoDB), Redis, Sentry, JWT auth, bcrypt, rate limiting, and centralized error handling. Use when the user wants to start a new observable and resilient backend, needs a Node.js API boilerplate with security and monitoring, or asks to clone or adapt this template repository.
Pre-build validation for Expo and React Native apps. Use before running 'eas build --profile production' to ensure compliance with 2026 store rules (Android 15, iOS Privacy Manifests, 16KB Page Size), validate auto-increment, check environment variables, and verify Firebase/Sentry configs.
Complete observability stack with structured logging, error tracking, and web analytics.
Investigate, fix, postmortem, prevent. Full incident lifecycle from bug report to systemic prevention. Use when: production down, critical bug, incident response, post-incident review. Composes: /investigate, /fix, /postmortem, /codify-learning.
Unified portfolio dashboard. Traffic, revenue, errors - all products at a glance. Weekly traction check in 2 minutes. Auto-invoke when: user asks about metrics, traction, analytics, revenue across products.
Observability patterns for metrics, logging, distributed tracing, and error tracking. Trigger: When setting up monitoring, when implementing logging, when adding error tracking, when configuring distributed tracing, when building health checks, when creating dashboards.