bolasblack

Create, update, validate, diff, or export DESIGN.md files following the Google Stitch DESIGN.md spec and @google/design.md tooling. Use when the user asks to write/update DESIGN.md, create a design system document, generate design tokens, encode brand/UI guidelines, export a design system, or document UI consistency rules for AI agents. Do NOT use for ordinary UI implementation unless the user asks for DESIGN.md or design-system documentation.

Screens third-party project dependencies for known vulnerabilities and supply-chain risk before installation using a bundled check-deps.py script. Use when user asks to install, add, update, upgrade, or pin packages with npm, pnpm, yarn, bun, pip, uv, poetry, or cargo, or when deciding whether a package version is safe to install. Do NOT use for OS package managers such as apt, brew, yum, apk, or pacman.

Track decisions (AGD) with validation and indexing. Use when making design decisions, recording important choices, discussing trade-offs, or when user mentions AGD or decision record.

End-to-end workflow for developing, debugging, configuring, and shipping pi-coding-agent extensions and pi packages. Use when building or maintaining extensions, skills, prompt templates, themes, settings.json setups, provider integrations, or when updating this skill after pi releases. Do NOT use for general coding questions unrelated to pi extension development.

Fork the current pi session into a new tmux pane. Use when user says /tmux-fork, 'fork to tmux', 'open in new pane', or wants to branch the conversation into a separate tmux pane.

Create and improve Claude Code Skills following official best practices. Use when creating a skill, improving skill descriptions, fixing skill activation issues, or structuring skill directories.

Convert MCP servers to Claude Code skills with progressive disclosure. Use when creating a skill from an MCP server, updating an existing MCP skill, or converting MCP documentation to skill format. Accepts MCP documentation URLs, npm package names, or direct connection info.

Query up-to-date library documentation and code examples using Context7. Provides 2 tools for resolving library IDs and querying documentation.

Generate changelog entries for alcatraz releases following Common Changelog conventions. Use when preparing a release, writing changelogs, creating release notes, or when user mentions release-note, changelog, or release preparation.

Review test code quality against behavioral testing principles. Use when reviewing test files, evaluating test quality, auditing test suites, or when asked about test coverage and test design issues.

Auto-fix Clojure/ClojureScript bracket mismatches using parinfer indentMode. Use when writing or editing .clj, .cljs, or .cljc files, working on ClojureScript code, or after any file modification to Clojure source. Do NOT use for non-Clojure files.

Rebase this fork onto the latest upstream while preserving spec-defined local behavior. Use when the user wants to rebase onto upstream, sync a fork with upstream/main, preserve local behavior after upstream changes, or clean history after an upstream sync. Do not use for ordinary merge conflict resolution unrelated to spec-backed fork maintenance.

Align ESLint and Oxlint configurations during lint setup, migration, or template maintenance. Use when configuring ESLint and Oxlint together, migrating ESLint to Oxlint, updating lint rule templates, comparing rule parity, changing lint scripts, reviewing inline lint disables, or modifying packages/toolconfs ESLint/Oxlint config templates such as eslint.mts, oxlint.mts, eslint.config.*, oxlint.config.*, eslintrc*, or oxlintrc*.