From ironforge
Verify and install all Ironforge dependency plugins. Run this once after installing Ironforge, or anytime you need to check that all dependencies are properly configured.
npx claudepluginhub romaindecoster/ironforge --plugin ironforgeThis skill is limited to using the following tools:
You are running the Ironforge setup procedure. Verify that all dependencies are available and help the user install any that are missing.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
You are running the Ironforge setup procedure. Verify that all dependencies are available and help the user install any that are missing.
Check each plugin's availability in the current session. For any that are missing, provide the exact installation commands below.
@analyst, @architect, @scrum-master, @dev)npx bmad-method install
/plugin marketplace add obra/superpowers-marketplace
/plugin install superpowers
upsert_spec, upsert_issue)/plugin marketplace add sudocode-ai/sudocode
/plugin install sudocode
use context7 capability/plugin marketplace add upstash/context7
/plugin install context7-plugin@context7-marketplace
/plugin install security-guidance@claude-plugins-official
.claude/agents/ (project-local) — specifically engineering-code-reviewer and testing-reality-checker
ls .claude/agents/ 2>/dev/null | grep -c engineering
git clone --depth 1 https://github.com/msitarzewski/agency-agents /tmp/agency-agents
mkdir -p .claude/agents && cp -r /tmp/agency-agents/agents/* .claude/agents/
rm -rf /tmp/agency-agents
After all plugins are confirmed, check if the .sudocode/ directory exists in the project root. If not, run:
sudocode init
This creates the .sudocode/ directory where specs and issues are persisted and committed to git.
/plugin commands yourself, the user must invoke them.sudocode/ is missing, inform the user to run sudocode init