dotfiles

Use this skill when the user wants to save, update, or reference visual design assets for the project. Triggers on "save design", "update designs", "sync designs", "add visual", "design assets", "claude design export", "design folder", "/design". Also fires proactively when the agent is about to write UI code (React components, CSS, Tailwind classes, layout) — in that case, read the active design first so code matches the visual spec. The design folder is always at `.pi/design/` and the agent should always check it before writing any UI-facing code.

Pointer to the jsdoc-conventions standards file. Read this before writing or editing any JSDoc in a project.

Pointer to the spec-structure standards file. Read this before writing or editing any implementation spec.

Port new paradigms from the global base harness (~/.pi/agent/) into the current project's .pi/ harness, adapting them to match the project's stack, workflow tier, and conventions. Run in any project to pull in improvements made to another project's harness.

Break down a spec.md or requirements.md into an actionable tasks.md with strategic grouping and ordering. Used after spec creation and before implementation.

Detect the project type from code signals and reorganize standards folders to match — web app, backend API, CLI, library, dotfiles, mobile, or monorepo.

Extract tribal knowledge and recurring patterns from the codebase into concise, documented standards files in agent-os/standards/.

Execute an approved spec plan, implementing each task in sequence with mandatory build/test verification before reporting completion.

Analyze your workflow and codebase for repetitive patterns, then generate or refine Pi skills to automate them. Bridges standards discovery with skill creation.

Rebuild and maintain the agent-os/standards/index.yml file so /inject-standards can suggest relevant standards without reading all files.

Set up project standards by detecting dependencies, fetching library docs (checking llms.txt first), generating use-case standards, and updating the standards index.

Inject relevant standards into the current context — auto-suggests based on what you're working on, or accepts explicit paths. Adapts output format for conversation, skill-building, or planning.

Establish foundational product documentation (mission, roadmap, tech-stack) in agent-os/product/ through an interactive conversation.

Create Excalidraw diagram JSON files that make visual arguments. Use when the user wants to visualize workflows, architectures, or concepts.

Write a scoped implementation spec for a feature or change. Produces plan.md, shape.md, standards.md, and references.md in .pi/agent-docs/specs/. Evolves per project via sync-spec.

Post-implementation upkeep runner. Extracts developer patterns and updates project skills, runs configured upkeep tasks, and keeps the harness in sync with how the project is actually built. Configured per project by 0-project-init.

Stage and commit changes with a structured, conventional commit message. Reads git diff to summarize what changed. Developer confirms message before committing. Appends to implementation log.

Execute an approved spec plan step by step, verifying build and tests after each task. Language-agnostic. Workflow-tier aware — pauses at significant decisions on high-care projects.