Meticulous Iterative Dev Skill: What It Does and How to Install It
Makes your agent check each step of a frontend change with a quick Meticulous visual simulation before a full cloud run.
- Installs
- 8.7K
- on skills.sh
- Stars
- 10
- on GitHub
- Updated
- Oct 2026
- last repo commit
meticulous-iterative-dev makes your agent build a multi-step frontend change one step at a time. After each step it finds the recorded sessions that touch the changed code, replays one or two against your local dev server, and sorts every visual difference into expected or unexpected before it commits.
When every step is done it hands off to meticulous-test for a full cloud run. It needs the meticulous command-line tool installed and signed in, a dev server at a known URL, and a git repo. It begins by running meticulous-cli-update, which can install or update software.
Good for
- Front-end developers making multi-step UI changes with an agent
- Teams already testing with Meticulous who want earlier feedback
- Reviewers who want unintended visual side effects caught per step
Install meticulous-iterative-dev
Claude Code
- 1
Copy this prompt.
Install the meticulous-iterative-dev skill in Claude Code. Run this command: /plugin marketplace add alwaysmeticulous/skills /plugin install meticulous@meticulous Then check that it loaded and tell me how to use it.
- 2
Paste it into Claude Code. It shows the change and asks before running it.
meticulous-iterative-dev calls other Meticulous skills, so install the whole set (the repo has 11). Full setup: app.meticulous.ai/docs/agents/setup. Plugin skills are named /meticulous:<skill-name>. After the plugin install, type /mcp and choose Authenticate for the Meticulous server. Choose one route; the skills CLI command targets Claude Code, Codex and Cursor together.
From the project README. Source.
What's in the skill
When it loads
Iterative frontend development loop using Meticulous for per-step visual validation. Use when implementing a multi-step frontend change and want to catch visual regressions and unintended side effects at each step, before the final cloud test run.
Sections in SKILL.md
- Prerequisites
- Per-step loop
- Step 1 — Implement the step's changes
- Step 2 — Find relevant sessions
- Step 3 — Simulate and analyse
- Step 4 — Commit
- After all steps — full cloud test run
- Final step — Report feedback to Meticulous
Key facts
- Installs on skills.sh
- 8,699 (Nov 2, 2026)
- GitHub stars (repo)
- 10 (Nov 2, 2026)
- Last commit (repo)
- Oct 29, 2026
What it includes
Runs the CLI and skills update check unless it already ran in this conversation.
Installs or updates software; see the safety section.
Runs code ·
meticulous-cli-update (first)Your agent makes the code changes for this step.
Step 1: implement the stepFinds recorded sessions that exercise the changed code.
Returns session IDs, base replay IDs and a relevance label. With --startingPointSha it only looks at changes since your last commit. If nothing is returned, it commits and relies on the final cloud run.
Runs code ·
meticulous local relevant-sessionsReplays 1 or 2 relevant sessions against your local app and classifies each diff.
Follows meticulous-simulate-and-diff with --appUrl pointing at your dev server and --headless. Each diff is Expected or Unexpected; unexpected ones are fixed and re-simulated.
Runs code ·
Step 3: simulate and analyseCreates a debug workspace when the cause of a difference is unclear.
Takes the head replay ID and --baseReplayId from the simulation output.
Runs code ·
meticulous debug replayRuns git add -p and git commit after each step.
Committing each step keeps the next --startingPointSha diff small.
Runs code ·
Step 4: commitAfter all steps, follows meticulous-test across the full set of recorded sessions.
Network ·
Full cloud test runSends Meticulous one short note on whether the loop helped.
Uses --outcome helped, neutral or hindered and --skill=meticulous-iterative-dev.
Network ·
meticulous agent submit-feedback
From the official docs
Permissions
Medium risk
This skill commits to your branch and ends by uploading a build to Meticulous. Run it on a feature branch and read each command your agent proposes.
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only mode
Watch out for
It commits to your branch after every step
The loop runs git add -p and git commit once per step, as SKILL.md describes. Work on a branch you are happy to have extra commits on. github.com
It ends by uploading a build to Meticulous
The final cloud run follows meticulous-test, which uploads your built frontend or Docker image to Meticulous. Only use it on code you are allowed to send there. github.com
It installs or updates software for you
Every Meticulous skill starts with meticulous-cli-update, which can run npm install --global @alwaysmeticulous/cli@latest, npx skills add alwaysmeticulous/skills with -y, and plugin updates. SKILL.md says to recommend the command instead if you decline a permission prompt. github.com
It sends a feedback note to Meticulous
The skill ends with meticulous agent submit-feedback (or the MCP submit_feedback) carrying a one or two sentence message, an outcome and the skill name. Tell your agent to skip it if you prefer. github.com
The plugin route connects a hosted MCP server
The plugin bundles an .mcp.json for https://app.meticulous.ai/api/mcp and no hooks or agents appear in the repo tree. You sign in from /mcp in Claude Code. github.com
Technical details
| Talks to | app.meticulous.ai |
|---|---|
| Sign-in and keys | Browser sign-in with meticulous auth login stores a token; METICULOUS_API_TOKEN or ~/.meticulous/config.json also work. |
| Scopes |
|
Questions
How do I install meticulous-iterative-dev?
Use the install box at the top of this page. The README installs the whole set of Meticulous skills, because this skill calls others. You also need the meticulous command-line tool and a sign-in, which the README gives as npm install --global @alwaysmeticulous/cli@latest then meticulous auth login.
Does meticulous-iterative-dev work in the Claude app?
Not as a Claude app skill. It runs the meticulous command-line tool and works with your git repo, so use Claude Code, Codex or Cursor, which the README names. The plugin route also connects a hosted Meticulous MCP server.
Do I need a Meticulous account?
Yes. The skills use the Meticulous CLI or MCP server, and sign-in happens in your browser through meticulous auth login. An API token set in METICULOUS_API_TOKEN also works, according to the skills' update instructions. What Meticulous itself costs is not stated in the repo.
Is meticulous-iterative-dev safe to use?
It runs commands and talks to Meticulous, so read what your agent proposes. It commits to your branch after each step and finishes by uploading a build to Meticulous. Every Meticulous skill also starts with an update check that can install packages, and it ends with a feedback note sent to Meticulous. See the safety section for details.
Is it official?
Yes. It is in Meticulous's own repo (alwaysmeticulous/skills), and the plugin manifest names Meticulous as the owner.
How is it different from meticulous-test?
meticulous-iterative-dev checks each step locally with one or two simulated sessions and commits as it goes. meticulous-test builds, uploads and runs the full cloud comparison. The iterative skill ends by following meticulous-test.
Information
updated Nov 2, 2026
- Repository
- alwaysmeticulous/skills
- Folder
skills/meticulous-iterative-dev
Sources
Docs, issue trackers and discussions this page is built from.
Show all 6Hide
- alwaysmeticulous/skills README · github.com
- Meticulous agent setup docs · app.meticulous.ai
- meticulous-iterative-dev SKILL.md · github.com
- meticulous-cli-update SKILL.md · github.com
- marketplace.json · github.com
- plugin.json · github.com