internal/builtins/content/sync/SKILL.md
Per-folder AGENTS.md generator. Walks the project tree, analyzes each directory's languages and key files, and writes AGENTS.md (only) into every folder that lacks a user-customized one. Drop-in replacement for v1's per-folder context sync; tool-specific context files now belong to translator plugins instead of the core framework. Use when the user asks to "sync the project", "regenerate AGENTS.md", or "refresh the per-folder context".
npx skillsauth add ar4mirez/samuel syncInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
samuel sync walks the project tree and writes per-folder AGENTS.md
files describing each directory's purpose, primary languages, key
files, and whether tests live there. The framework writes AGENTS.md
exclusively — vendor-specific context files are produced by translator
plugins, not the core (v2 invariant per RFD 0009).
<!-- Auto-generated by Samuel. Files without the marker are
considered user-customized and skipped unless --force.node_modules/, vendor/,
language build outputs, and IDE caches are skipped. Configurable
via samuel.toml [sync.skip].[sync.languages]).[sync.folders]).go.mod, package.json, etc.) are surfaced with descriptions.Methodology bodies can intercept via these named hook points (bodies arrive in PRD 0004):
sync.before — once before the walk startssync.analyze-folder — per directory, after analysissync.write-agents-md — per directory, before writesync.after — once after the walk endsdevelopment
Zig language guardrails, patterns, and best practices for AI-assisted development. Use when working with Zig files (.zig), build.zig, or when the user mentions Zig. Provides comptime patterns, allocator conventions, C interop guidelines, and testing standards specific to this project's coding standards.
tools
WordPress framework guardrails, patterns, and best practices for AI-assisted development. Use when working with WordPress projects, or when the user mentions WordPress. Provides theme development, plugin architecture, REST API, blocks, and security guidelines.
tools
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs. Use when testing web apps, automating browser interactions, or debugging frontend issues.
tools
Suite of tools for creating elaborate, multi-component web applications using modern frontend technologies (React, Tailwind CSS, shadcn/ui). Use for complex projects requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX pages.