Di Carlo Martínez avatar

Di Carlo Martínez

Community

@dicarsmtz · Costa Rica

10Followers
|
33Public Repos
|
9Published Skills

Software Engineer

Skills Distribution
DomainDeveloper To...Developer Tooling .. (35%)Cybersecurity & Co.. (25%)UI/UX & Creative M.. (20%)Business, Finance .. (20%)

Agent Skills by Di Carlo Martínez

Showing 9 vetted skills indexed across 1 GitHub repositories.

Frequently Asked Questions About Di Carlo Martínez

FAQPage Schema
What tasks can I accomplish with Di Carlo Martínez's skills?

You can generate Notion technical designs and lean PRDs, convert them into Jira Epics and micro-stories, run repository-grounded threat models, perform security best-practice reviews for Python, JavaScript/TypeScript, and Go, audit and refactor UI/UX surfaces, capture OS-level screenshots, and drive real browsers via Playwright.

Who are these skills designed for?

They target software engineers, senior/staff engineers, and architects who need implementation-ready design documents, AppSec threat models, secure-by-default code reviews, frontend design-system work, and terminal-driven browser debugging within a Codex-style engineering environment.

How do the Playwright and screenshot skills run in practice?

The playwright skill drives a real browser from the terminal using playwright-cli or a bundled wrapper for navigation, form filling, snapshots, and data extraction. The playwright-interactive skill keeps a persistent browser or Electron session via js_repl, while the screenshot skill captures full screens, windows, or pixel regions at OS level.

What prerequisites or dependencies do these skills require?

The technical-design skill requires access to source resources and a repository for mandatory codebase analysis. Security reviews only support Python, JavaScript/TypeScript, and Go. Browser skills need playwright-cli or the bundled wrapper, and threat modeling requires an explicit user request plus a target codebase or path.

How do the Notion and Jira skills keep output lean?

The PRD skill enforces brevity and focuses strictly on the MVP core loop to prevent decision fatigue. The Jira skill produces micro-stories under 100 words with explicit User Value statements, validates paths against the current codebase, and orders work by dependency without enterprise text bloat.