0XFF-96/Perth-Agent-Con-Workshop
Skill Claude CodeCodex
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
0XFF-96/Perth-Agent-Con-Workshop
Skill Claude CodeCodex
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.
0XFF-96/Perth-Agent-Con-Workshop
Skill Claude CodeCodex
Use when you have a written implementation plan to execute in a separate session with review checkpoints.
0XFF-96/Perth-Agent-Con-Workshop
Skill Claude CodeCodex
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup.
0XFF-96/Perth-Agent-Con-Workshop
Skill Claude CodeCodex
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.
0XFF-96/Perth-Agent-Con-Workshop
Skill Claude CodeCodex
Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
0XFF-96/Perth-Agent-Con-Workshop
Skill Claude CodeCodex
Use when executing implementation plans with independent tasks in the current session.
0XFF-96/Perth-Agent-Con-Workshop
Skill Claude CodeCodex
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
0XFF-96/Perth-Agent-Con-Workshop
Skill Claude CodeCodex
Use when implementing any feature or bugfix, before writing implementation code.
0XFF-96/Perth-Agent-Con-Workshop
Skill Claude CodeCodex
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback.
0XFF-96/Perth-Agent-Con-Workshop
Skill Claude CodeCodex
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions.
0XFF-96/Perth-Agent-Con-Workshop
Skill Claude CodeCodex
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always.
0XFF-96/Perth-Agent-Con-Workshop
Skill Claude CodeCodex
Use when you have a spec or requirements for a multi-step task, before touching code.
0XFF-96/Perth-Agent-Con-Workshop
Skill Claude CodeCodex
Use when creating new skills, editing existing skills, or verifying skills work before deployment.
0XFF-96/Perth-Agent-Con-Workshop
Skill Claude CodeCodex
Review a pull request with this repo's methodology (CI gate + AI-comment triage + CopilotKit/A2UI domain rubric) and post a single GO/NO-GO verdict comment on the PR. Use when asked to review a PR by number.
0XFF-96/Perth-Agent-Con-Workshop
Skill Claude CodeCodex
Start the AgentCon workshop app (Vite frontend + CopilotKit runtime) and smoke-test that the L2-L4 tabs load and respond. Use when the user wants to run, start, boot, or demo the app, or asks "does it work".
0XFF-96/Perth-Agent-Con-Workshop
Skill Claude CodeCodex
Run this repo's full quality gate (typecheck + tests + build) and report a clear go/no-go. Use before committing or calling work done, or when the user asks to verify, check, or validate their changes.
0XFF-96/Perth-Agent-Con-Workshop
Skill Claude CodeCodex
Show the workshop learner's progress and drive them to the next step via the Makefile-driven WorkMate companion. Use when the user asks where they are in the workshop, what to do next, or to track / tick off progress.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: