barcelosvinicius
- 29 skills
- 0 followers
- 7 hours ago last updated
- ▌ Proc Adr · barcelosviniciusUse when making any significant technical decision that affects structure, security, performance, or is difficult to reverse. Process for recording Architectural Decision Records (ADRs) — when to create them, the mandatory format, naming, and status lifecycle.
- ▌ Proc Sdd · barcelosvinicius bundleUse when a project spans more than two weeks, runs multiple features in parallel, or the AI starts contradicting earlier decisions (context drift). Spec-Driven Development: executable specs as source of truth — spec → plan → tasks hierarchy, EARS syntax, atomic task rules, and the context-as-graph model for token-efficient sessions.
- ▌ Infra CI CD · barcelosvinicius bundleUse when configuring or evolving a project's CI/CD pipeline — stage ordering, dependency audit (SCA), static analysis (SAST), automated dependency updates, commit message validation, and merge gates. Stack-agnostic principles with GitHub Actions / Maven / npm examples available as on-demand resources.
- ▌ Fe UX Patterns · barcelosvinicius bundleUse when creating or reviewing any UI component, screen, or form. Operational UX guide — visual hierarchy, colors, loading states, forms, perceived performance, and user feedback patterns.
- ▌ Proc Changelog · barcelosvinicius bundleUse when preparing a release, creating release notes, generating user-facing updates, or closing a sprint with deliverables. Maintains CHANGELOG.md from Conventional Commits following Keep a Changelog + SemVer.
- ▌ Be DB Migrations · barcelosvinicius bundleUse when creating tables, adding columns, creating indexes, changing constraints, or migrating data with any versioned migration tool (Flyway, Liquibase, Alembic, Prisma Migrate, Rails migrations). Naming, idempotency, and safe schema evolution rules.
- ▌ Proc Code Review · barcelosviniciusUse when reviewing a PR, requesting review from another agent, or implementing a quality gate before merge. Structured review protocol — per-layer checklists, responsibility by change type, feedback categories, and delegation between agents.
- ▌ Be API Versioning · barcelosvinicius bundleUse when creating the initial structure of a REST API, introducing a breaking change, or migrating unversioned endpoints to a versioned model. URL-prefix strategy (/api/v1/), breaking-change criteria, deprecation lifecycle with Sunset headers, and a phased migration checklist.
- ▌ Ops Observability · barcelosviniciusUse when adding logging, metrics, or tracing; defining SLOs and alerts; writing runbooks; or preparing a service for production operation. Structured logs, the four golden signals, alert hygiene, and runbook discipline.
- ▌ Proc Safe Removal · barcelosviniciusUse before deleting code, configuration, or documentation, and before moving content between files. Removal is the only operation whose error no test catches — the test dies with the code. Four axes to clear before deleting, a verification protocol for relocations, and the `// NB:` note that keeps the reason alive for whoever asks again.
- ▌ Proc Skill Creator · barcelosvinicius bundleUse when a needed domain/process/infrastructure skill is missing, when an existing skill needs significant refactoring, or when expanding the base kit. Meta-skill: discovery process, mandatory structure (SKILL.md + resources), naming, quality criteria, and delivery checklist.
- ▌
- ▌ Proc Context Budget · barcelosviniciusUse when the session feels sluggish, output quality drops, after adding several skills/agents/MCP servers, or to decide whether there is room to add more — audits what consumes the context window (agents, skills, MCP tools, rules, CLAUDE.md) and returns prioritized token-savings recommendations.
- ▌ Proc Domain Mapping · barcelosvinicius bundleUse at project kickoff, before introducing a new bounded context, or when domain boundaries seem to have drifted. DDD-based pipeline: identifies bounded contexts, aggregates, domain events, and process flows from code structure; output feeds the domain map in docs/structural-analysis.md.
- ▌ Proc Learning Trail · barcelosviniciusUse when adopting a new practice, technology, or pattern in the project, or when onboarding needs a guided path. Creates and maintains the Learning Trail — the record of adopted practices, why each exists, and learning resources for the team.
- ▌ Be JWT Auth Patterns · barcelosvinicius bundleUse when implementing token-based authentication (JWT), deciding how to revoke tokens on logout, or choosing where to store tokens on the client. Stack-agnostic flow, secret handling, blocklist revocation, and client storage rules, with Java/Spring examples as a resource.
- ▌ Proc Impact Analysis · barcelosvinicius bundleUse before opening a PR, after a large refactoring, or whenever a change touches a shared boundary. Determines which modules, flows, domain events, and downstream consumers are affected, assigns a risk level, and produces a focused review checklist.
- ▌ QA Verification Loop · barcelosviniciusUse when finishing a change, before declaring work "done", or before opening a PR — a stack-agnostic verification loop (build, type-check, lint, tests, security scan, diff review) that produces a READY / NOT READY verdict so quality is checked in the generation loop, not just in CI.
- ▌ Be API Error Handling · barcelosvinicius bundleUse when creating a centralized exception handler, adding new error types, or defining a REST API's error response contract. Exception hierarchy, HTTP status mapping, and RFC 9457 problem-details format, with a Spring Boot example as a resource.
- ▌ QA Test Data Builders · barcelosviniciusUse when writing unit or integration tests that need test data. Centralize object creation in fixture builders, follow the AAA pattern (Arrange, Act, Assert), and keep data deterministic — avoids repetition and flaky tests.
- ▌ Be Pagination Patterns · barcelosvinicius bundleUse when implementing or fixing any REST endpoint that returns a collection. Never return an unbounded list — server-side pagination with offset or cursor strategies, response contract, and limits. Spring Boot and Angular examples as on-demand resources.
- ▌ Engineering Principles · barcelosviniciusUse when making a design decision and needing the project-independent ground rules — UX, security, coupling, testing, observability, resilience, and the AI-assisted documentation protocol. One-page digest with pointers into the full engineering-principles.md document.
- ▌ Proc Release Checklist · barcelosviniciusUse before any production delivery — first deploy, release with schema or security changes, or any release after more than two weeks of inactivity. Pre-go-live validation: security, database, API, frontend, observability, process, and post-deploy checks.
- ▌ Sec Secrets Management · barcelosviniciusUse when handling any credential — API keys, database passwords, signing secrets, certificates — or when configuring environments and CI. Storage, injection, rotation, scanning, and incident response for leaked secrets.
- ▌ Proc Code Documentation · barcelosvinicius bundleUse when writing or reviewing comments, docstrings, and inline documentation in code. When to comment vs. when to rename, the "why not what" rule, documenting public/business-rule functions, and avoiding comment rot. Per-language doc-comment formats as resources.
- ▌ Proc Session Continuity · barcelosvinicius bundleUse at the start and end of every work session (human or AI-assisted). At start: read docs/HISTORY.md, docs/structural-analysis.md, and git status before touching code. At end: update those docs and commit them with the code. Mandatory continuity protocol that prevents rework and context drift.
- ▌ Proc Structural Analysis · barcelosvinicius bundleUse at project kickoff, after a major refactoring, or whenever the architecture diverges from its documentation. Guided pipeline: scans the project, maps modules to layers, extracts dependencies and domain boundaries, detects risks, and outputs a versioned structural-analysis.md.
- ▌ Fe Accessibility Patterns · barcelosvinicius bundleUse when implementing any interactive component, form, modal, or table. Concrete WCAG 2.1 AA accessibility patterns — semantic HTML, ARIA attributes, keyboard navigation, color contrast, and automated testing.
- ▌ Proc Dependency Management · barcelosviniciusUse when adding a new dependency, upgrading existing ones, or auditing the dependency tree. Selection criteria, lockfile discipline, update cadence, CVE response, and removal hygiene for any package ecosystem.