Tier 1: Session Memory
Claude Code's native projects/ directory provides 30-day transcript retention. Every conversation is automatically saved. This is the raw material.
20 juil.
835 articles
Claude Code's native projects/ directory provides 30-day transcript retention. Every conversation is automatically saved. This is the raw material.
Different tasks need different specialists. PAI uses a three-tier agent model: TierWhat It IsExampleVoice?Task SubagentsBuilt into Claude CodeEngineer, Architect, Explore, QATesterNoNamed AgentsPersistent identities with backstoriesSerena (Architect), Marcus (Engineer), Rook (Pentester)Yes (ElevenLabs)Custom AgentsDynamic composition from 28 personality traits"Create 5 security researchers"Yes Named agents have their own ElevenLabs voices. When five agents run in parallel, I can hear which one i
The Kai CLI wraps Claude Code with voice notifications. When I run a task and walk away, I hear "Kai starting: Working on research" from across the room. When it finishes, I hear the summary. Every agent has a unique ElevenLabs voice. The Algorithm announces each phase as it executes. This transforms asynchronous work into ambient awareness — I don't have to be staring at a screen to know what's happening. For some people, voice will be the primary interface, not just notifications. They'll talk
He's from the distant future and genderless, but I mostly refer to him as a him. I've named my entire personalized system Kai. Kai is my Digital Assistant that will always be with me, and he is my instance of PAI. Think of it this way: PAI is the architecture—the blueprint for building a Personal AI system. Kai is MY implementation of that architecture, customized with MY knowledge, MY processes, MY domain expertise. He runs on Claude Code today, but the platform doesn't define him—the seven com
Creating a skill is straightforward: Create the directory: ~/.claude/skills/YourSkill/Define triggers in SKILL.md: USE WHEN [keyword patterns]Add workflows: Step-by-step procedures for common operationsBuild CLI tools: TypeScript utilities for deterministic tasks That's it. Claude Code loads all skills into its system prompt at startup. When your request matches a skill's triggers, it routes automatically.
Here's what I find fascinating: PAI, Claude Code, OpenCode, MoltBot—they're all arriving at the same patterns independently. Skills. Hooks. Memory. Agent orchestration. Context priming. This convergence tells us these aren't arbitrary design choices. This is what the architecture of a Personal AI system actually looks like. The seven components aren't my opinion. They're what everyone keeps rediscovering. The question isn't whether these components are right. It's how quickly we can mature each
🤖 He's from the distant future and genderless, but I mostly refer to him as a him. I've named my entire personalized system Kai. Kai isn't a different AI model or a fork of Claude Code. Kai IS Claude Code—but completely personalized for me. Think of it this way: Claude Code is like macOS or Linux—incredibly powerful out of the box. But just like you customize your operating system with YOUR apps, YOUR shortcuts, YOUR workflows, Kai is Claude Code customized with MY knowledge, MY processes, MY d
🎯 This is THE MOST IMPORTANT part of the entire system. If you take away one thing from this entire post, let it be this: Skills are how you transform Claude Code from a general-purpose assistant into YOUR domain expert. You don't need to fine-tune models. You need to build Skills.
Creating a skill is straightforward: Create the directory structure:~/.claude/Skills/YourSkill/ ├── SKILL.md # Routing and domain knowledge ├── Workflows/ # Step-by-step procedures └── Tools/ # CLI scripts1234Define when to use it in SKILL.md:markdown--- name: YourSkill description: What it does. USE WHEN [trigger phrases] ---1234Create workflows for common operationsBuild CLI tools for deterministic tasksDocument with examples That's it. Now Claude Code knows YOUR
So the umbrella of everything I'm gonna talk about today is what I call a Personal AI Infrastructure (PAI), which is PAI for an acronym. Everyone likes pie. It's also one syllable, which I think is an advantage. But here's what makes PAI v2 different from what came before: This isn't just a collection of prompts and tools anymore. PAI v2 is about taking Claude Code—which is already incredible—and personalizing it into YOUR cognitive operating system. Think of Claude Code as the foundation, like
The best prompt engineering is building a system that doesn't need perfect prompts. Everyone's obsessed with prompt engineering. "How do I write the perfect prompt?" "What's the magic phrase that makes GPT-4 work better?" The real power is in building a system that gives YOUR AI the context, tools, and structure to understand what you actually want, even when your prompts are messy. Instead of spending 20 minutes crafting the perfect research prompt every time, you build a Research skill once th
📁 Context lives in Skills, not a separate directory. Context isn't stored in a separate "context" directory anymore. Context IS the Skills. Each Skill contains its own knowledge files: ~/.claude/Skills/Blogging/ → Blog writing standards, style guides~/.claude/Skills/Research/ → Research methodology files~/.claude/Skills/Art/ → Visual aesthetic guidelines All Skills are pre-loaded into Claude Code's system prompt at startup. When you make a request, the routing system matches it to the appropria
🪝 Hooks are the nervous system—they connect everything automatically. We've covered Skills (WHAT to do), Context (WHAT to know), and History (WHAT to remember). Now let's talk about WHEN things happen automatically. The Hook System makes your personalized Claude Code reactive.
SessionStart Hook (~/.claude/hooks/session-start/): typescript// When session starts: // 1. Load CORE context (identity, principles, contacts) // 2. Check for active tasks from previous sessions // 3. Initialize observability tracking // 4. Set up voice server connection12345 Every time you start Claude Code, this runs automatically. You don't ask for it. It just happens. Stop Hook (~/.claude/hooks/stop/): typescript// When session ends: // 1. Extract 🎯 COMPLETED message from final response //
Kai est un outil CLI personnalisé qui intègre Claude Code avec des notifications vocales et une gestion de contexte. Il offre plusieurs modes d'utilisation (interactif, requête unique, silencieux) et s'exécute en TypeScript/Bun avec des outils configurables. Les notifications vocales créent une boucle de retour naturelle permettant une sensibilisation ambiante du travail asynchrone.
json{ "mcpServers": { "website-analyzer": { "url": "https://mcp-website-analyzer.YOUR-SUBDOMAIN.workers.dev", "description": "Analyzes websites and extracts key information" } } }12345678
Once connected, you can ask your AI assistant to: "Use httpx to check what technology stack danielmiessler.com uses""Scan these domains for me: example.com, test.com""What security headers does github.com have?" The AI will automatically use the MCP server tools to fetch this information.
AI-powered browsers and assistants are designed to read and act on web content on a user’s behalf. This creates a broader attack surface for prompt injection, where malicious instructions are embedded in otherwise normal content (for example, a calendar invite, email, or document). We’ve reviewed an attack scenario that demonstrates how an AI assistant can be influenced by untrusted content to navigate the web and attempt actions a user could perform at the keyboard. If the 1Password browser ext
You may be affected if all of the following apply: You use an AI-powered browser or AI assistant that can autonomously navigate and interact with web pages.The AI assistant is able to read or act on untrusted content that comes from outside your direct control, such as emails, calendar invitations, shared documents, or web pages.Your 1Password browser extension is unlocked while the AI assistant is in use.
🪝 Hooks are the nervous system—they connect everything automatically. We've covered Skills (WHAT to do), Context (WHAT to know), and History (WHAT to remember). Now let's talk about WHEN things happen automatically. The Hook System makes your personalized Claude Code reactive.
SessionStart Hook (~/.claude/hooks/session-start/): typescript// When session starts: // 1. Load CORE context (identity, principles, contacts) // 2. Check for active tasks from previous sessions // 3. Initialize observability tracking // 4. Set up voice server connection12345 Every time you start Claude Code, this runs automatically. You don't ask for it. It just happens. Stop Hook (~/.claude/hooks/stop/): typescript// When session ends: // 1. Extract 🎯 COMPLETED message from final response //
At the center of my workflow is a custom kai command that wraps Claude Code with voice notifications and context management. bash# Interactive mode (default PAI directory) kai # Single-shot query with voice kai "what's my schedule today?" # Run with specific context directory kai --context ~/Projects/Website "deploy the latest changes" # Silent mode (no voice) kai --no-voice "analyze this code for security issues" # Wallpaper management (Kitty terminal integration) kai wallpaper circuit-boar
Dario Amodei est très clair : aujourd’hui, la science ne dispose d’aucun outil fiable permettant de déterminer si un système d’IA est conscient, ni même de définir précisément ce que serait la conscience dans le cas d’une machine. Il ne dit pas que les modèles actuels sont conscients.Il ne dit pas non plus qu’ils le deviendront forcément. Mais il insiste sur un point : l’absence de certitude ne permet pas d’écarter totalement la question, surtout à mesure que les systèmes gagnent en complexité,
Apple poursuit sa stratégie historique en rendant les technologies accessibles et ergonomiques, notamment via des commandes vocales discrètes. Siri, actuellement en retard face aux assistants basés sur l'IA générative, devrait être renforcé par des partenariats comme celui avec Google pour intégrer des modèles d'IA plus avancés. Cette combinaison permettrait à Apple de retrouver son avantage compétitif dans le domaine crucial de l'interface homme-machine.