woliveiras

Create or revise coding-assistant skills that match this repository's structure and conventions. Use when: writing, renaming, or reviewing a skill. Do not use: for general writing or non-skill documentation.

Set up an Android CI/CD pipeline with lint, static analysis, unit tests, dependency review, and build verification. Use when: creating CI for Android, adding Gradle checks. Do not use: for local development setup, non-CI automation.

Run a disciplined bugfix loop with reproduction, hypotheses, regression test, fix, and cleanup. Use when: fixing bugs, debugging regressions, investigating failures. Do not use: for feature implementation, refactoring.

Design or review a ChromaDB-backed RAG workflow. Use when: creating collections, choosing embedding functions, chunking documents, writing retrievers. Do not use: for general LLM integration, non-RAG patterns.

Create, review, or debug a CI/CD workflow. Use when: editing GitHub Actions, fixing CI failures, adding release/deploy automation. Do not use: for general DevOps, infrastructure as code.

Structured code review workflow ensuring context and clarity. Use when: implementation complete, tests verified, before merge request. Do not use: during active implementation, before verification checklist, or for design reviews.

Structure consequential decisions with explicit trade-offs. Use when choosing architecture, tools, or strategy. Do not use for obvious fixes or time-critical emergencies.

Run or prepare a safe Google Cloud CLI operation. Use when: using gcloud, changing GCP resources, deploying to GCP. Do not use: for local CLI exploration, non-GCP operations.

Spec-Driven Development workflow. Use when user asks to "create spec", "new spec", "approve spec", "implement spec", "/spec", or when starting work on any non-trivial change in a repository that uses docs/specs/. Enforces immutable numbering, status lifecycle (Draft → Approved → In Progress → Implemented → Deprecated), and index synchronization.

Enforces the shared HTTP API contract defined in spec 0002. Use when implementing or reviewing any endpoint handler in servers/go, servers/rust, servers/python, servers/nodejs, or servers/dotnet. Trigger phrases: "implement endpoint", "add handler", "api contract", "/api-contract", or when editing any handlers.* or routes.* file in the servers/ directory.

Reproducibility rules, CSV schema, and measurement procedures for the benchmark defined in spec 0009. Use when implementing or reviewing files in benchmark/ or scripts/. Trigger phrases: "benchmark", "harness", "wrk", "rps_per_mb", "/benchmark-harness".

Patterns and anti-patterns for the .NET 10 Minimal API + Native AOT server defined in spec 0008. Use when implementing or reviewing any file in servers/dotnet/. Trigger phrases: "dotnet server", "csharp server", "native aot", "minimal api", "/server-dotnet".

Patterns and anti-patterns for the Go net/http server defined in spec 0004. Use when implementing or reviewing any file in servers/go/. Trigger phrases: "go server", "net/http", "modernc sqlite", "/server-go".

Patterns and anti-patterns for the Node.js/Fastify server defined in spec 0007. Use when implementing or reviewing any file in servers/nodejs/. Trigger phrases: "nodejs server", "fastify", "better-sqlite3", "/server-nodejs".

Patterns and anti-patterns for the Python/FastAPI + granian server defined in spec 0006. Use when implementing or reviewing any file in servers/python/. Trigger phrases: "python server", "fastapi", "granian", "/server-python".

Patterns and anti-patterns for the Rust/Axum server defined in spec 0005. Use when implementing or reviewing any file in servers/rust/. Trigger phrases: "rust server", "axum", "sqlx", "/server-rust".

Patterns and conventions for the Android (Jetpack Compose + Kotlin) app. Use when implementing or reviewing any screen, composable, ViewModel, repository, or service. Trigger phrases: "android pattern", "jetpack compose", "new screen", "new composable", "viewmodel", "/android".

arXiv Atom/XML API integration patterns. Use when implementing or reviewing any code in data/remote/ArxivApiService.kt or any file that calls the arXiv API. Trigger phrases: "arxiv api", "fetch papers", "query arxiv", "/arxiv-api", or when editing ArxivApiService.kt.

Debugging workflow for the Android (Kotlin + Jetpack Compose) app. Use when tracking down runtime errors, unexpected behavior, network issues, or state problems. Trigger phrases: "debug", "não está funcionando", "erro em runtime", "por que isso falha", "breakpoint", "/debug".

Unit testing patterns and conventions using JUnit5 + MockK + Turbine. Use when writing, reviewing, or debugging unit tests in this project. Trigger phrases: "write test", "unit test", "test this viewmodel", "test this repository", "/unit-test".

MADR (Markdown Any Decision Records) workflow. Use when recording an architecture or significant technical decision. Trigger phrases: "new adr", "architecture decision", "record decision", "write adr", "/madr".

Spec-Driven Development workflow. Use when user asks to "create spec", "new spec", "approve spec", "implement spec", "/spec", or when starting work on any non-trivial change in a repository that uses docs/specs/. Enforces immutable numbering, status lifecycle (Draft → Approved → In Progress → Implemented → Deprecated), and index synchronization.

Product Requirements Document (PRD) writing workflow. Use when the user wants to define a new feature, product area, or user journey before writing specs. Trigger phrases: "write prd", "product requirements", "new feature brief", "define feature", "/write-prd".

Update project documentation after implementing a feature. Use when: updating docs, documentation, update docs after implementation, sync docs with code.

Extract and formalize domain terminology into a glossary. Use when: defining domain terms, building a glossary, hardening terminology, domain model, DDD, ubiquitous language, glossary.

Generate a structured spec from direct input. Use when: you already know what you want and just need the formatted template. For exploration and interviews, use the spec-writer agent instead.

Generate unit tests from a spec's acceptance criteria. Use when: you have a written spec and need tests, generate tests from spec, TDD from spec, spec to tests.

Scaffold a new Go service package following Bookaneer's architecture. Use when creating a new domain service, adding a new integration (metadata provider, download client, indexer, notification channel), or adding a new API handler. Generates code following the project's layered architecture, interface patterns, and conventions.

Review code for security vulnerabilities aligned with OWASP Top 10:2025. Use when asked to audit, review, or check code for security issues including SQL injection, path traversal, authentication flaws, broken access control, and cryptographic failures in Go backend or React frontend code.

UI/UX design patterns and Material 3 best practices for Petit Android app. Use when: creating new screens, building Compose layouts, choosing Material 3 components, designing forms, implementing loading/empty/error states, adding animations and transitions, working with typography hierarchy, spacing and sizing, card and list designs, navigation patterns, visual feedback, color usage, dark theme support, skeleton loaders, confirmation feedback, swipe actions.

Security best practices for Petit Android app. Use when: handling user input, working with Room database queries, managing file I/O (photo storage, export/import), implementing authentication (Firebase Auth), storing sensitive data (keystore, DataStore), configuring ProGuard, validating data boundaries, implementing export/import functionality, working with notifications, handling deep links.

Offline-first architecture patterns for Petit Android app. Use when: implementing data persistence, designing Room database operations, working with sync status tracking, building cache strategies, implementing WorkManager background tasks, designing data flows that must work without network, handling export/import, planning future Firebase/Firestore cloud sync. Covers Room as source of truth, soft delete, SyncStatus, WorkManager, DataStore.