source-command-sparc-code

Generates modular code from pseudocode and architecture using the SPARC code mode.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/derbalimajd04-dot/al-wasat --skill source-command-sparc-code-derbalimajd04-dot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-command-sparc-code
Source: https://github.com/derbalimajd04-dot/al-wasat/tree/main/.agents/skills/source-command-sparc-code
Command: npx skills add https://github.com/derbalimajd04-dot/al-wasat --skill source-command-sparc-code-derbalimajd04-dot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It provides a structured Auto-Coder workflow that turns pseudocode and architecture definitions into clean, modular code without hardcoded secrets or oversized files. ## Core Features & Use Cases - Modular Code Generation: Writes code following clean architecture principles, splitting components into files under 500 lines. - Configuration Management: Uses config files and environment abstractions instead of hardcoded secrets or environment values. - Multiple Execution Paths: Runs via MCP tools (claude-flow sparc_mode), NPX CLI fallback, or a local Codex-flow installation. - Use Case: Ask the agent to implement REST API endpoints from an architecture spec, and it generates modular, configuration-driven code while storing context in memory for later retrieval. ## Quick Start Ask the agent to run the sparc code mode to implement your REST API endpoints from the provided architecture.

Frequently Asked Questions about source-command-sparc-code

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

FAQPage Schema
How do I run the SPARC code mode to generate code?▼

Run the SPARC code mode via the MCP tool mcp__claude-flow__sparc_mode with mode set to code and a task description, or use the NPX fallback command npx Codex-flow sparc run code followed by your task description.

How to implement REST API endpoints with SPARC code mode?▼

Pass a task description like implement REST API endpoints to the sparc_mode MCP tool or the NPX CLI command. The Auto-Coder writes modular code following clean architecture, splitting files under 500 lines and using config-based environment values.

What is the difference between MCP tools and NPX CLI for SPARC?▼

MCP tools are the preferred option when available, offering direct integration like sparc_mode and memory_usage. The NPX CLI is a fallback for terminal use or when MCP tools are unavailable, supporting the same modes and namespaces.

Does SPARC code mode support memory and context storage?▼

Yes, it supports memory integration through mcp__claude-flow__memory_usage for storing and searching context, or the NPX commands memory store and memory query with a namespace flag for mode-specific recall.

What are the limitations of the Auto-Coder code generation?▼

The Auto-Coder requires clear pseudocode or architecture input and depends on claude-flow tooling being available via MCP or NPX. It enforces file size limits under 500 lines, so very large components must be decomposed into subtasks.