dev-workflow
v0.2.1Playwright testing, human-in-the-loop demo/verification workflow, Claude Code environment setup (token optimization, status line), and Godot 4 C# project setup
By Clint Day0 GitHub starsUpdated 6 days ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 5 skill or MCP entries
- Source updated
- Sep 17, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install dev-workflow for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install dev-workflow-3@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/wolf123450/ClaudeSkillsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/dev-workflow/.
Plugin files
├── .claude-plugin/plugin.json├── skills/claude-code-statusline/SKILL.md├── skills/claude-code-token-optimization/SKILL.md├── skills/demoing-work/SKILL.md├── skills/godot-setup/SKILL.md└── skills/playwright-testing/SKILL.md
Included Skills5
Use when the user wants to set up, install, or replicate a Claude Code status line showing model name, session token usage, context-window percentage, and 5h/7-day rate-limit usage — including on a new machine or in a fresh environment.
Use when the user wants to cut Claude Code token/context spend, complains sessions are getting expensive, or asks to set up session-hygiene and subagent-delegation discipline — including replicating this setup on a new machine or in a fresh environment.
Use when implementation work is complete and automated checks (tests, verify, verification-before-completion) pass, before telling the user the work is done. Walks the user through the golden path and relevant edge cases live, then gates completion on the user's explicit confirmation rather than self-declaring the work finished. Use for both UI-facing changes (demo live in the app) and non-UI changes (narrated CLI/API walkthrough).
Use when setting up a new Godot 4.x C#/.NET project for Claude Code agentic development, or bootstrapping MCP servers, local docs indexing, third-party skill curation, custom skills, subagents, and hooks for an existing Godot project. Not for API reference lookups — see the docs-layer setup for that.
Use when writing, running, or debugging Playwright tests against a web application (not Tauri/desktop apps — see tauri-playwright for that), or when driving a live browser to verify or demo a feature. Covers locator strategy, waiting, network mocking, debugging failures, and delegating test runs to a subagent so verbose output stays out of the main session.
Plugin manifests1
{
"name": "dev-workflow",
"description": "Playwright testing, human-in-the-loop demo/verification workflow, Claude Code environment setup (token optimization, status line), and Godot 4 C# project setup",
"version": "0.2.1",
"author": {
"name": "Clint Day",
"email": "[email protected]"
}
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[dev-workflow on Agent Plugins Marketplace](https://pluginsmp.com/plugins/dev-workflow-3)