project-specificies

Records confirmed project-specific deviations in per-project Markdown notes for future agent sessions.

Updated Aug 4, 2026
One-click install
npx skills add https://github.com/tschallacka/ai-skills --skill project-specificies-tschallacka
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-specificies
Source: https://github.com/tschallacka/ai-skills/tree/main/project-specificies
Command: npx skills add https://github.com/tschallacka/ai-skills --skill project-specificies-tschallacka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Projects accumulate quirks—custom integration wiring, environment constraints, tooling gotchas—that agents rediscover the hard way every session. This Skill captures those confirmed deviations once in a per-project note so future work starts with the facts already loaded instead of re-debugging the same surprises. ## Core Features & Use Cases - Per-project deviation notes: Stores one <project>-deviations.md file per project in the shared skill-data directory (${XDG_CONFIG_HOME:-$HOME/.config}/tsch-ai-skills/), outside the skill install directory so updates never overwrite them. - Load-before-work workflow: Checks for and reads the matching note before investigating project-specific behavior, preventing wrong assumptions. - Evidence-based recording: Only confirmed deviations are written, stated as current facts without investigation narratives, changelogs, or debugging history. - Use Case: A repo's make test writes into /tmp and fails when TMPDIR points at a mounted volume. Record it once; the next session loads the note before running tests and avoids the failure. ## Quick Start Check whether a deviations note exists for this project and load it before debugging, then record any confirmed environment quirk you discover.

Frequently Asked Questions about project-specificies

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I record project-specific quirks for future coding sessions?▼

Create a <project>-deviations.md file in ${XDG_CONFIG_HOME:-$HOME/.config}/tsch-ai-skills/ with frontmatter containing name and description. Add confirmed facts under area-based headings, stated as current behavior without debugging narratives.

What belongs in a project deviations note?▼

Only confirmed deviations from expected project behavior: environment quirks, non-obvious conventions, tooling gotchas, and data limitations. General documentation, changelogs, code style, and behavior matching normal defaults do not belong.

Where are project deviation notes stored?▼

Notes live in the shared skill-data directory at ${XDG_CONFIG_HOME:-$HOME/.config}/tsch-ai-skills/, one file per project. They sit outside the skill's install directory so a skill update or reinstall cannot overwrite them.

When should a deviations note be loaded?▼

Load it when starting work that depends on project-specific behavior, such as implementation, debugging, testing, or tooling. Do not load or create notes for unrelated projects or tasks that follow normal defaults.

Should I document how a bug was fixed in the deviations note?▼

No. Record only the surprising fact as it stands now, not the investigation history or fix narrative. If a bug was fixed, capture the fact that made it possible, not how you discovered it.