load-design
openbooklet.com/s/load-designopenbooklet.com/s/load-design@1.0.0GET /api/v1/skills/load-designUse when a project's design system lives outside the project root (e.g., a shared monorepo package, a sibling directory). Sets design_system_path in pipeline-config.json so all agents use the specified path instead of the default design-system/ convention.
Use when users want to bootstrap the brain with existing project knowledge -- reading ADRs, feature specs, UX docs, commit history, retro lessons, and error patterns to seed institutional memory on a project that already has artifacts on disk. Also use for incremental re-hydration after significant work outside the pipeline. Triggers on "hydrate brain", "bootstrap brain", "seed memory", "brain init", "populate brain", "import history".
Use when users want to set up or connect to the Atelier Brain -- the persistent memory layer for the pipeline. Handles first-time setup (personal or shared), colleague onboarding from existing config, database provisioning, and connection verification.
Use when users ask about the atelier-pipeline system, how it works, what agents do, or how to use the multi-agent orchestration pipeline. Covers agent roster, pipeline flow, quality gates, and key principles.
Use when users want to install or set up the atelier-pipeline multi-agent orchestration system in their project. Bootstraps all agent personas, rules, commands, references, and pipeline state files. Works for new and existing projects.
Use when users want to remove the atelier-pipeline multi-agent orchestration system from their project. Cleanly removes all installed files, hook registrations, and CLAUDE.md pipeline section. Preserves user-created custom agents and retro lessons on request.
Auto-indexed from robertsfeir/atelier-pipeline
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.