af-engineer-command

Design, package, and maintain modular AssistFlow commands with SKILL.md frontmatter.

3|Updated Oct 5, 2025
One-click install
npx skills add https://github.com/korchasa/ide-rules --skill af-engineer-command
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: af-engineer-command
Source: https://github.com/korchasa/ide-rules/tree/main/catalog/skills/af-engineer-command
Command: npx skills add https://github.com/korchasa/ide-rules --skill af-engineer-command

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps teams design and maintain modular AssistFlow commands (Skills) that extend capabilities, enabling consistent, reusable workflows.

Core Features & Use Cases

  • Guidance for creating new Commands (SKILL.md frontmatter, structure, and resources) and best practices for packaging.
  • Clear anatomy and patterns for command organization (scripts/, references/, assets/), including validation, packaging, and progressive disclosure.
  • Use cases include building domain-specific commands, updating existing commands, and scaling workflows across projects.

Quick Start

Run the init_command.py script to scaffold a new command folder, then customize SKILL.md and the bundled resources.

Frequently Asked Questions about af-engineer-command

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

FAQPage Schema
How do I create reusable command workflows for AssistFlow?

You create reusable AssistFlow command workflows by scaffolding a new command folder via init_command.py, then customizing the SKILL.md frontmatter alongside organized scripts, references, and assets.

What is the correct folder structure for packaging modular AI commands?

The correct folder structure for modular AI commands uses scripts/, references/, and assets/ subdirectories to ensure deterministic workflows and progressive disclosure aligned with the .cursor/skills directory.

How does frontmatter validation work when packaging commands into .skill files?

Frontmatter validation checks your SKILL.md metadata against required schemas before packaging commands into .skill files, preventing structural errors and maintaining consistent workflows across projects.

Can I use this to update existing AssistFlow commands across multiple projects?

Yes, you can update existing AssistFlow commands across projects by modifying the modular scripts, references, and assets, then revalidating the frontmatter and repackaging the resources into .skill files.

What's the best way to scale domain-specific command workflows?

The best way to scale domain-specific command workflows is applying modular organization patterns with deterministic scripts and structured references, ensuring commands remain maintainable and progressively discoverable across teams.