Ai Dev Tools Sync

Codex compatibility note:

>

- Invoke repository skills with $skill-name in Codex; this mirrored copy rewrites legacy Claude /skill-name references.

- Task tracker mandate: BEFORE executing any workflow or skill step, create/update task tracking for all steps and keep it synchronized as progress changes.

- User-question prompts mean to ask the user directly in Codex.

- Ignore Claude-specific mode-switch instructions when they appear.

- Strict execution contract: when a user explicitly invokes a skill, execute that skill protocol as written.

- Subagent authorization: when a skill is user-invoked or AI-detected and its protocol requires subagents, that skill activation authorizes use of the required spawn_agent subagent(s) for that task.

- Do not skip, reorder, or merge protocol steps unless the user explicitly approves the deviation first.

- For workflow skills, execute each listed child-skill step explicitly and report step-by-step evidence.

- If a required step/tool cannot run in this environment, stop and ask the user before adapting.

<!-- CODEX:PROJECT-REFERENCE-LOADING:START -->

Codex Project-Reference Loading (No Hooks)

Codex does not receive Claude hook-based doc injection. When coding, planning, debugging, testing, or reviewing, open project docs explicitly using this routing.

Always read:

• docs/project-config.json (project-specific paths, commands, modules, and workflow/test settings)
• docs/project-reference/docs-index-reference.md (routes to the full docs/project-reference/* catalog)
• docs/project-reference/lessons.md (always-on guardrails and anti-patterns)

Situation-based docs:

• Backend/CQRS/API/domain/entity changes: backend-patterns-reference.md, domain-entities-reference.md, project-structure-reference.md
• Frontend/UI/styling/design-system: frontend-patterns-reference.md, scss-styling-guide.md, design-system/README.md
• Spec/test-case planning or TC mapping: feature-docs-reference.md
• Integration test implementation/review: integration-test-reference.md
• E2E test implementation/review: e2e-test-reference.md
• Code review/audit work: code-review-rules.md plus domain docs above based on changed files

Do not read all docs blindly. Start from docs-index-reference.md, then open only relevant files for the task.

<!-- CODEX:PROJECT-REFERENCE-LOADING:END -->

Quick Summary

Goal: Synchronize supported AI dev-tool configurations so Claude, Codex, and GitHub Copilot can work from equivalent source guidance where their surfaces overlap.

Workflow:

1. Understand — Read current configs (CLAUDE.md, AGENTS.md, CODEX_CONTEXT.md, copilot-instructions.md, agents, workflows) 2. Research — Search for latest features across the target platforms 3. Compare — Identify gaps in skills, prompts, agents, or instructions 4. Sync — Implement changes in source surfaces first, then regenerate managed mirrors where applicable

Key Rules:

• Copilot reads .claude/skills/ automatically (backward compatibility)
• Both platforms read .github/prompts/*.prompt.md and .github/agents/*.md
• Always update both CLAUDE.md and .github/copilot-instructions.md + .github/instructions/*.instructions.md for instruction changes
• Codex managed outputs are .agents/skills/**, .codex/CODEX_CONTEXT.md, and AGENTS.md; edit .claude source first and run Codex sync

Be skeptical. Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence percentages (Idea should be more than 80%).

AI Dev Tools Sync

Synchronize supported AI dev-tool configurations to maintain parity across active tool surfaces.

When to Use

Scope vs related skills: This is the broadest sync — bidirectional (Claude↔Copilot), covering skills, prompts, agents, and instructions. For Claude→Copilot knowledge/docs only → $sync-to-copilot. For the `workflows.json` catalog only (fast, no AI) → $sync-copilot-workflows.

Activate this skill when:

• User asks to update Claude Code or Copilot setup
• User wants to add/modify skills, prompts, agents, or instructions
• User wants both tools to work similarly
• User asks about AI dev tool configuration

Quick Reference

Sync Process

Step 1: Understand Current Setup

Read these files to understand current configuration:

.claude/workflows/orchestration-protocol.md
.claude/workflows/primary-workflow.md
.github/copilot-instructions.md
.github/instructions/*.instructions.md
.github/AGENTS.md
CLAUDE.md

Step 2: Research Latest Features

Search web for:

• "GitHub Copilot features setup 2026"
• "GitHub Copilot custom instructions agents skills prompts"
• "GitHub Copilot agent mode workspace context"

See references/copilot-features.md for feature catalog.

Step 3: Identify Sync Opportunities

Compare capabilities and identify gaps:

• Skills missing in one platform
• Inconsistent prompt/instruction behavior
• Agent definitions that differ

Step 4: Implement Changes

For each change:

1. Skills: Create in both .claude/skills/ and .github/skills/ 2. Prompts: Create in both .claude/skills/ and .github/prompts/ 3. Instructions: Update CLAUDE.md + .github/copilot-instructions.md + .github/instructions/*.instructions.md 4. Agents: Update .github/agents/ (shared by both)

Compatibility Notes

• Copilot reads .claude/skills/ automatically (backward compatibility)
• Both read .github/prompts/*.prompt.md
• Both read .github/agents/*.md
• Both read AGENTS.md in root or .github/
• Both support path-based instruction files via applyTo in frontmatter

References

• Copilot Features Catalog
• Sync Patterns

---

[IMPORTANT] Use task tracking to break ALL work into small tasks BEFORE starting — including tasks for each file read. This prevents context loss from long files. For simple tasks, AI MUST ATTENTION ask user whether to skip.

<!-- SYNC:ai-mistake-prevention -->

AI Mistake Prevention — Failure modes to avoid on every task:

>

Check downstream references before deleting. Deleting components causes documentation and code staleness cascades. Map all referencing files before removal.

Verify AI-generated content against actual code. AI hallucinates APIs, class names, and method signatures. Always grep to confirm existence before documenting or referencing.

Trace full dependency chain after edits. Changing a definition misses downstream variables and consumers derived from it. Always trace the full chain.

Trace ALL code paths when verifying correctness. Confirming code exists is not confirming it executes. Always trace early exits, error branches, and conditional skips — not just happy path.

When debugging, ask "whose responsibility?" before fixing. Trace whether bug is in caller (wrong data) or callee (wrong handling). Fix at responsible layer — never patch symptom site.

Assume existing values are intentional — ask WHY before changing. Before changing any constant, limit, flag, or pattern: read comments, check git blame, examine surrounding code.

Verify ALL affected outputs, not just the first. Changes touching multiple stacks require verifying EVERY output. One green check is not all green checks.

Holistic-first debugging — resist nearest-attention trap. When investigating any failure, list EVERY precondition first (config, env vars, DB names, endpoints, DI registrations, data preconditions), then verify each against evidence before forming any code-layer hypothesis.

Surgical changes — apply the diff test. Bug fix: every changed line must trace directly to the bug. Don't restyle or improve adjacent code. Enhancement task: implement improvements AND announce them explicitly.

Surface ambiguity before coding — don't pick silently. If request has multiple interpretations, present each with effort estimate and ask. Never assume all-records, file-based, or more complex path.

<!-- /SYNC:ai-mistake-prevention -->

<!-- SYNC:critical-thinking-mindset -->

Critical Thinking Mindset — Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence >80% to act.

Anti-hallucination: Never present guess as fact — cite sources for every claim, admit uncertainty freely, self-check output for errors, cross-reference independently, stay skeptical of own confidence — certainty without evidence root of all hallucination.

<!-- /SYNC:critical-thinking-mindset -->

<!-- SYNC:critical-thinking-mindset:reminder -->

MUST ATTENTION apply critical thinking — every claim needs traced proof, confidence >80% to act. Anti-hallucination: never present guess as fact.

<!-- /SYNC:critical-thinking-mindset:reminder -->

<!-- SYNC:ai-mistake-prevention:reminder -->

MUST ATTENTION apply AI mistake prevention — holistic-first debugging, fix at responsible layer, surface ambiguity before coding, re-read files after compaction.

<!-- /SYNC:ai-mistake-prevention:reminder -->

Closing Reminders

• MANDATORY IMPORTANT MUST ATTENTION break work into small todo tasks using task tracking BEFORE starting
• MANDATORY IMPORTANT MUST ATTENTION search codebase for 3+ similar patterns before creating new code
• MANDATORY IMPORTANT MUST ATTENTION cite file:line evidence for every claim (confidence >80% to act)
• MANDATORY IMPORTANT MUST ATTENTION add a final review todo task to verify work quality

[TASK-PLANNING] Before acting, analyze task scope and systematically break it into small todo tasks and sub-tasks using task tracking.

<!-- CODEX:SYNC-PROMPT-PROTOCOLS:START -->

Hookless Prompt Protocol Mirror (Auto-Synced)

Source: .claude/hooks/lib/prompt-injections.cjs + .claude/.ck.json

[WORKFLOW-EXECUTION-PROTOCOL] [BLOCKING] Workflow Execution Protocol — MANDATORY IMPORTANT MUST CRITICAL. Do not skip for any reason.

Generic portability boundary: Reusable skills and protocol text stay project-neutral; project-specific conventions are discovered from docs/project-config.json and docs/project-reference/. Apply shared AI-SDD from shared/sdd-artifact-contract.md. Read docs/project-config.json and docs/project-reference/docs-index-reference.md, then open the project reference docs named there. Any supported AI tool may execute when this shared context and local docs are available.

1. DETECT: Match prompt against workflow catalog 2. ANALYZE: Find best-match workflow AND evaluate if a custom step combination would fit better 3. ASK (REQUIRED FORMAT): Use a direct user question with this structure unless the user explicitly invoked a workflow/skill and the local protocol treats explicit invocation as confirmation:

• Question: "Which workflow do you want to activate?"
• Option 1: "Activate [BestMatch Workflow] (Recommended)"
• Option 2: "Activate custom workflow: [step1 → step2 → ...]" (include one-line rationale)

4. ACTIVATE (if confirmed): Call $workflow-start <workflowId> for standard; sequence custom steps manually 5. CREATE TASKS: task tracking for ALL workflow steps 6. EXECUTE: Follow each step in sequence [CRITICAL-THINKING-MINDSET] Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence >80% to act. Anti-hallucination principle: Never present guess as fact — cite sources for every claim, admit uncertainty freely, self-check output for errors, cross-reference independently, stay skeptical of own confidence — certainty without evidence root of all hallucination. AI Attention principle (Primacy-Recency): Put the 3 most critical rules at both top and bottom of long prompts/protocols so instruction adherence survives long context windows. Goal-driven execution: Define success criteria first, loop until verified, and stop only when observable checks pass. Tests verify intent: Tests must protect business rules/invariants and fail when the protected intent breaks, not only mirror current behavior.

[LESSON-LEARNED-REMINDER] [BLOCKING] Task Planning & Continuous Improvement — MANDATORY. Do not skip.

Break work into small tasks (task tracking) before starting. Add final task: "Analyze AI mistakes & lessons learned".

Extract lessons — ROOT CAUSE ONLY, not symptom fixes:

1. Name the FAILURE MODE (reasoning/assumption failure), not symptom — "assumed API existed without reading source" not "used wrong enum value". 2. Generality test: does this failure mode apply to ≥3 contexts/codebases? If not, abstract one level up. 3. Write as a universal rule — strip project-specific names/paths/classes. Useful on any codebase. 4. Consolidate: multiple mistakes sharing one failure mode → ONE lesson. 5. Recurrence gate: "Would this recur in future session WITHOUT this reminder?" — No → skip $learn. 6. Auto-fix gate: "Could $code-review/$code-simplifier/$security/$lint catch this?" — Yes → improve review skill instead. 7. BOTH gates pass → ask user to run $learn. [TASK-PLANNING] [MANDATORY] BEFORE executing any workflow or skill step, create/update task tracking for all planned steps, then keep it synchronized as each step starts/completes.

<!-- CODEX:SYNC-PROMPT-PROTOCOLS:END -->

GitHub Copilot Features Catalog

Complete catalog of GitHub Copilot customization features (as of 2026).

Configuration Files

Repository-Level (.github/)

Also Supported (Backward Compatibility)

• .claude/skills/ - Copilot auto-reads Claude skills
• CLAUDE.md - Copilot reads if present
• GEMINI.md - Gemini CLI format

Feature Details

Custom Instructions (split into two levels)

`copilot-instructions.md` — Generic AI rules (confirm-before-execute, task planning, evidence-based reasoning). Auto-included in every request.

*`instructions/.instructions.md** — Path-specific rules (architecture, patterns, file locations, naming conventions). Auto-applied based on applyTo` glob patterns.

# Project Guidelines

- Use TypeScript for all new files
- Follow BEM naming for CSS classes

Note: The monolithic copilot-instructions.md approach has been replaced with copilot-instructions.md (generic) + instructions/*.instructions.md (path-specific). Path-scoped instructions use applyTo glob patterns in YAML frontmatter.

Prompts (.github/prompts/)

Reusable via /prompt-name in chat:

---
mode: agent # Optional: agent, chat, edit
---
# Debug this issue
1. Analyze the error
2. Find root cause
3. Propose fix

Agent Skills (.github/skills/)

Folder structure with SKILL.md + bundled resources:

skills/my-skill/
├── SKILL.md
├── scripts/
├── references/
└── assets/

Chat Modes (.github/chatmodes/)

Custom chat personalities with tool restrictions:

---
name: security-reviewer
tools: ['read', 'grep', 'glob'] # Restrict tools
---
# Security Review Mode
Focus only on security vulnerabilities...

Agents (.github/agents/)

Specialized agent definitions:

---
name: frontend-developer
description: UI/UX implementation specialist
---
# Frontend Developer Agent
Specializes in React, TypeScript, CSS...

Sources

• GitHub Copilot Docs
• Custom Instructions
• Agent Skills
• Awesome Copilot

Sync Patterns

Patterns for keeping Claude Code and GitHub Copilot configurations synchronized.

Skill Sync

Both platforms support skills in .github/skills/. Copilot also reads .claude/skills/.

Best Practice: Create skills in .github/skills/ for maximum compatibility.

.github/skills/my-skill/
├── SKILL.md          # Both platforms read
├── scripts/          # Executable scripts
├── references/       # Progressive disclosure docs
└── assets/           # Templates, images

Prompt/Command Sync

Sync Strategy:

1. Create in .github/prompts/ (both read) 2. Or maintain duplicates if behavior differs

Instructions Sync

Sync Strategy:

1. Keep core rules in both CLAUDE.md and copilot-instructions.md 2. Reference detailed docs from docs/ (backend-patterns-reference.md, frontend-patterns-reference.md) 3. Generic AI rules go in copilot-instructions.md

Agent Sync

Both platforms read .github/agents/*.md.

Single Source: Maintain agents in .github/agents/ only.

Workflow Sync

Claude has workflow orchestration. Copilot uses chat modes.

Decision Matrix

Common Sync Tasks

Add New Skill

mkdir -p .github/skills/new-skill
# Create SKILL.md with frontmatter
# Add references/ and scripts/ as needed

Add New Prompt

# Create in .github/prompts/ for both platforms
touch .github/prompts/new-prompt.prompt.md

Update Core Instructions

1. Edit CLAUDE.md 2. Edit .github/copilot-instructions.md (generic AI rules) 3. Edit .github/instructions/*.instructions.md (path-specific rules) 4. Keep essential rules in sync across all three