skills4sh

Persist project decisions, conventions, and session handoffs as reviewable markdown in `.agent-memory/`. Use when asked to "manage project memory", "initialize .agent-memory", "migrate memory", "build memory from docs", "save session learnings", "sync memory", "run memory maintenance", "check memory status", or "onboard a new developer"; when `.agent-memory/` or `AGENTS.md` memory pointers are in play; when sharing project context with another developer or reviewing project memory in a pull request; or when context "forgets between sessions". Sync reconciles files already in the checkout. Not for memory leaks, RAM usage, or human memory.

Export design tokens and page structure from the codebase into a CI pipeline a Figma plugin can consume. Use when asked to "sync code to Figma", "export design tokens to Figma", "set up a Figma sync pipeline", "wire up the tokens-sync-to-figma plugin", "generate a figma-export.json", "create a page walker", or "keep Figma up to date with the codebase".

Extract and archive Discord images, attachments, links, and conversation files. Use when asked to "extract Discord images", "download Discord attachments", "harvest a Discord channel", "archive a DM", or when scraping or preserving content from a Discord conversation.

Build, debug, and review Eleventy v3 sites and Nunjucks templates, including the Build Awesome v4 prerelease migration. Use when asked to "create an 11ty page", "add a Nunjucks filter", "fix my layout chain", "review my .njk template", "set up Eleventy", "migrate to Build Awesome", or "audit my static site"; when `package.json` includes `@11ty/eleventy` or `@awesome.me/buildawesome`; when paths include `.eleventy.js`, `eleventy.config.js`, `.njk`, `.11tydata.js`, `.data.js`, `.11ty.js`, or `.server.js`; or when debugging Nunjucks rendering or Eleventy data cascades, filters, shortcodes, and security. Generic static-site/security topics and `.data.js`/`.server.js` names require confirmed Eleventy or Build Awesome context; standalone Nunjucks work is also in scope.

Implement Figma designs in the existing codebase, map design tokens, and establish component mappings and project rules. Use when asked to "implement this Figma design", "turn this Figma into code", "build from a Figma link", "match this Figma mockup", "extract Figma design tokens", "create Figma design system rules", "set up Figma guidelines", "code connect this component", or "map this Figma component to code"; or when a Figma URL/selection must become repository code, code tokens, agent rules, or Code Connect mappings.

Manage a personal agent rulebook. Use when asked to set up agent rules, reload them at session start or after compaction, fine-tune rule loading, check rulebook status or diagnose unrelated rules being loaded, link dotfiles, configure an AGENTS.md pointer, or update this skill or its rulebook.

Capture and compare localhost pages across viewports for visual regression. Use when asked to "screenshot my site", "capture pages", "visual diff", "compare screenshots", "responsive screenshots", "check breakpoints", "visual regression", or capture a Portless app at a named .localhost URL.

Architect and audit portable agent skills for retrieval, predictability, progressive disclosure, evals, and repository gates. Use when asked to "create a skill", "author a skill", "improve a skill", "review a skill", "refactor a skill", "compare skill rubrics", "distill a skill from sessions", "reconcile skill plans", or "teach skill authoring"; when paths include `skills/<name>/SKILL.md`, `references/*.md`, helper scripts, evals, lockfiles, security manifests, or vendor adapters; or when mentions include skill-creator, Skill Development, skills.sh, trigger descriptions, completion criteria, leading words, or model/user invocation.