Skip to main content
jcwleo
GitHub creator profile

jcwleo

Repository-level view of 22 collected skills across 1 GitHub repositories.

skills collected
22
repositories
1
updated
2026-07-28
repository map

Where the skills live

Top repositories by collected skill count, with their share of this creator catalog and occupation spread.

repository explorer

Repositories and representative skills

ultrawork
computer-occupations-all-other

Use when the user explicitly delegates autonomous end-to-end delivery across discovery, planning, implementation, and verification; not for a small execution-ready task.

2026-07-28
ultrawork
computer-occupations-all-other

Use when the user explicitly delegates autonomous end-to-end delivery across discovery, planning, implementation, and verification; not for a small execution-ready task.

2026-07-28
ralplan
software-developers

Use when requirements are sufficiently known but implementation is broad, risky, architecture-sensitive, cross-file, multi-step, or strategy-unclear and needs a plan; not for still-vague discovery or an execution-ready task.

2026-07-28
test-driven-development
software-quality-assurance-analysts-and-testers

Use when the user explicitly requests TDD, test-first, or RED-GREEN-REFACTOR, or an already-selected workflow enters its internal TDD gate; ordinary implementation remains Ralph.

2026-07-28
ralplan
software-developers

Use when requirements are sufficiently known but implementation is broad, risky, architecture-sensitive, cross-file, multi-step, or strategy-unclear and needs a plan; not for still-vague discovery or an execution-ready task.

2026-07-28
test-driven-development
software-quality-assurance-analysts-and-testers

Use when the user explicitly requests TDD, test-first, or RED-GREEN-REFACTOR, or an already-selected workflow enters its internal TDD gate; ordinary implementation remains Ralph.

2026-07-28
systematic-debugging
software-developers

Use when an observed failure, regression, flake, unexpected output, or unknown root cause needs investigation; a known-cause execution-ready fix remains Ralph.

2026-07-27
systematic-debugging
software-developers

Use when an observed failure, regression, flake, unexpected output, or unknown root cause needs investigation; a known-cause execution-ready fix remains Ralph.

2026-07-27
Showing top 8 of 22 collected skills in this repository.
Showing 1 of 1 repositories
All repositories loaded