config-sync

Handlauf: walk a built phase through the real interface in a browser as a demanding user and report what is wrong (layout, states, speed, usability, edge…

Build a released plan block by block in git worktrees, with subagents on the cheaper model.

Initialize a project's Claude Code configuration: Obsidian knowledge base, PRD, root and area CLAUDE.md files, path-scoped rules, hooks.

Write a Product Requirements Document (PRD) for a software system or AI feature: executive summary, user stories, technical specification, risks.

Decide which screens a product needs and how they connect, before any is specified: inventory of what exists, navigation graph, findings, target page list…

Define a project's design system, write tokens into the codebase and reasoning into the knowledge base, approved via an example page.

Shared vocabulary for designing deep modules: module, interface, depth, seam, adapter, leverage, locality.

Review open or phase changes against specs, accepted decisions and the project's own patterns, in three parallel lenses (security, spec fidelity, structure)…

Write the handoff for the next session into .claude/state.md.

Run a retrospective on a session or build phase and propose changes to the agent's environment: automated checks, review standards, a slimmer CLAUDE.md.

Write the implementation plan for one build phase in plan mode and get it released before anything is touched.

Survey the existing code for places where shallow modules can be deepened, show the candidates as a visual HTML report, and work the chosen one through the…