rubenmarcus/rubenmarcus-skills

Audit and implement answer-engine discovery using aeo.js, crawler policy, canonical identity, structured data, and machine-readable content. Use for AEO/GEO audits, llms.txt, AI crawler access, or integrating aeo.js into a website.

Coordinate coding agents using isolated Git worktrees and explicit race, comparison, or sequential handoff strategies. Use when implementing alternatives or splitting coding work across agents, branches, or sessions.

Independently review a proposed change, design, or analysis for concrete failures and unsupported claims. Use when adversarial review is requested or a consequential result needs verification by someone other than its author.

Investigate and fix defects by reproducing the reported path, comparing hypotheses, and checking runtime behavior. Use for bugs, regressions, intermittent failures, and fixes needing evidence beyond a plausible code change.

Improve a product or artifact through repeated construction, independent critique, measured comparison, and regression checks. Use for sustained iteration when a single implementation pass cannot establish the required quality.

Add or repair local Git hooks for staged secret scanning and project-specific quality checks without overwriting existing workflows. Use for pre-commit, commit-msg, pre-push, or a requested local gate before sharing code.

Coordinate multiple agents on implementation or research with isolated ownership, reproducible handoffs, independent checks, and evidence-based conflict resolution. Use when parallel or peer-agent work is requested or already in progress.

Design or repair checks that measure real behavior and fail under a deliberate defect. Use when adding invariants, probes, regression gates, quality thresholds, or diagnosing a green check that misses a real failure.

Research a question using attributable sources, explicit uncertainty, and evidence that can change a decision. Use for technical, market, competitor, social-media, or literature research needing a defensible synthesis.

Turn a task, issue, design, or document into an implementation plan with observable acceptance criteria and bounded work. Use before a multi-step implementation when the input leaves material behavior or dependencies unclear.

Run an authorized implementation through repeated focused edits and real validation feedback with recoverable progress. Use for a requested coding loop, a multi-step change needing iterations, or resuming an existing loop.