Jiri's personal monorepo of AI-tool instructions: rules, skills, and slash commands consumed by Claude Code, Copilot CLI, Gemini CLI, Cursor, and any other agent that can read markdown.

Everything here is tool-agnostic where possible. Each AI tool picks up what it needs through its own loading mechanism (Claude Code via the sync hook, Cursor via @file references, Gemini CLI via its commands directory, etc.).

A SessionStart hook symlinks every skills/*/ folder into ~/.claude/skills/, so skills appear automatically inside Claude Code at every session start — no manual install step.

The canonical hook script lives in this repo at skills/setup-skills-autorefresh/scripts/sync-skills.js. It syncs whatever source folder is passed to it as an argument (and prunes symlinks for skills you've removed). Register it on a machine with the bundled setup-skills-autorefresh skill, which bakes the folder into the hook command in ~/.claude/settings.json:

bash skills/setup-skills-autorefresh/scripts/install.sh ~/instructions/skills

• Copilot CLI uses a parallel script at ~/.copilot/hooks/sync-skills.js that copies (not symlinks, github/copilot-cli#1021) skills into ~/.copilot/skills/.

The hook script is the source of truth for the sync behaviour — read it directly if you need to debug.

Three always-apply files under rules/. Each carries type: "always_apply" frontmatter so AI tools that respect that convention load them on every interaction.

• rules/general.md — core principles, coding standards, testing (TDD mandatory), restrictions, file-length limits, writing style, git commit format.
• rules/builder.md — defaults for spinning up new applications (tech stack picks, scaffolding flow, verification protocol).
• rules/design.md — frontend design thinking and aesthetics guidelines (originally from the Anthropic frontend-design plugin).

CLAUDE.md mandates rules/general.md is loaded first, before anything else.

Each skill is a directory under skills/ containing a SKILL.md with name, description, and (optional) metadata frontmatter, followed by the skill body. See the agentskills.io spec for the format. The table below lists every skill in the repo — keep it in sync when you add, remove, or rename one. Each skill name links to its SKILL.md; new rows should link the name to skills/<name>/SKILL.md the same way.

The Depends on column lists other skills in this repo that the skill invokes or requires to function (— if none). It is mandatory: every row must declare its dependencies. A skill that only points the reader to another skill ("use X instead") or is synced from an upstream repo does not "depend on" it — leave the cell —.

(Inside Claude Code you may also see skills loaded from other sources; this table covers the skills defined in this repo — ls skills/.)

The four team-* skills (an agent dev team — a writer, a reviewer, a tester, and a team-ship lead that runs them) are adapted from @zodchiii's post on X.

TOML slash commands under gemini-cli/commands/. Format:

description = "One-line description shown in /help"
prompt = """
Your prompt body. Use {{args}} where the user's input should be interpolated.
"""

Current commands: create-prd, feature-request, generate-changelog, process-task-list, summarise.

Gemini CLI reads from its own config path — symlink or copy this directory there to wire them up.

The original PRD → tasks → process pipeline this repo started as. Still usable as standalone prompts when you want a structured feature-development flow with manual review gates.

1. create-prd.md — interview-driven PRD generation. Output: _prds/prd-[feature-name].md.
2. generate-tasks.md — break the PRD into parent tasks, then sub-tasks (with a confirmation gate between them). Output: _tasks/tasks-[name].md.
3. process-task-list.md — instructs the AI to work one sub-task at a time, waiting for approval, running tests, committing per parent task.
4. feature-request.md — alternative entry point: skip the PRD and go straight from a feature request to a task list.

Usage in Claude Code / Cursor: reference the file with @create-prd.md (or your tool's equivalent) and let it drive.

Video demo of the original workflow on Claire Vo's "How I AI" podcast.

Personal repo, but PRs welcome if something here is genuinely useful elsewhere. To add:

• A skill: create skills/<name>/SKILL.md following the agentskills.io spec. It will be picked up by the sync hook on next session start. Add a matching row to the Skills table above, linking the name to skills/<name>/SKILL.md, and fill the Depends on cell — list every other repo skill this one invokes or requires, or — if it is self-contained.
• A rule: add rules/<name>.md with type: "always_apply" frontmatter.
• A Gemini command: add gemini-cli/commands/<name>.toml. Add it to the Current commands list above.

Universality requirement: anything added here must be reusable by any reader — no personal data, secrets, employer names, internal URLs, or hardcoded identities. Full policy: rules/universality.md. After cloning, activate the pre-commit scanner once: bash scripts/install-hooks.sh.

Log notable changes in changelog.md using the existing YYYYMMDDTHHMM — Title format.