Profile My skills Saved My plugins Edit profile Submit a skill

← all publishers

criseulises

@criseulises source repo

3 published skills

  1. ▌
    Scaffolding REST API · criseulises bundle
    Scaffolds a production-ready REST API in TypeScript using Fastify, Zod for input validation, pino for structured logging, and emits an OpenAPI 3.1 spec. Use when the user asks to "scaffold a REST API", "start a new backend", "bootstrap a Node API", or mentions Fastify, Zod, OpenAPI, rate limiting, or structured error responses. Covers project layout, validation pipeline, error envelope, rate limiting with @fastify/rate-limit, health and readiness endpoints, graceful shutdown, and OpenAPI generation. Do NOT use for GraphQL schemas, gRPC services, Python/Go/Ruby backends, full-stack frameworks (Next.js, Remix), or for adding routes to an existing non-Fastify codebase.
    0 installs
  2. ▌
    Auditing Env Files · criseulises bundle
    Audits a project directory for leaked secrets, mis-handled .env files, committed credentials, and hardcoded API keys before a release or open-source publish. Use when the user asks to "audit env files", "check for leaked secrets", "prep this repo for open source", "review before rotation", or mentions .env exposure, gitignore safety, or pre-publish security checks. Covers .gitignore verification, .env vs .env.example diffing, source-code secret scanning with a fixed pattern set, git history search, and a human-readable rotation plan with masked values. Do NOT use for live cloud credential rotation, cloud IAM review, runtime secret management (Vault, AWS Secrets Manager), or dependency vulnerability scanning.
    0 installs
  3. ▌
    Checking Production Readiness · criseulises bundle
    Audits a service for production readiness before its first deploy or a major rollout — verifies health endpoints, graceful shutdown, structured logging, 12-factor config, observability hooks, secrets handling, and container/runtime basics. Use when the user asks to "check production readiness", "pre-deploy audit", "is this ready to ship?", or mentions SLOs, health checks, graceful shutdown, or observability gaps. Covers a deterministic 40-item checklist, severity scoring, and a punch-list output. Do NOT use for security audits of secrets in source (use auditing-env-files), cloud cost review, pen testing, or load testing — those are separate skills.
    0 installs