atelier-setup

Solid

Configure a repository for Atelier's development workflow. Use only when the user explicitly invokes atelier-setup; it inspects existing repository instructions and domain-document conventions, previews an idempotent project-guidance update, and writes only after approval. It does not install Atelier, configure a harness, or scaffold empty workflow artifacts.

AI & Automation 38 stars 3 forks Updated today MIT

Install

View on GitHub

Quality Score: 87/100

Stars 20%

Recency 20%

100

Frontmatter 20%

Documentation 15%

100

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

# Atelier Setup Set up the repository conventions that Atelier skills need without taking ownership of the developer's installation, harness configuration, or project structure. Explore first, present the proposed edit exactly, and write only after the developer approves it. ## 1. Explore Read the repository before proposing any change: - Root `AGENTS.md` and `CLAUDE.md`, if present. Note whether either already has an `## Atelier` heading. - Root `CONTEXT.md` and `CONTEXT-MAP.md`. - `docs/adr/` and any context-local `docs/adr/` directories. - Genuine monorepo signals: a workspace manifest, or multiple independently deployable packages with their own source directories. Do not create, install, configure, or modify anything during exploration. ## 2. Present Findings Summarize what exists and recommend a domain-document layout: - **Single-context** is the default: domain language belongs in root `CONTEXT.md`; architectural decisions belong in root `docs/adr/`. - **Multi-context** is appropriate only when the repository has genuinely separate bounded contexts. `CONTEXT-MAP.md` belongs at the root and points to each context's `CONTEXT.md` and `docs/adr/` directory. Explain that these documents remain lazy: do not create `CONTEXT.md`, `CONTEXT-MAP.md`, or an ADR directory until another Atelier skill has resolved terminology or made a decision worth recording. Select the instruction file to edit: 1. If both files exist, ask which file should own the Atelier guid...

Details

Author: martinffx
Repository: martinffx/atelier
Created: 6 months ago
Last Updated: today
Language: TypeScript
License: MIT

Integrates with

Anthropic · AI

Bundled in these plugins

atelier

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

init-workspace

Bootstrap a project's way of working: fetch the agentic-workflow documentation scaffold (template/) and adapt it to THIS project by interview — fill the CLAUDE.md documentation map, gate commands and architecture, prune doc folders that don't apply, keep the SPEC/feature/fix and GitHub templates — then offer to install the skills. The adaptive counterpart to a raw `npx degit` copy. On a repo that already has the scaffold, detects it and switches to **upgrade mode**: diffs the project's substrate against the current template, reads `docs/workflow/MIGRATION.md`, and proposes only the blocks the project is missing — never clobbering a tailored one. On Claude Code and want hand-tuned per-skill model/effort tiers? Install the `#claude` branch instead (`npx skills add gtrabanco/agentic-workflow#claude`) — see the README. This branch is model-agnostic: the skill inherits whatever model and effort your agent session is already using. Triggers: "set up the agentic workflow here", "init-workspace", "scaffold this proje

19 Updated 1 weeks ago

gtrabanco

Code & Development Listed

setup-engineering

Configures this repository for the engineering skills by writing .claude/engineering.local.md — where specs, plans, and ADRs are saved, if at all — and excluding it from git locally. Run once per repository before relying on doc-saving skills.

0 Updated yesterday

thinceller

AI & Automation Listed

orient

Orient in the current project. On first contact with an unprepared project, set up the workflow's operating requirements, then orient. Run autonomously. Use for /orient requests.

0 Updated today

amurshak