all publishers

marcioaltoe

@marcioaltoe source repo

116 published skills · page 2 of 2

  1. ▌
    External API Adapters · marcioaltoe
    Use when designing, writing, or reviewing adapters for external APIs, ERP systems, payment providers, storage providers, or third-party services. Covers boundary contracts, typed clients, retries, timeouts, pagination, error normalization, observability, and tests. Do not use for pure internal domain logic with no external service boundary.
    4 installs
  2. ▌
    Hono API Best Practices · marcioaltoe bundle
    Design HTTP APIs for Bun + Hono backends using Clean Architecture, Zod contracts in a shared package, OpenAPI generation from Zod, and thin controllers. Supports two selectable conventions — standard REST (resource paths with GET/POST/PATCH/PUT/DELETE) and POST-only action-based paths — picking one per project. Use when defining new endpoints, auditing or refactoring existing routes, shaping request/response contracts and envelopes, establishing API standards, or mapping typed application errors to HTTP status codes. Do not use for GraphQL, tRPC, non-Hono runtimes, or frontend-only concerns.
    6 installs
  3. ▌
    Integration Contract Testing · marcioaltoe
    Use when writing or reviewing tests for external API adapters, storage adapters, database integration boundaries, or service contracts. Covers fixture design, schema validation, negative contracts, fakes, recorded responses, and CI-safe verification. Do not use for simple pure unit tests with no boundary contract.
    3 installs
  4. ▌
    Git Commit · marcioaltoe
    Automatically analyzes code changes and creates git commits with conventional commit messages when the user indicates they want to save/commit their work. Use when user mentions committing, saving work, or wants changes recorded in git history. Examples - "commit these changes", "save this work", "I'm done with this feature, let's commit", "create a commit for the auth updates".
    8 installs
  5. ▌
    UI Designer · marcioaltoe
    Expert UI/UX designer for React applications with shadcn/ui and Tailwind CSS. **ALWAYS use when creating UI components, implementing responsive layouts, or designing interfaces.** Use when user needs component creation, design implementation, responsive layouts, accessibility improvements, dark mode support, or design system architecture. Examples - "create a custom card component", "build a responsive navigation", "setup shadcn/ui button", "implement dark mode", "make this accessible", "design a form layout".
    7 installs
  6. ▌
    Test Engineer · marcioaltoe
    Expert testing and quality engineer for Vitest (running on Bun). Use when user needs test creation, test strategy, code quality setup, E2E testing, or debugging test failures. Examples - "write tests for this function", "create E2E tests with Playwright", "help me test this API route", "setup testing infrastructure", "why is this test failing?", "improve code quality with Biome".
    9 installs
  7. ▌
    Database Architect · marcioaltoe
    Expert database schema designer and Drizzle ORM specialist. Use when user needs database design, schema creation, migrations, query optimization, or Postgres-specific features. Examples - "design a database schema for users", "create a Drizzle table for products", "help with database relationships", "optimize this query", "add indexes to improve performance", "design database for multi-tenant app".
    8 installs
  8. ▌
    Pull Request Skill · marcioaltoe bundle
    Pull Request review manager for CodeRabbit AI. **ALWAYS use when user needs to work with PR reviews, fix CodeRabbit issues, or check review status.** Downloads, organizes, and helps resolve review comments systematically. Examples - "download PR reviews", "fix CodeRabbit issues for PR 123", "check review status", "organize review comments by severity".
    7 installs
  9. ▌
    Code Standards · marcioaltoe
    Expert in code design standards including SOLID principles, Clean Code patterns (KISS, YAGNI, DRY, TDA), and pragmatic software design. **ALWAYS use when designing ANY classes/modules, implementing features, fixing bugs, refactoring code, or writing functions.** Use proactively to ensure proper design, separation of concerns, simplicity, and maintainability. Examples - "create class", "design module", "implement feature", "refactor code", "fix bug", "is this too complex", "apply SOLID", "keep it simple", "avoid over-engineering".
    12 installs
  10. ▌
    Backend Engineer · marcioaltoe
    Backend engineering with Modular Monolith, bounded contexts, and Hono. **ALWAYS use when implementing ANY backend code within contexts, Hono APIs, HTTP routes, or service layer logic.** Use proactively for context isolation, minimal shared kernel, and API design. Examples - "create API in context", "implement repository", "add use case", "context structure", "Hono route", "API endpoint", "context communication", "DI container".
    8 installs
  11. ▌
    Project Workflow · marcioaltoe
    Development workflow and quality gates for the Bun + TypeScript stack. **ALWAYS use before commits** to ensure quality gates are met. Also use when starting development or when user asks about workflow process. Examples - "before commit", "quality gates", "workflow checklist", "bun commands", "pre-commit checks".
    7 installs
  12. ▌
    Frontend Engineer · marcioaltoe
    Expert frontend engineering with simplified pragmatic architecture, React 19, TanStack ecosystem, and Zustand state management. **ALWAYS use when implementing ANY frontend features.** Use when setting up project structure, creating pages and state management, designing gateway injection patterns, setting up HTTP communication and routing, organizing feature modules, or optimizing performance. **ALWAYS use when implementing Gateway Pattern (Interface + HTTP + Fake), Context API injection, Zustand stores, TanStack Router, or feature-based architecture.**
    6 installs
  13. ▌
    Clean Architecture · marcioaltoe
    Clean Architecture principles for Modular Monolith with bounded contexts and minimal shared kernel. **ALWAYS use when working on backend code, ESPECIALLY when creating files, deciding file locations, or organizing contexts (auth, tax, bi, production).** Use proactively to ensure context isolation and prevent "Core Obesity Syndrome". Examples - "create entity", "add repository", "where should this file go", "modular monolith", "bounded context", "shared kernel", "context isolation", "file location", "layer organization".
    7 installs
  14. ▌
    Naming Conventions · marcioaltoe
    Expert in naming conventions for files, directories, classes, functions, and variables. **ALWAYS use when creating ANY files, folders, classes, functions, or variables, OR when renaming any code elements.** Use proactively to ensure consistent, readable naming across the codebase. Examples - "create new component", "create file", "create folder", "name this function", "rename function", "rename file", "rename class", "refactor variable names", "review naming conventions".
    8 installs
  15. ▌
    Typescript Type Safety · marcioaltoe
    TypeScript type safety including type guards and advanced type system features. **ALWAYS use when writing ANY TypeScript code (frontend AND backend)** to ensure strict type safety, avoid `any` types, and leverage the type system. Examples - "create function", "implement class", "define interface", "type guard", "discriminated union", "type narrowing", "conditional types", "handle unknown types".
    11 installs
  16. ▌
    Error Handling Patterns · marcioaltoe
    Error handling patterns including exceptions, Result pattern, validation strategies, retry logic, and circuit breakers. **ALWAYS use when implementing error handling in backend code, APIs, use cases, or validation logic.** Use proactively for robust error handling, recovery mechanisms, and failure scenarios. Examples - "handle errors", "Result pattern", "throw exception", "validate input", "error recovery", "retry logic", "circuit breaker", "exception hierarchy".
    8 installs