curdx-core

Define CURDX core argument flags and .curdx-state.json state management rules.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ForeverWorld/curdx-ralph --skill curdx-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: curdx-core
Source: https://github.com/ForeverWorld/curdx-ralph/tree/main/skills/curdx-core
Command: npx skills add https://github.com/ForeverWorld/curdx-ralph --skill curdx-core

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Centralizes and standardizes the CURDX core arguments and state-management rules to reduce ambiguity and errors across plugins and workflows.

Core Features & Use Cases

  • Standardized flags: --quick, --commit, --no-commit, --max-task-iterations, --fresh
  • State-file guidance: .curdx-state.json schema and phase definitions
  • Consistent parsing and execution modes across all CURDX plugins and runtimes
  • Use Case: A plugin developer can rely on a single, documented core for argument handling and state transitions.

Quick Start

Configure and apply CURDX core to unify argument parsing and state management across all plugins.

Frequently Asked Questions about curdx-core

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize CLI arguments and state management for plugin development?

To standardize CLI arguments and state management for plugin development, apply CURDX core rules to unify parsing logic, execution modes, and state-file schema definitions across all workflows.

What is the .curdx-state.json schema used for in runtime state management?

The .curdx-state.json schema defines phase tracking and state transitions during runtime execution. It centralizes state management to reduce ambiguity and errors across different plugins and workflows.

How do I use the --quick and --commit flags for CLI execution mode configuration?

Configure CLI execution modes by passing supported flags like --quick for quick mode and --commit or --no-commit to control branch handling. These standardized flags ensure consistent parsing across all CURDX plugins.

Does CURDX core work with requirement-driven design and standard execution workflows?

Yes, CURDX core applies to both standard and quick modes, including requirement-driven design workflows. It standardizes argument handling and state transitions across all runtime environments without external dependencies.

What are the limitations of using manual state files versus a centralized state management schema?

Manual state file handling introduces ambiguity and parsing errors across plugins. CURDX core resolves this by enforcing a unified .curdx-state.json schema and standardized flag parsing logic for consistent execution.

How do I configure max task iterations and fresh state for runtime execution?

Configure runtime execution by passing the --max-task-iterations flag to limit cycles and --fresh to reset state. CURDX core defines these standardized arguments to ensure consistent parsing across plugin runtimes.