Skip to content
Back to search

studio

MarketplaceWorks with Claude CodeGitHub

The /studio plugin: repo-native traced development.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/eversluis--studio/badge.svg)](/listings/eversluis--studio)

HTML

<a href="/listings/eversluis--studio"><img src="/api/listings/eversluis--studio/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

claude plugin marketplace add ~/Projects/studio
claude plugin install studio@studio

Then, in any repo, use one of: - `/studio <idea>` (top-down, the preferred mode); - `/studio fix <change>` (bottom-up, small changes only); - `/studio refactor <goal>` (behaviour unchanged, proven by the same tests); - `/studio recode <scope>` (write it fresh from the plan, compare with the old code, and choose per component); - `/studio adopt` (an existing repo); - `/studio audit`.

For Obsidian, see `skills/studio/reference/obsidian.md`.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 16 lines
  1. {
  2. "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
  3. "name": "studio",
  4. "description": "The /studio plugin: repo-native traced development.",
  5. "owner": {
  6. "name": "Eric Versluis",
  7. "email": "eric.versluis@paqt.com"
  8. },
  9. "plugins": [
  10. {
  11. "name": "studio",
  12. "source": "./",
  13. "description": "Six-layer traced development as markdown in the repo, readable in Obsidian."
  14. }
  15. ]
  16. }
README.md · README · 50 lines
  1. # studio
  2. A Claude Code plugin: `/studio` develops software through six traced layers, kept as concise markdown in the repo's `studio/` folder and read in Obsidian.
  3. | | EngineeringStudio (app) | /studio (this plugin) |
  4. |---|---|---|
  5. | Storage | server and web UI | markdown in the repo |
  6. | Review | marks, two-step approval | git |
  7. | Layers | P, R, S, Detailed Design, Analysis, V | P, R, A (Architecture), C (Code), CR (Code Review), V |
  8. | Link suggestions | embeddings | code facts (paths, imports, per-test coverage) and BM25, judged by the agent |
  9. | Fits | formal projects, sign-off | everyday development by agents |
  10. It is the same V-model in a lighter flavour, and it sits next to the app rather than replacing it. The one hard rule is that all code is linked: every public symbol is in a Code entity, and every test is in a Verification entity. The code is never copied: Code and Verification entities embed it live.
  11. - Process and modes: `skills/studio/SKILL.md`
  12. - Rules and entity format: `skills/studio/reference/rules.md`
  13. - Layer agents: `agents/`
  14. - Helper (stdlib Python 3.11+): `skills/studio/scripts/studio.py`. It reads Python natively and every other language (TS/JS, Go, Java, Kotlin, C#, PHP, Rust, Swift, …) through [Universal Ctags](https://ctags.io) (`brew install universal-ctags`). Coverage runs pytest for Python and any lcov-producing runner for the rest. `studio.py check` runs the repo's own linters and type checkers (ruff, mypy, pyright, eslint, biome, tsc, svelte-check, semgrep: whichever the repo configures) and puts each finding under its Code entity.
  15. ## Install
  16. ```bash
  17. claude plugin marketplace add ~/Projects/studio
  18. claude plugin install studio@studio
  19. ```
  20. Then, in any repo, use one of:
  21. - `/studio <idea>` (top-down, the preferred mode);
  22. - `/studio fix <change>` (bottom-up, small changes only);
  23. - `/studio refactor <goal>` (behaviour unchanged, proven by the same tests);
  24. - `/studio recode <scope>` (write it fresh from the plan, compare with the old code, and choose per component);
  25. - `/studio adopt` (an existing repo);
  26. - `/studio audit`.
  27. For Obsidian, see `skills/studio/reference/obsidian.md`.
  28. ## Other models
  29. The requirements critic, the code mapper and the code reviewer can run on an OpenAI model through the [GitHub Copilot CLI](https://docs.github.com/copilot/how-tos/copilot-cli) (`copilot`), so that a second model reviews Claude's work. Turn it on per repo with `[delegate.<agent>]` in `studio/studio.toml` (see "Delegation to other models" in `skills/studio/SKILL.md`). The CLI uses your `copilot` sign-in, or a token in `COPILOT_GITHUB_TOKEN` (set it in your shell profile, never in a repo). Run `studio.py delegate --list` to see what runs where. When Copilot can't run, the skill falls back to the Claude agent. Delegated runs send repository content to GitHub.
  30. ## Develop
  31. ```bash
  32. python3 -m venv .venv && .venv/bin/pip install pytest pytest-cov
  33. .venv/bin/python -m pytest -q # the multi-language tests skip without universal-ctags
  34. ```
  35. ## Copyright
  36. Copyright (c) 2026 Eric Versluis. All rights reserved. See `LICENSE`.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.