dotfiles

Update project documentation — README.md, user guide, and UML.md. Evaluates whether the project is a coding project or a non-code workspace and adapts accordingly. Load when asked to update docs, refresh documentation, or after significant changes.

Resume work in an existing project. Reads the latest handoff (if any), then UML.md, and gives the user a fast on-ramp. Also handles quick catch-ups ("what was I doing?").

Structured workflow for adding any new feature to an existing project. Creates a features/<slug>/ directory containing a living spec (README.md), technical plan (plan.md), implementation log (changes.md), and review report (review.md). Covers requirements clarification, codebase pattern survey, plan approval gate, implementation, UML.md update, and diff review. Use whenever a user asks to add, build, or implement a new feature, integration, job, endpoint, or module.

Manages the handoffs/ directory — a chronological log of session-ending state snapshots. Write a handoff when finishing a session or completing a feature. Read the latest handoff when resuming a project. The next agent reads ONLY the most recent handoff file; older files are the user's version history and must not be read by the agent. Load this skill when asked to hand off, wrap up, or when resuming a project that has a handoffs/ directory.

Modern take on brutalism with bold borders, vivid accent colors, and raw, high-contrast layouts on warm surfaces.

Comprehensive bootstrap flow for a brand-new project. Begins with a deep-dive architectural conversation, then runs a plan → implement → review chain, and finally writes the initial UML.md. Load this when the user starts pi in an empty or near-empty directory, or when explicitly asked to bootstrap a new project.

Enforce a planning-first workflow. Before non-trivial implementation, write or update plan.md with goals, approach, file-level changes, risks, and a checklist. Use when the user asks to build a feature, refactor, fix a non-obvious bug, or whenever scope is unclear. Skip only for one-line tweaks or pure questions.

Canonical specification for the project's UML.md file. Every project pi works on keeps a single UML.md at the repo root that captures the current architecture as Mermaid diagrams plus a Last Activity log. Load this skill when creating or updating UML.md.