developer

Plugin developer from marketplace developer-vault in facundomartinezvidal/developer-vault. Commands read from the repo's manifest — 5 days ago.

Skills (22)

• api-design

  Designs and reviews APIs other code depends on: HTTP endpoints, RPC, GraphQL, webhooks, events and public library functions. Use for request and response shapes, status codes, errors, pagination, idempotency, versioning and breaking changes (\"qué status devuelvo\", \"esto rompe a los clientes\").

• clean-code

  Makes code readable at the level of names, functions, comments, error handling and async code, in any language. Use when code is hard to follow, a name misleads or errors are swallowed (\"esta función es muy larga\"). Step-by-step restructuring: refactoring; whole PRs: reviewing-code.

• data-structures-and-algorithms

  Chooses data structures and algorithms and reasons about cost, in any language. Use when code is slow on large inputs, for Big-O, caching or profiling, or for sorting, search, graph and dynamic programming problems (\"esto tarda mucho\", \"qué estructura uso\"). Queries: relational-databases.

• debugging

  Finds the root cause of a failure with a reproduce, hypothesize and prove method, in any language. Use for stack traces, crashes, hangs, flaky or production-only failures and fixes that didn't hold (\"por qué falla\", \"falla a veces\"). Not needed when the error already shows the cause.

• design-patterns

  Chooses, applies and removes design patterns and GRASP responsibilities, in any language. Use when growing conditionals, object creation or notifications might need a pattern, to judge if one is overkill, or to explain one (\"qué patrón uso\", \"quién debería hacer esto\").

• developer

  Software developer for any programming language that implements features, fixes bugs, refactors and writes tests, and also advises on code. Use for building or changing code, code review, diagnosing failures, testing strategy, secure coding, APIs, production behavior, choosing a pattern or data stru

• clean-architecture

  Reviews and designs code structure with Clean Architecture: layers, the Dependency Rule, ports and adapters, boundaries and packaging. Use when a framework, ORM or database leaks into business logic, or to decide where code lives (\"cómo estructuro el proyecto\", \"dónde va esta lógica\").

• domain-driven-design

  Models complex business domains with ubiquitous language, bounded contexts and aggregates. Use when business terms conflict, a shared model is tangled, or a business invariant needs a consistency boundary (\"cómo modelo este dominio\", \"agregados\"). Layers and folders alone: clean-architecture.

• software-design

  Designs and reviews module interfaces: information hiding, what callers must know, call ordering, and failure or retry contracts. Use when one change spreads across modules, an API is easy to misuse or a layer adds nothing (\"cómo diseño esta interfaz\", \"lo separo o lo junto\").

• threat-modeling

  Threat-models a design with STRIDE: assets, data flows, trust boundaries, ranked risks and mitigations. Use when designing or reviewing something with users, money, files, tenants, webhooks or AI agents (\"es seguro este diseño\", \"cómo lo podrían atacar\"). Vulnerable code: secure-coding.

• framework-practices

  Applies current practices of the framework in use, with deep guidance for ASP.NET Core and Spring Boot, checking official docs for the installed version. Use for controllers, DI, configuration, ORMs, framework security, tests, startup and upgrades (\"cómo se hace esto en Spring\").

• implementing-designs

  Turns an architect's plan, ADR, C4 view, DDD model or threat model into working code without losing what was decided. Use to implement a design or check code against one (\"implementá lo que dijo el arquitecto\", \"cómo llevo esto a código\"). Open decisions: architect agent.

• opening-pull-requests

  Opens pull requests and writes their title and description following the project's conventions and PR template. Shows the exact text and publishes nothing until confirmed. Use to open or describe a PR or set up PR conventions (\"abrí el PR\", \"armá la PR\").

• pragmatic-practices

  Advises on how to approach development work: unclear requirements, slicing, estimates, prototypes, unfamiliar code, dependency upgrades, merge conflicts, docs and automation (\"cómo encaro esto\", \"cuánto puede llevar\"). Not needed for a clearly specified small task.

• production-readiness

  Makes code behave well in production with logging, metrics, tracing, timeouts, retries, graceful failure and safe releases. Use when code calls other services, runs as a job or consumer, or is about to ship (\"agregá logs\", \"está listo para producción\"). A known failure: debugging.

• refactoring

  Improves existing code without changing behavior, using code smells and small, safe refactoring moves. Use when code resists a change, before adding a feature, or to judge if a cleanup is worth it (\"refactorizá esto\", \"qué code smells tiene\"). Layers or modules: architect agent.

• relational-databases

  Designs relational schemas and migrations, writes and reviews SQL, and handles indexes, transactions and concurrency on any SQL engine or ORM. Use for tables, keys, slow queries, balances, stock or uniqueness (\"cómo modelo estas tablas\", \"falta un índice\"). Not for NoSQL.

• reviewing-code

  Reviews diffs, pull requests and commits for correctness, safety and maintainability, with feedback people can act on. Use before merging or to check one's own change (\"revisá este PR\", \"le das una mirada\"). A whole package's structure: architect agent.

• secure-coding

  Writes and reviews code to resist vulnerabilities, following OWASP Top 10 and CWE. Use when code handles input, SQL or shell commands, files, auth, sessions, permissions, tokens, secrets or personal data, or someone asks if code is safe (\"esto es seguro\"). Design threats: threat-modeling.

• testing

  Writes and reviews automated tests and makes code testable, in any language. Use when behavior needs tests, mocks are brittle, a suite is slow or flaky, code has no tests, or for TDD and coverage (\"qué debería testear\", \"cómo testeo esto\"). An unknown failure: debugging.

• user-interfaces

  Builds and reviews screens and components on any front-end stack. Use for pages, forms, tables, modals, client state and UI bugs, including loading, empty and error states, accessibility and responsive layout (\"armame esta pantalla\", \"el formulario no anda\").

• writing-commits

  Creates Git commits and writes their messages following the project's conventions, looking first in conventions/commits.md. Use to commit, split a change into commits, write a message or set up commit conventions (\"hacé el commit\", \"qué título le pongo\"). Without conventions, offers a default.

Subagents (1)

• developer

  Software developer for any programming language that implements features, fixes bugs, refactors and writes tests, and also advises on code. Use for building or changing code, code review, diagnosing failures, testing strategy, secure coding, APIs, production behavior, choosing a pattern or data stru

Similar plugins