Slash Command

/init-workspace-flow-rules

Creates IDE/OS/project-specific agent rule files for workspace customization if explicitly enabled (Phase 4 of init-workspace-flow). Skips otherwise.

developer-tools

npx claudepluginhub griddynamics/rosetta --plugin core

Prompt Preview

<init_workspace_flow_rules>

<description_and_purpose>
Creates IDE-specific and tech-specific rule files that customize agent behavior for the workspace. Optional, disabled by default — runs only when explicitly enabled by user.
</description_and_purpose>

<workflow_context>
- Phase 4 of 8 in init-workspace-flow
- Input: TECHSTACK (from P3), state.mode, IDE/OS detection
- Output: core agents file, tech-specific rule files
- Prerequisite: Phase 3 complete (TECHSTACK exists on disk)
</workflow_context>

<phase_steps>
1. Check if rules phase enabled
2. If disabled, mark skipped and proceed to ...

Command Content

Other plugins with /init-workspace-flow-rules

/rulebook-init

Initializes Rulebook for the current project by auto-detecting languages/frameworks/services, generating AGENTS.md with rules/skills and .rulebook config. Optionally installs Git hooks and GitHub Actions workflows.

rulebook

/hatch3r-rule-customize

Customizes hatch3r rules by editing scope globs, toggling enabled state and activation mode, overriding descriptions via YAML, and appending markdown instructions in .hatch3r/rules/ files.

hatch3r

/init

112

Creates or updates AgentBridge project config files (.agentbridge/config.json and collaboration.md) in the current workspace with defaults for daemon ports, agents, markers, turn coordination, roles, thinking patterns, communication, and review process.

5 tools

agentbridge

/init

118

Initializes or audits .claude/ configuration by detecting repository tech stack and generating CLAUDE.md, settings.json, and rules. Supports --audit and --force flags.

7 tools

/init-rules

Runs interactive wizard to generate or update .spartan/config.yaml for rules, review stages, and build commands. Auto-detects project stack (languages, frameworks, DBs, tests); supports profiles.

ai-toolkit

/cc-setup

Analyzes current repo, detects tech stack and infra, deploys full 4-layer Claude Code setup (CLAUDE.md routing, Skills, Hooks, Agents), MCP servers, LSP hints, memory, and cost optimization. Supports --auto, --dry-run, --audit flags.

claude-code-expert

Stats

Parent Repo Stars15

Parent Repo Forks6

Last CommitMar 25, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

<init_workspace_flow_rules> <description_and_purpose> Creates IDE-specific and tech-specific rule files that customize agent behavior for the workspace. Optional, disabled by default — runs only when explicitly enabled by user. </description_and_purpose> <workflow_context> - Phase 4 of 8 in init-workspace-flow - Input: TECHSTACK (from P3), state.mode, IDE/OS detection - Output: core agents file, tech-specific rule files - Prerequisite: Phase 3 complete (TECHSTACK exists on disk) </workflow_context> <phase_steps> 1. Check if rules phase enabled 2. If disabled, mark skipped and proceed to ...

<init_workspace_flow_rules>

<description_and_purpose> Creates IDE-specific and tech-specific rule files that customize agent behavior for the workspace. Optional, disabled by default — runs only when explicitly enabled by user. </description_and_purpose>

<workflow_context>

Phase 4 of 8 in init-workspace-flow
Input: TECHSTACK (from P3), state.mode, IDE/OS detection
Output: core agents file, tech-specific rule files
Prerequisite: Phase 3 complete (TECHSTACK exists on disk) </workflow_context>

<phase_steps>

Check if rules phase enabled
If disabled, mark skipped and proceed to Phase 5
Read state and TECHSTACK
Execute rules skill
Update state </phase_steps>

<check_enabled step="4.1">

Read agents/init-workspace-flow-state.md
If rules phase NOT enabled: mark Phase 4 skipped in state, proceed to Phase 5
Autonomous decision based on enable flag — no user prompting </check_enabled>

<read_inputs step="4.2" condition="enabled">

Read state.mode for dual-mode behavior
Read TECHSTACK from disk
Detect IDE and OS from environment </read_inputs>

<execute_rules step="4.3" condition="enabled">

ACQUIRE init-workspace-rules/SKILL.md FROM KB and EXECUTE with state.mode and TECHSTACK as inputs </execute_rules>

<update_state step="4.4">

Write to agents/init-workspace-flow-state.md:
- Rule files status (created | updated | skipped | disabled)
- Phase 4 completion timestamp
Log gaps identified for Phase 7 </update_state>

<validation_checklist>

Disabled: state shows "skipped: disabled by default", no rule files modified
Enabled: core agents file and tech rules exist on disk, consistent with TECHSTACK </validation_checklist>

- Halt if TECHSTACK missing — dependency failure, do not generate rules

</init_workspace_flow_rules>