with one click
jujo
jujo contains 4 collected skills from JYC11, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
Analyze an existing codebase to extract repeating patterns and auto-generate jujo generator templates from them. Turns "how we already do it" into reusable generators. Use when: the user says "analyze patterns", "extract templates", "create generator from existing", "reverse engineer templates", "make a generator for this pattern", "automate this boilerplate", or wants to turn repeated code structures into jujo generators. Triggers on: "analyze pattern", "extract template", "create generator from", "reverse engineer", "automate boilerplate", "find patterns", "what repeats".
Use the jujo CLI to generate code from template sets. Follow the four-phase agent protocol: discover generators, read schemas, preview with dry-run, then execute. After generation, read the manifest to find AI customization markers and fill them in. Triggers on: "generate module", "scaffold", "jujo generate", "add module", "create entity", "new endpoint", "codegen", "stamp out", "generate boilerplate".
Run manual QA against the jujo CLI binary using a real temp project. Build the release binary, create an isolated test directory, execute commands, capture stdout/stderr/exit codes, and produce a structured results file in the project's .qa/ folder. Use when: the user asks to "manual test", "manual QA", "QA the CLI", "smoke test", "exercise the binary", "end-to-end QA", or wants to verify CLI behavior outside of automated tests. Triggers on: "manual qa", "manual test", "smoke test", "QA", "exercise the CLI", "test the binary", "end-to-end test the CLI".
Guide for writing tests following the project's layered test standards. Use when the user says "write tests", "add tests", "test strategy", "what tests to write", "test this module", "where should this test go", or is deciding which test layer to use.