batur
- 19 skills
- 0 followers
- 6 hours ago last updated
- ▌ Eslint · baturEnforce and review the TypeScript ESLint baseline for this project. Use when creating or reviewing ESLint flat config, lint rules, imports, exports, naming, file names, side-effect imports, environment access, component boundaries, or provider/SDK dependency restrictions in TypeScript code.
- ▌ Openapi · baturCreate, update, and review OpenAPI documentation for REST APIs. Use when adding or changing API endpoints, request/response DTOs, route metadata, authentication schemes, error envelopes, pagination, filtering, sorting, examples, generated OpenAPI files, SDK contracts, or contract-test expectations.
- ▌ Cicd Git · batur bundleEnforces CI/CD and Git workflow standards for TypeScript projects. Use when creating or reviewing branches, commits, pull requests, GitHub Actions, deployment pipelines, release/versioning, CODEOWNERS, hooks, secret scanning, OpenAPI checks, migrations, raw SQL gates, or day-one deployability.
- ▌ Build Mvp · batur bundlePlan, implement, verify, and prepare the smallest releasable product or bounded first release that delivers one primary end-to-end outcome to a defined early audience and creates measurable feedback. Use when the user says MVP, minimum viable product, first usable release, early release, core product flow, private beta, or asks to turn a validated PoC or prototype into a usable product. Keep non-core features out of scope while retaining essential security, data integrity, validation, error handling, testing, observability, deployment, rollback, and support requirements. Do not use merely to test feasibility; use validate-poc when critical assumptions remain unresolved.
- ▌ API Design · baturDesign and review TypeScript REST APIs using the project baseline, REST API Guidelines, /api/v1 versioning, plural kebab-case resources, custom JSON envelopes, cursor pagination, PATCH semantics, stable error contracts, request IDs, idempotency, DTO/serializer boundaries, and OpenAPI impact checks. Use when creating or reviewing HTTP endpoints, controllers, route handlers, API DTOs, serializers, API clients, pagination, filtering, sorting, or request/response contracts.
- ▌ TS Testing · baturDefines the TypeScript testing standard for AI coding and review. Use when adding, changing, or reviewing tests, test structure, Vitest, Playwright e2e, validation/error/PATCH/auth/security/tenant tests, fixtures, mocks/fakes, coverage, CI test commands, or any behavior that needs test protection.
- ▌ Typescript · baturApply the project TypeScript baseline when creating, editing, or reviewing TypeScript code, tsconfig files, imports, module formats, strict typing, NodeNext backend projects, frontend bundler projects, build configs, and package-level TypeScript conventions.
- ▌ Validation · baturApply the project's Zod runtime validation standard for TypeScript APIs, forms, env/config, webhooks, third-party responses, and AI outputs. Use when creating or reviewing schemas, DTO inputs, request body/query/path parsing, PATCH validation, Zod error mapping, or boundary validation.
- ▌ Patch Update · baturDesign, implement, and review PATCH/partial-update behavior in TypeScript REST APIs. Use when adding or reviewing PATCH endpoints, update schemas, nullable field clearing, immutable fields, optimistic concurrency, update serializers, or tests for partial updates.
- ▌ Validate Poc · batur bundleDesign, implement, and evaluate a time-boxed proof of concept that tests the riskiest product, technical, integration, data, performance, or workflow assumption using explicit success, failure, and exit criteria and an evidence-backed go, pivot, stop, or inconclusive recommendation. Use when the user says PoC, proof of concept, concept test, feasibility test, technical spike, validate an application flow, test whether an architecture or integration can work, or reduce uncertainty before full implementation. Do not use for a production release or a complete early-user product; use build-mvp after feasibility is sufficiently resolved.
- ▌ Error Handling · baturDesign, implement, or review TypeScript REST API error handling. Use when adding API errors, AppError/DomainError classes, HTTP status mapping, Zod error mapping, PATCH/update errors, external provider failures, logging/error-tracker integration, or when reviewing whether client responses are safe and consistent.
- ▌ AI Coding Review · baturMeta skill for AI coding agents and reviewers in TypeScript software projects. Use when planning, implementing, refactoring, reviewing, or approving AI-generated code; when deciding which project skill to apply; when enforcing architecture, API, security, testing, documentation, CI/CD, validation, error handling, persistence, auth, logging, and OpenAPI standards together.
- ▌ Documentation Adr · batur bundleUse this skill when creating, updating, or reviewing repository documentation, ADRs, engineering standards, architecture docs, Mermaid diagrams, README onboarding, Copilot instructions, or documentation changes required by architecture/API/security/database/auth/deployment decisions in TypeScript software projects.
- ▌ Security Baseline · baturEnforce the project's secure-by-default TypeScript/Node.js security baseline. Use when creating or reviewing authentication, authorization, API endpoints, input handling, CORS, rate limits, secrets, logging, webhooks, file uploads, SSRF-sensitive URL fetching, dependency/security checks, or AI-generated code.
- ▌ Auth Authorization · baturDefines authentication and authorization rules for TypeScript applications. Use when adding or reviewing auth guards, AuthContext, provider adapters, role/permission checks, tenant or organization boundaries, API key auth, 401/403/404 behavior, protected routes, and server-side access control.
- ▌ Config Environment · baturEnforce TypeScript config and environment rules. Use when adding or reviewing env variables, process.env usage, Zod env validation, server/client config separation, secrets, public env exposure, feature flags, provider config, .env.example, or adapter initialization.
- ▌ Database Persistence · baturApply the TypeScript database and persistence architecture standard. Use when adding or reviewing PostgreSQL, Supabase, Drizzle, Prisma, MongoDB, Firebase/Firestore, repositories, migrations, transactions, tenant-scoped queries, serializers, IDs, timestamps, soft delete, raw SQL, indexes, constraints, audit logs, or persistence tests.
- ▌ Logging Observability · baturDefines logging and observability standards for TypeScript apps. Use when adding or reviewing loggers, request IDs, structured logs, error tracking, Sentry/Datadog/OpenTelemetry adapters, health checks, external service logging, safe redaction, or production debugging behavior.
- ▌ Component Architecture · baturEnforce the TypeScript component-based architecture baseline. Use when creating, moving, or reviewing modules, features, shared code, use-cases, controllers, routes, repositories, adapters, serializers, integrations, dependency boundaries, or cross-component imports.