How does UFC memory fit into the new skills architecture ?

[smolcompute]

Seems CC is about to have much of the UFC framework backed in soon if Anthropic rolls out their memory tool to CC.
https://docs.claude.com/en/docs/agents-and-tools/tool-use/memory-tool

I mistakenly thought it was already in CC. I assume it will be coming...

[smolcompute]

Speaking of memory, @danielmiessler , I'm confused about what happened to the UFC's context folder in the new version of PAI. The update note mentions it's been replaced by skills ? How so ? Thanks!

[danielmiessler]

The context is in the skills.

…

On Fri, Oct 17, 2025 at 5:36 PM, smol compute < ***@***.*** > wrote: Speaking of memory, @ danielmiessler ( https://github.com/danielmiessler ) , I'm confused about what happened to the UFC's context folder in the new version of PAI. The update note mentions it's been replaced by skills ? How so ? Thanks! — Reply to this email directly, view it on GitHub ( #36 (comment) ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AAAMLXVPKMEINMEP6NJIIIL3YGDSDAVCNFSM6AAAAACJI3IK3OVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINZRGQ3DGMQ ). You are receiving this because you were mentioned. Message ID: <danielmiessler/Personal_AI_Infrastructure/repo-discussions/36/comments/14714632 @ github. com>

[smolcompute]

I've read both Anthropic's documentation and PAI's skills docs and it's not obvious how this works for the UFC. The documentation for the UFC is still based on the old context folder. I use the UFC primarily to give PAI a memory, i.e., context about all aspects of my life. It's not immediately obvious how this fits with the new skills architecture.
I also don't know what this refers to:

Update global context:

Edit your global configuration to include the skill in <available_skills>:

your-new-skill Your description with USE WHEN triggers... user

This goes in Claude's settings.json file ? In the main CLAUDE.md file? I haven't seen this mentioned anywhere in Anthropic's documentation. It seems skills are automatically loaded at session start without needing to add them to any settings / claude.md file.

[evenromo]

I don't remember where I saw it either in one of the commands, hooks or skills. But somewhere there are references to a file "${PAI_DIR}/global/KAI.md" that's probably the that is the "global" file you're questioning. Or am I misunderstanding your question?

[smolcompute]

I think you're correct. I'm still unsure why that's needed though since CC already loads the front matter of each skill at session's start and hence always has a full copy of the available skills. Is this to play nice with Codex and Gemini ?

[danielmiessler]

Right, this is why we just moved to skills natively.

…

On Sun, Oct 19, 2025 at 06:43, smol compute < ***@***.*** > wrote: I think you're correct. I'm still unsure why that's needed though since CC already loads the front matter of each skill at session's start and hence always has a full copy of the available skills. Is this to play nice with Codex and Gemini ? — Reply to this email directly, view it on GitHub ( #36 (reply in thread) ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AAAMLXVNYN2TQNLZBJB4VEL3YOIPDAVCNFSM6AAAAACJI3IK3OVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINZSGE3TGOI ). You are receiving this because you were mentioned. Message ID: <danielmiessler/Personal_AI_Infrastructure/repo-discussions/36/comments/14721739 @ github. com>

[smolcompute]

As of October 19, despite the the user-prompt-submit-hook having been deleted, the UFC documentation still says :

Dynamic Requirements Loading
The UFC system uses the user-prompt-submit-hook to:

Hook Implementation Flow

#!/bin/bash
# user-prompt-submit-hook (simplified)

1. Always load global context

load_global_context "${PAI_DIR}/PAI.md"

2. Analyze user intent

INTENT=$(analyze_intent "$USER_PROMPT")

3. Load matching skill

case "$INTENT" in
  "website")
    invoke_skill "website"
    ;;
  "research")
    invoke_skill "research"
    ;;
  "development")
    invoke_skill "development"
    ;;
esac

[danielmiessler]

About to fix it. Hopefully for a long time.

…

On Sun, Oct 19, 2025 at 12:49 PM, smol compute < ***@***.*** > wrote: As of October 19 , despite the the user-prompt-submit-hook having been deleted, the UFC documentation still says : Dynamic Requirements Loading The UFC system uses the user-prompt-submit-hook to: Hook Implementation Flow #!/bin/bash # user-prompt-submit-hook (simplified) ***************************** 1. Always load global context ***************************** load_global_context "${PAI_DIR}/ PAI. md ( http://pai.md/ ) " ********************** 2. Analyze user intent ********************** INTENT=$(analyze_intent "$USER_PROMPT") ********************** 3. Load matching skill ********************** case "$INTENT" in "website") invoke_skill "website" ;; "research") invoke_skill "research" ;; "development") invoke_skill "development" ;; esac — Reply to this email directly, view it on GitHub ( #36 (reply in thread) ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AAAMLXX3K6Y3B4TUEJQ3UYL3YPTNRAVCNFSM6AAAAACJI3IK3OVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINZSGMZTCNI ). You are receiving this because you were mentioned. Message ID: <danielmiessler/Personal_AI_Infrastructure/repo-discussions/36/comments/14723315 @ github. com>

[Wayku7]

The way I see that, I use the telos file as a UFC file system to keep everything as organized as possible.
My telos file is split between 15 files and directory structure, with documentation in every part of it.
With the main one at the upper level for the parts that are more static.

[danielmiessler]

Mine is multi-file now too, and it has a skill so I can add to it, query it, etc. I don't actually create a unified one manually; I have the system do that dynamically when needed during a skill invocation.

…

On Mon, Oct 27, 2025 at 1:31 AM, Jack < ***@***.*** > wrote: The way I see that, I use the telos file as a UFC file system to keep everything as organized as possible. My telos file is split between 15 files and directory structure, with documentation in every part of it. With the main one at the upper level for the parts that are more static. — Reply to this email directly, view it on GitHub ( #36 (comment) ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AAAMLXSJ2QZMSGPL7W2SS2L3ZVRWPAVCNFSM6AAAAACJI3IK3OVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINZYG44TAMY ). You are receiving this because you were mentioned. Message ID: <danielmiessler/Personal_AI_Infrastructure/repo-discussions/36/comments/14787903 @ github. com>

[Wayku7]

The breakdown of mine was assisted by CC Sonnet 4.5 with my system-architect assitant. I was in the loop a few time to be sure it undertand what I had in mine and that I understand what it was proposing to me.

Its not juste a file ou multiple file anymore, its a file structure to where I can place the related documentation.
Like my projetc or sub-project documentation.

I am in the process of migrating my PAI from the hook to skill orchestration.
After ill convert my Telos-integrator prompt into a skill.

[smolcompute]

Mine is multi-file now too, and it has a skill so I can add to it, query it, etc. I don't actually create a unified one manually; I have the system do that dynamically when needed during a skill invocation.

@danielmiessler I hope you update the article on PAI on your website with your current organization. A concrete example of your setup, with file structure, etc., would be very helpful.