jcarlosrodicio/opencode-agent-orchestration-kit

jcarlosrodicio/opencode-agent-orchestration-kit

Skill Claude CodeCodex

Guides 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.

jcarlosrodicio/opencode-agent-orchestration-kit

Skill Claude CodeCodex

Patterns and architectures for autonomous loops — from simple sequential pipelines to RFC-driven multi-agent DAG systems. Use when setting up autonomous development workflows, choosing the right loop architecture, or building CI/CD-style continuous development pipelines.

jcarlosrodicio/opencode-agent-orchestration-kit

Skill Claude CodeCodex

Conducts multi-axis code 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.

jcarlosrodicio/opencode-agent-orchestration-kit

Skill Claude CodeCodex

Simplifies code for clarity. 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.

jcarlosrodicio/opencode-agent-orchestration-kit

Skill Claude CodeCodex

Optimizes 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.

jcarlosrodicio/opencode-agent-orchestration-kit

Skill Claude CodeCodex

Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.

jcarlosrodicio/opencode-agent-orchestration-kit

Skill Claude CodeCodex

Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.

jcarlosrodicio/opencode-agent-orchestration-kit

Skill Claude CodeCodex

Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production, security-sensitive logic, irreversible operations), or any time a confident output would be cheaper to verify now…

jcarlosrodicio/opencode-agent-orchestration-kit

Skill Claude CodeCodex

Pattern for progressively refining context retrieval to solve the subagent context problem. Use when spawning subagents that need codebase context they cannot predict upfront, or when building multi-agent workflows where context is progressively refined.

jcarlosrodicio/opencode-agent-orchestration-kit

Skill Claude CodeCodex

Use the Open Design workbench to create editable visual projects, prototypes, landing pages, dashboards, mobile screens, decks, and implementation handoffs.

jcarlosrodicio/opencode-agent-orchestration-kit

Skill Claude CodeCodex

Optimizes application performance. Use when performance requirements exist, when you suspect performance regressions, or when Core Web Vitals or load times need improvement. Use when profiling reveals bottlenecks that need fixing.

jcarlosrodicio/opencode-agent-orchestration-kit

Skill Claude CodeCodex

Hardens code against vulnerabilities. Use when handling user input, authentication, data storage, or external integrations. Use when building any feature that accepts untrusted data, manages user sessions, or interacts with third-party services.

jcarlosrodicio/opencode-agent-orchestration-kit

Skill Claude CodeCodex

Grounds every implementation decision in official documentation. Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.

jcarlosrodicio/opencode-agent-orchestration-kit

Skill Claude CodeCodex

Drives development with tests. 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.

jcarlosrodicio/opencode-agent-orchestration-kit

Skill Claude CodeCodex

Discovers and invokes agent skills. Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked.

jcarlosrodicio/opencode-agent-orchestration-kit

Skill Claude CodeCodex

Comprehensive multi-phase verification system. Use after completing a feature, before creating a PR, when ensuring quality gates pass, or after refactoring.

jcarlosrodicio/opencode-agent-orchestration-kit

Skill Claude CodeCodex

Use for every final review of a diff - an independent pass that assumes the change is wrong, accounts for every changed file, attacks it along fixed dimensions, fact-checks its own findings and ends in an explicit verdict. Use also when the user asks for a red-team or devil's-advocate review.

jcarlosrodicio/opencode-agent-orchestration-kit

Skill Claude CodeCodex

Use when the user asks to commit or open a pull request, or when /autonomous reaches delivery - produces atomic commits that stage explicit paths only, with messages and a pull-request body written from the actual diff.

jcarlosrodicio/opencode-agent-orchestration-kit

Skill Claude CodeCodex

Use before specifying any feature, fix or refactor that arrives as a short request, roadmap line, screenshot or one-paragraph idea - turns it into an implementable specification with scope, reuse, requirements, acceptance criteria, hostile test cases and the open questions the request leaves ambiguous.

jcarlosrodicio/opencode-agent-orchestration-kit

Skill Claude CodeCodex

Use after tests and validation pass and before the final review, whenever a change could show up at runtime - a screen, a command, an endpoint, a job or a data store - to prove the change works in the running system, including its failure path, with repeatable steps and minimal evidence.

jcarlosrodicio/opencode-agent-orchestration-kit

Skill Claude CodeCodex

Use as the last step of any change that altered behavior, contracts, schema, architecture, setup or a roadmap item, before committing - updates the documentation the repository treats as its source of truth so the next session starts from accurate context.