g-tavares14
- 21 skills
- 0 followers
- 6 hours ago last updated
- ▌ Context Engineering · g-tavares14Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.
- ▌ Shipping And Launch · g-tavares14Prepares production launches. Use when the user runs /agent-skills:ship. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.
- ▌ CI CD And Automation · g-tavares14Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
- ▌ Documentation And Adrs · g-tavares14Records decisions and documentation. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
- ▌ Security And Hardening · g-tavares14Hardens code against vulnerabilities. Use when auditing an input handler for vulnerabilities, when handling user input, authentication, data storage, or external integrations, or when checking a login flow is safe against the OWASP Top Ten. Use when building any feature that accepts untrusted data, manages user sessions, or interacts with third-party services. Use when auditing dependencies for known vulnerabilities, triaging package-manager audit findings, or assessing supply-chain risk in a new package. Use when personal data or privacy compliance (GDPR, CCPA) is involved.
- ▌ Code Review And Quality · g-tavares14Conducts multi-axis code review. Use when the user runs /agent-skills:review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
- ▌ Spec Driven Development · g-tavares14Creates specs before coding. Use when the user runs /agent-skills:spec. Use when starting a new project, feature, or significant change and no specification exists yet. Use when drafting a PRD or requirements document with objectives and scope, or when requirements are unclear, ambiguous, or only exist as a vague idea. Use when a single requirement spans several independently testable capabilities and needs decomposing into a capability map of modules before specifying.
- ▌ Test Driven Development · g-tavares14Drives development with tests using the red-green-refactor loop. Use when the user runs /agent-skills:test. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
- ▌ API And Interface Design · g-tavares14Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.
- ▌ Ship · g-tavares14 bundleCodex shortcut for the shipping lifecycle. Use only when the user explicitly invokes $ship.
- ▌ Spec · g-tavares14 bundleCodex shortcut for the specification lifecycle. Use only when the user explicitly invokes $spec.
- ▌ Test · g-tavares14 bundleCodex shortcut for the test-driven development lifecycle. Use only when the user explicitly invokes $test.
- ▌ Plan Work · g-tavares14 bundleCodex shortcut for the planning lifecycle. Use only when the user explicitly invokes $plan-work.
- ▌ Review Code · g-tavares14 bundleCodex shortcut for the code review lifecycle. Use only when the user explicitly invokes $review-code.
- ▌ Code Simplification · g-tavares14Simplifies code for clarity. Use when the user runs /agent-skills:code-simplify. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.
- ▌ Doubt Driven Development · g-tavares14Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testing a plan for hidden failure modes, when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production auth, security-sensitive logic, a high-stakes migration, irreversible operations), or any time a confident output would be cheaper to verify now than to debug later.
- ▌ Source Driven Development · g-tavares14Grounds every implementation decision in official documentation. Use when you want to verify an approach against the official docs before implementing it, or when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.
- ▌ Incremental Implementation · g-tavares14Delivers changes incrementally in thin, verifiable slices. Use when the user runs /agent-skills:build. Use when implementing any feature or change that touches more than one file, or when picking up the next task from a plan. Use when rolling a change out behind a feature flag, when you're about to write a large amount of code at once, or when a task feels too big to land in one step.
- ▌ Git Workflow And Versioning · g-tavares14Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump, tagging, or writing a changelog.
- ▌ Planning And Task Breakdown · g-tavares14Breaks work into ordered tasks. Use when the user runs /agent-skills:plan. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
- ▌ Constraint Driven Development · g-tavares14 bundleEstablishes a project's quality bar as a written contract and stops agents quietly lowering it. Use when the user runs /agent-skills:constraints. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no number in mind, records everything in CONSTRAINTS.md, and watches the diff for a weakened bar — new @ts-ignore or eslint-disable suppressions, skipped or deleted tests, assertions stripped out, unimplemented stubs, thresholds edited down. Use when no quality bar is written down, when the user says "set up constraints" or "define our standards", when the user wants dimensions they care about — accessibility, web performance, coverage — set up as enforced constraints, when an agent keeps silencing checks or skipping tests to get to green, when you need a coverage or performance threshold and don't know what number to pick, or when an agent writes more code than anyone will read.