code-engine-skill

Document Code Engine CLI repository conventions and architecture across src/, tools/, commands/, and skills.

Updated May 21, 2026
One-click install
npx skills add https://github.com/gomezsteve382/command-center-tool --skill code-engine-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-engine-skill
Source: https://github.com/gomezsteve382/command-center-tool/tree/main
Command: npx skills add https://github.com/gomezsteve382/command-center-tool --skill code-engine-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires esbuild, and includes scripts (resource) components.

What problem does it solve?

Code Engine's repository lacks a unified, discoverable set of conventions and architecture documentation, making onboarding and contributor collaboration challenging.

Core Features & Use Cases

  • Centralized guide to Code Engine CLI architecture, including src/, tools/, commands/, and the skill system.
  • Clear rules for Skill Units (mandatory SKILL.md with name/description frontmatter) and optional resources (scripts/references/assets) to enable on-demand loading.
  • Provides a governance scaffold for maintainers to align future changes with established patterns and best practices.

Quick Start

Review this guide before implementing new features to ensure alignment with the repository’s conventions.

Frequently Asked Questions about code-engine-skill

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

FAQPage Schema
How do I document CLI architecture conventions for a TypeScript repository?

Documenting CLI architecture conventions involves defining structural rules for src/, tools/, commands/, and skills directories to guide feature development and project organization. It provides a centralized governance scaffold for contributor onboarding.

What are the mandatory frontmatter requirements for skills?

Mandatory skills frontmatter requires a SKILL.md file containing name and description fields. This enforces discoverability and standardizes skill unit definitions across the repository.

How do I organize optional assets in a CLI tool for on-demand loading?

Organizing optional assets for on-demand loading involves separating scripts, references, and assets from the core skill logic. This prevents unnecessary payload execution during initial CLI startup.

Does the Code Engine architecture guide work with esbuild?

The architecture guide applies to repositories using esbuild as a dependency. It aligns build tooling conventions with the overarching project structure and coding style guidelines.

What is the best way to align new CLI features with established coding conventions?

Aligning new features with coding conventions requires reviewing centralized architecture documentation before implementation. This ensures new tools and commands match existing src/ and skills patterns.