Menu
Use this skill when editing files in ai/ or .claude/ folders.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | ai-context-documentation |
| description | Use this skill when editing files in ai/ or .claude/ folders. |
When working on ai/ documentation, TODOs, or .claude/ configuration, consult these resources.
The ai/ directory is the pwiz-ai repository (separate from pwiz). Changes to anything under ai/ are committed and pushed directly to pwiz-ai master - no feature branches needed.
Read ai/docs/ai-repository-strategy.md for:
.claude/skills/{skill-name}/SKILL.md
Required frontmatter:
---
name: skill-name
description: When to activate this skill (one sentence)
---
.claude/commands/pw-{command-name}.md
Required frontmatter:
---
description: Brief description of what the command does
---
ai/docs/{topic-name}.md
| Type | Location | Repository |
|---|---|---|
| Skills | .claude/skills/ | pwiz-ai (ai/) |
| Commands | .claude/commands/ | pwiz-ai (ai/) |
| Guides | ai/docs/ | pwiz-ai (ai/) |
| TODOs (active) | ai/todos/active/ | pwiz-ai (ai/) |
| TODOs (completed) | ai/todos/completed/ | pwiz-ai (ai/) |
All documentation in ai/ belongs to the pwiz-ai repository. Commit and push directly to master - no feature branches needed for documentation work.
ALWAYS load when working in pwiz_tools/Osprey (C# port), on maccoss/osprey (Rust), or debugging Osprey-Rust parity issues.
ALWAYS load before git commit, push, or PR - team-specific commit format differs from standard conventions.
ALWAYS load when working on LabKey Server modules (MacCossLabModules, targetedms), in a LabKey enlistment directory, or on GitHub issues/PRs in LabKey repositories.
ALWAYS load when working in pwiz_tools/Skyline, on GitHub issues labeled 'skyline', or TODOs referencing Skyline code.
Invoke when starting an autonomous overnight session ("this is a nighttime autonomous session"). Sets a deep-investigation posture - premium on progress and high-definition findings, expects 5-8 hours of work without check-ins.
ALWAYS load when investigating bugs, failures, or unexpected behavior - ensures root cause analysis before attempting fixes.