acx.code.assistant

Generate Carbon ACX code scaffolds for React, Cloudflare Workers, and Python.

Updated Aug 9, 2025
One-click install
npx skills add https://github.com/chrislyons/carbon-acx --skill acx-code-assistant
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: acx.code.assistant
Source: https://github.com/chrislyons/carbon-acx/tree/main/.claude/skills/project/acx-code-assistant
Command: npx skills add https://github.com/chrislyons/carbon-acx --skill acx-code-assistant

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires TypeScript, React, Vite, Python, Cloudflare Workers, ESLint, Prettier, Ruff, Black, Vitest, pytest, and includes references (resource) components.

What problem does it solve?

Writing boilerplate code that adheres to strict project conventions, style guides, and quality standards is repetitive and time-consuming. This skill automates the generation of production-ready code scaffolds for Carbon ACX, ensuring consistency and reducing development effort.

Core Features & Use Cases

  • Multi-Language Scaffolding: Generates React components, TypeScript APIs, Cloudflare Workers, and Python scripts.
  • Convention Enforcement: Ensures all generated code follows Carbon ACX's specific naming, typing, and architectural patterns.
  • Built-in Quality Checks: Includes basic tests and passes linters (ESLint, Ruff, Prettier, Black) automatically.
  • Use Case: A developer needs a new React component to display emission trends. Instead of manually setting up the file, types, and basic structure, they ask the skill to "Create a React component for displaying emission trends," getting a ready-to-use, compliant scaffold in seconds, so "AI works, you rest."

Quick Start

Example: React Component Generation

User: "Create a React component for displaying a list of activities with their emission factors"

Output File: apps/carbon-acx-web/src/components/ActivityList.tsx

import React from 'react';

interface Activity {

activity_id: string;

name: string;

emission_factor?: number;

unit?: string;

}

// ... (rest of the component code)

Frequently Asked Questions about acx.code.assistant

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

FAQPage Schema
How do I generate production-ready React components that follow project conventions?

This Skill generates React components with TypeScript strict mode, ESLint/Prettier compliance, design-token styling, and basic tests built in. Describe what you need—a list, form, or chart component—and get a scaffold matching Carbon ACX conventions instantly, ready to customize.

Can I generate Cloudflare Workers endpoints that comply with team standards?

Yes. The Skill creates Cloudflare Workers endpoints with TypeScript typing, error handling, and linter compliance. It enforces repository conventions from AGENTS.md and CLAUDE.md, so generated endpoints integrate seamlessly into your monorepo without manual refactoring.

What scaffolding does this Skill support beyond React?

It generates React components, TypeScript APIs, Cloudflare Workers, Python scripts, API clients, and test suites. All output adheres to Carbon ACX conventions: TypeScript strict mode, Ruff/Black for Python, ESLint/Prettier for JavaScript, and includes basic tests automatically.

How do I ensure generated code passes linters and style checks?

The Skill bakes in compliance with ESLint, Prettier, Ruff, and Black during generation. All scaffolds pass these tools without manual fixes, saving time on code review cycles and formatting disputes within your team's standards.

Can I use this for Python scripts and data pipelines?

Yes. The Skill generates Python scripts and data pipelines with Ruff and Black formatting, robust error handling, and basic pytest tests included. Output follows Carbon ACX conventions for naming, typing, and structure across the monorepo.

What happens if I need test files for my generated code?

Test suites are generated alongside your code. React components get Vitest tests; Python code gets pytest suites. All tests follow repository conventions and are ready to run, reducing the barrier to test coverage from the start.