retz8

Claude Code ecosystem expertise. Modules: CLI tool (setup, slash commands, MCP servers, hooks, plugins, CI/CD), extensibility (agents, skills, output styles creation), CLAUDE.md (project instructions, optimization). Actions: configure, troubleshoot, create, deploy, integrate, optimize Claude Code. Keywords: Claude Code, Anthropic, CLI tool, slash command, MCP server, Agent Skill, hook, plugin, CI/CD, enterprise, CLAUDE.md, agentic coding, agent, skill, output-style, SKILL.md, subagent, Task tool, project instructions, token optimization. Use when: learning Claude Code features, configuring settings, creating skills/agents/hooks, setting up MCP servers, troubleshooting issues, CI/CD integration, initializing or optimizing CLAUDE.md files.

Generates a hotfix track definition document for the jioh agent workflow system. Use when asked to create a hotfix track for a small, out-of-band task between phases. Produces a file under docs/tasks/ following the hotfix-{name}.md format and updates README.md.

Create structured implementation plans for features, refactoring, upgrades, design, architecture, or infrastructure. Generates machine-readable, deterministic plans for autonomous execution by AI agents or humans. Domains: software implementation, package upgrades, system refactoring, architecture design, infrastructure changes. Actions: create, generate, structure implementation plans. Keywords: implementation plan, technical spec, feature spec, upgrade plan, refactoring plan, architecture spec, infrastructure plan, design doc. Use when: planning new features, refactoring existing code, upgrading packages, designing architecture, documenting infrastructure changes.

Snippet newsletter Skill A — Phase 2. Interactive. Reads the latest candidates file written by /discover-oss-candidates, presents repo options to the human, writes 3 selection files (one per language), increments the issue counter. Run Saturday morning after reviewing the Friday night candidates file.

Snippet newsletter Skill A — Phase 1. Fully automated. Discovers trending OSS repos for Python, JS/TS, and C/C++, validates all repos via GitHub API, and writes a single candidates file for human review. Reads issue number from snippet/current-issue.txt. No human input required. Run on Friday nights. After reviewing the output, run /discover-oss-candidates-select to make selections.

Snippet newsletter Skill B — Phase 2. Interactive. Reads the latest snippet candidate files written by /find-snippet-candidates, presents ranked candidates to the human (all 3 languages at once), verifies selected snippet URLs via GitHub API, and appends Snippet Selections to the corresponding selection files. Run Sunday morning after reviewing the Saturday night candidate files.

Snippet newsletter Skill B — Phase 1. Fully automated. Finds the 3 latest selection files written by Skill A, spawns 6 parallel snippet-repo-explorer sub-agents (2 per language) via GitHub API, and writes 3 snippet candidate files for human review. No human input required. Run on Saturday nights. After reviewing, run /find-snippet-candidates-select to make selections.

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

Divide a specced pastiche task into sub-task GitHub issues with autonomy and dependency labels, mirror them into `_dev/TODO.md`, and update the parent issue. Use after `grill-to-spec` completes for a task, or when the user invokes `/divide-task`.

Convert a completed grill-me session into a spec file. Captures only the task and the decisions locked during grilling — no implementation details, no invented decisions. Use when the user asks to write a spec from a grill, save grill decisions, or after a grill-me session concludes.

Pick up or resume a task from `_dev/TODO.md` — marks `[WIP]`, creates or switches to the task's feature branch, rebases with main. Use when the user invokes `/pick-up-task` or asks to grab/resume a pastiche task.

Rebase the current pastiche feature branch onto main to absorb hotfixes. Use when the user invokes `/rebase-feat-with-main`, when resuming a task, or after a hotfix lands on main while a feature branch is in flight.

Ship a pastiche release — version bump, plugin build, CHANGELOG entry, release commit, tag, GitHub Release, milestone close. Use when the user invokes `/release-pastiche` after a TODO group's final feat→main merge. Human-triggered only; never run from an automated routine.

Use when bootstrapping pastiche for first-time adoption (post-`/pastiche-init`) — fills `KNOWLEDGE.md` and seeds `[GENERAL]` `WISDOM.md` rules section by section. Resumable across sessions; re-invoke to continue.

Use when bootstrapping pastiche in a frontend repo for the first time — scaffolds `pastiche/{config.yaml, FACT.md, KNOWLEDGE.md, WISDOM.md}` and extracts FACT. Single-use; refuses to overwrite. Curation happens later via `/pastiche-setup`.

Use to re-validate `pastiche/{config.yaml, FACT.md, KNOWLEDGE.md, WISDOM.md}` after hand-editing any of them outside the mutator skills. Thin manual wrapper around the bundled lint script; reports drift and schema violations.