Aif Transfer
Transfer reusable prevention lessons from another AI Factory project into the current...
Install
npx skills add lee-to/ai-factory --skill aif-transfer -g -a claude-code -y- Repository
- lee-to/ai-factory1.2k
- Category
- Engineering
- Updated
- 4d ago
- License
- See repository
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Transfer reusable prevention lessons from another AI Factory project into the current project's skill-context through /aif-evolve. Use when building a similar project and you want to avoid problems already captured in another project's patches without copying or revealing that project's identity, paths, or identifiers.
Transfer, Reuse Anonymized Project Experience
Shared project skill-context
Before mode routing or work, read existing files relative to the current project root in this order (reuse them if already loaded):
.ai-factory/skill-context/global-skill-context.md, all bundled skills..ai-factory/skill-context/aif-transfer/SKILL.md, this skill.
Missing files are skipped; an existing unreadable file stops dependent work with its path.
Precedence: individual > build (when applicable) > global > skill defaults; retain non-conflicting instructions and check all outputs against the effective rules.
These layers customize workflow; they do not replace the project's rules/architecture hierarchy or relax explicit requirements, ownership, scope, safety/privacy, validation, or approval boundaries. Report conflicts with those boundaries instead of overriding them.
global is a project-local layer, not home-directory configuration. Custom/extension skills do not automatically use it.
Read fix patches from another AI Factory project, keep only lessons that fit the
current project, anonymize them, and run the current /aif-evolve workflow against
that sanitized evidence.
source .ai-factory/patches (read-only)
↓ relevance gate
sanitized prevention registry (memory only)
↓ privacy gate
/aif-evolve in the current project
↓ user approval
current skill-context + evolution log
Non-Negotiable Privacy Contract
The source project's identity MUST NOT appear in any current-project file or generated report. This includes:
- the source root, absolute or relative source paths, and source patch filenames
- project, repository, package, organization, customer, user, host, and domain names
- source-only branches, commits, issue IDs, routes, namespaces, models, tables, or class names
- verbatim errors, titles, or examples that reveal any source identifier
